The call ends. The next action is already clear.
Turn every completed conversation into structured data your software can use: outcome, duration, end reason, transcript, task facts, recording availability, quality, and usage - delivered by API or signed webhook.
Call result
Talk To My Agent
Conversation
Post-call record
Workflow action
CRM updated · reschedule task created
Webhook verified
Stop treating calls like a black box.
The conversation becomes searchable evidence and a reliable trigger for the systems that run the business.
Know what happened
See status, end reason, duration, direction, caller and called number, plus task facts produced for outbound objectives.
Review the actual conversation
Use optional transcripts and recordings for coaching, dispute review, quality control, and understanding recurring demand.
Automate the next step
Send the completed call record to your CRM, data warehouse, support queue, or n8n workflow through a signed webhook.
A reliable result pipeline after every call.
Read results on demand or subscribe once and let completed calls push structured records into your stack.
- 01
The call completes
The gateway reports duration, direction, end reason, optional transcript, quality data, and task results.
- 02
The record is normalized
Inbound and outbound calls use a consistent response shape so downstream software does not parse local files.
- 03
Your endpoint is notified
A signed webhook delivers the same detailed call object and can retry without changing the payload.
- 04
Your workflow acts
Deduplicate by event ID, verify the signature and timestamp, then update the system that owns the next step.
Your data policy decides what is kept and shipped.
Call intelligence is useful only when access and retention are deliberate. Transcripts can remain local, shipping can be disabled, and recordings are exposed through short-lived signed URLs when available.
Signed delivery
Verify HMAC against the raw request body, enforce timestamp freshness, and process each event ID once.
Optional transcript shipping
When transcript shipping is off, local text can remain on the self-hosted server and the API reports that no transcript was shipped.
Scoped retrieval
Read call lists, individual results, and recording links through authenticated voice:read access.
What teams build with call data
Read the Call Results API guideCall intelligence questions
What does a call result include?
The detailed endpoint can include status, direction, numbers, duration, end reason, transcript, task facts, usage, quality, and whether a recording is available.
Do I have to ship transcripts?
No. Transcript shipping is configurable. When disabled, transcripts may remain as local files on the self-hosted gateway and are not returned through the API.
How are webhooks secured?
Verify the HMAC signature over the raw body, check timestamp freshness, reject replayed event IDs, and keep the shared secret in your server’s secret store.
Can I fetch a recording through the API?
When a recording exists and your key has read access, the recording endpoint returns a short-lived signed URL rather than exposing the storage object publicly.
Make every conversation improve the next one.
Connect call results to the place where your team already measures, learns, and acts.
Plan your result pipeline