Confirm access
Check whether the provider exposes transcripts, recordings, recording URLs or call events through an approved export, webhook or API.
OPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZCALL TRACKINGFROM $99/MOENQUIRY REVIEWSENIOR TEAMISO 27001PLATFORMOPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZCALL TRACKINGFROM $99/MOENQUIRY REVIEWSENIOR TEAMISO 27001PLATFORM
GibsonFamily-Owned Sydney Lead Engine · Since 2006
Internal Gibson operation
Can AI analyse calls from your existing provider?
Yes. AI can analyse calls from an existing provider when the account exposes a usable transcript, recording or event feed. Post-call analysis does not normally require a phone-number transfer. Transcripts and accessible recordings support conversation review; metadata supports attribution and workflow reporting but cannot reveal what was said.
Published 5 August 2026 · Last reviewed 5 August 2026 · By Albert Triolo, Founder and Managing Director
Current public statusOperating Gibson call-event connector pattern; provider access is assessed separately
Evidence boundary
This proves one operating connector pattern, not universal compatibility. Conversation analysis still depends on provider access to a recording or transcript, lawful recording controls and a separately scoped data path.
What is confirmed
Facts this entry can support.
- 01Gibson operates a connector that receives authenticated call-start and call-end events from its current provider.
- 02The connector creates or enriches a Zoho Call_Tracking_Data record and matches the two events with Gibson_Call_ID.
- 03Zoho is Gibson's verified operating example, not a customer requirement. A customer's existing CRM can be assessed for a usable API, import or approved integration path.
- 04Call-end data can add duration, outcome, voicemail state and a recording URL when the provider supplies those fields.
- 05If the matching start record is absent, the connector creates a combined fallback record and returns the action created-fallback.
How a similar problem proceeds
What has to be true before AI can review the calls?
The decisive question is data access, not the provider logo. A scoped assessment confirms what the account exposes before Gibson quotes an implementation.
Set the lawful use
Confirm notice, consent, retention, access and review controls for the intended Australian operating context.
Map the decision
Define the buyer question the calls must answer, such as lost-lead reasons, objection patterns, lead quality or agent coaching.
Test a bounded sample
Run representative calls through a controlled review, record failures and decide whether a production integration is justified.
Redacted operating proof
What does Gibson's operating connector actually prove?
This redacted path is based on Gibson's current Delacon-to-Zoho connector. Zoho is the verified Gibson example, not a customer requirement. The same pattern can be assessed for a customer's existing CRM without publishing caller data, credentials or recording URLs.
- 01
Authenticated call-start event
- call_id
- caller
- tracking_number
- campaign
- call_start
- 02
Create CRM call record
- Gibson example: Zoho
- Call_Tracking_Data
- Gibson_Call_ID
- Status_of_Call: In Progress
- 03
Call-end enrichment
- Call_Duration_s
- Status_of_Call
- Voicemail
- Call_Recording_URL
- Survey_Outcome
- 04
Match or create fallback
- Match on Gibson_Call_ID
- Update existing record
- Otherwise create combined record
- Return created-fallback
The artefact shows the integration shape only. Available fields vary by provider and account. It does not expose a caller, credential, transcript or recording, and it does not prove that another provider grants the access needed for conversation analysis.
Implementation decision
Do you need to replace the phone system first?
Often, no. Keeping the current provider can reduce operational disruption, but only when the required call data is accessible and reliable.
| Option | When it fits | What to verify |
|---|---|---|
| Keep the existing provider | Useful when recordings, transcripts or events can be accessed through an approved path. | The available data and history are limited by the provider, plan, permissions and retention settings. |
| Replace the phone system | Useful when the current provider cannot expose required data or when broader telephony change is already justified. | Number transfer, routing, training and operational risk make replacement a separate business decision. |
Questions before using this example
Status and fit, answered directly.
Do we need to transfer our phone numbers to Gibson?
Usually not for post-call analysis. If the current provider exposes a usable transcript, recording or event feed, Gibson can assess a connector around that source. A number transfer is only considered when the existing system cannot support the required outcome or a wider telephony change is already in scope.
Can AI analyse calls when we only have call metadata?
Only in a limited way. Metadata can support attribution, missed-call reporting, duration analysis and workflow checks. It cannot show what the caller or agent said, so it cannot support reliable conversation themes, objections or coaching without a transcript or accessible recording.
What if the provider has recordings but no transcripts?
A separately scoped workflow may transcribe accessible recordings before analysis. The assessment must confirm lawful access, audio quality, file format, retention, volume, security controls and the accuracy required for the decision.
Will the Free Review inspect our provider account?
No. The Free Review is an orientation conversation, not an evidence inspection. If the use case is worth pursuing, Gibson separately scopes an assessment of provider access, data quality, controls and a representative sample before quoting implementation.
Does our business need to use Zoho CRM?
No. Zoho is named because it is Gibson's verified operating example. A customer's existing CRM, such as HubSpot, Salesforce or another supported system, can be assessed for API, import, identifier, permission and write-back requirements. Naming an example does not guarantee compatibility.
Where can the analysis results go?
Depending on scope, approved outputs can be written to the customer's CRM after compatibility assessment, or to a reporting table, dashboard or human review queue. CRM write-back and other system integrations are owned by Gibson's Integrations service and are quoted separately from the conversation-analysis configuration.
What happens after the Free Review?
The Free Review identifies whether the operating problem is worth investigating. A separately scoped assessment then tests access, evidence, controls and representative calls. Gibson only quotes implementation after those facts are known.
Canonical service ownership
Which Gibson page owns the next question?
Call Tracking ›The canonical service for broad call attribution, campaign reporting and inbound call analytics.Speech Analytics ›The service for configured conversation review when usable call content is available.Integrations ›The canonical service for assessed CRM write-back and connections between supported systems.Can AI read call tracking data? ›A practical guide to the difference between call metadata and conversation content.Call recording in Australia ›A general legal and operating overview to inform, not replace, professional advice.Start with the Free Review ›An orientation conversation only. Account access and evidence inspection require a separately scoped assessment.
Provider references
What do provider documents establish?
- Twilio Conversational Intelligence documentationTwilio documents post-call analysis and support for recordings sourced outside Twilio. Provider access and implementation details still require verification.
- ClickSend Voice Messaging documentationClickSend documents outbound text-to-speech voice messaging and states this product is unavailable to new customers. It is not evidence that ClickSend supplies inbound call recordings for this use case.
Related register entries
Next decision
Keep the provider. First prove the data path.
Use the Free Review to orient the problem. If the opportunity is credible, Gibson can separately scope the provider-access assessment and then quote a bounded conversation-analysis implementation. Write-back to the customer's CRM, after compatibility assessment, is a separate integration scope.