Skip to navigation

Webhook Events

View as Markdown

SimZ can send webhook events to your application when a call completes or when a call audit finishes. Use these events to sync call outcomes, recording metadata, lead custom data, and audit results.

Event types

EventWhen it firesBest forRequires review prompt?
call.completedAfter recording completes and the call record is updated.Call metadata, recording metadata, lead custom data.No
call.audit.completedAfter audit/review processing finishes.Qualification and review outcomes.Yes

call.completed

This event fires after SimZ stores call recording and metadata. It is independent from audit processing.

{
"event": "call.completed",
"callId": "call_1777920072301_12514",
"agentId": "d5c58cfd-ddb4-47ba-8c85-d68a8f7f36e3",
"companyId": "comp_0005",
"status": "Completed",
"amd_result": null,
"timestamp": "2026-05-19T15:02:14.781Z",
"call": {
"direction": "Outbound",
"callerNumber": "+15551234567",
"toNumber": "+15557654321",
"callDateTime": "2026-05-19T15:00:02.000Z",
"durationSeconds": 132,
"billedDurationMinutes": 3,
"recordingUrl": "call_1777920072301_12514.mp3",
"twilioCallSid": "CAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
},
"lead": {
"customData": {
"leadId": "LEAD-001",
"campaignTag": "spring-2026"
}
}
}

The status field carries the call’s lifecycle status. Common values are Completed, AMD Terminated, No Answer, Busy, Failed, and Canceled.

amd_result is populated only when answer machine detection ran and reached a conclusion; it is null otherwise. See Answer Machine Detection for how to interpret it.

amd_resultMeaning
machine_start, machine_end_beep, machine_end_silence, machine_end_otherAn answering machine or voicemail greeting was detected.
faxA fax line answered.
transcript_guardSimZ’s transcript-based layer recognized a voicemail greeting.
humanA live person answered.
unknownDetection was inconclusive; the call continued as normal.

call.audit.completed

This event fires after SimZ finishes review/audit processing. The audit object depends on your agent review prompt and custom fields schema.

{
"event": "call.audit.completed",
"callId": "call_1777920072301_12514",
"agentId": "d5c58cfd-ddb4-47ba-8c85-d68a8f7f36e3",
"companyId": "comp_0005",
"status": "human",
"timestamp": "2026-05-19T15:06:41.220Z",
"lead": {
"customData": {
"leadId": "LEAD-001",
"campaignTag": "spring-2026"
}
},
"audit": {
"qualified": true,
"reason": "Customer confirmed interest and scheduled a callback"
}
}

Unlike call.completed, the status on this event is a classification of who or what answered, not a lifecycle status. It is always one of:

statusMeaning
humanA live person answered and took part in the call.
answer_machineVoicemail, an answering machine, or a fax line answered.
no_answerNobody picked up, or the line was busy.
dncThe call reached a do-not-call outcome.
failedThe call failed or was canceled.
unknownThe outcome could not be classified.

Common fields

FieldTypeDescription
eventstringEvent name.
callIdstringSimZ internal call ID.
agentIdstringAgent that handled the call.
companyIdstringCompany ID.
statusstringCall lifecycle status on call.completed; answer classification on call.audit.completed. The two use different value sets — see each event above.
timestampstringISO 8601 generation timestamp.
lead.customDataobject or nullClient custom data passed with the lead or call.

Delivery behavior

Webhook deliveries are signed when a secret is configured, retried according to webhook settings, and logged in the SimZ webhook management UI.