on_call_end
Triggered at the end of a call to provide detailed Call and End User information.
About This Event
The on_call_end
webhook is triggered at the conclusion of a call in the Altur platform. This webhook provides detailed information about the call, the assistant involved, and the end user. Use this webhook to keep your backend or CRM updated with the latest call data.
Event Details
- Trigger: Automatically triggered at the end of a call.
- Purpose: To update your backend or CRM with call status, transcript, recording URL, and user information.
Request Details
- HTTP Method:
POST
- Content Type:
application/json
- Endpoint: The URL you configure in your webhook integration settings.
- Authentication: Includes the
X-Altur-Signature
header for HMAC verification.
Payload Example
Here’s an example of the payload sent with the on_call_end
event:
Root Fields
Field | Type | Description |
---|---|---|
type | string | Event type (on_call_end ). |
id | string | Unique identifier for the call. |
status | string | Status of the call enum value (e.g., ended ). |
answered_by | string | Indicates who answered the call (human , machine or unknown ). |
transcript | array | Call transcript object. |
recording_url | string | URL to download the call recording. |
Assistant Object
Field | Type | Description |
---|---|---|
id | uuid | Unique identifier for the assistant. |
nickname | string | Assistant’s nickname. |
name | string | Assistant’s name. |
End User Object
Field | Type | Description |
---|---|---|
id | uuid | Unique identifier for the end user. |
status | string | Current status of the user enum value (e.g., converted ). |
display_name | string | Display name of the user. |
phone_number | string | User’s phone number (E.164 format). |
context | string | Additional user-specific information. |
extracted_data | object | Key-value pairs of extracted data. |
Response Expectations
Your endpoint should return a 200 OK status code to confirm receipt of the webhook. For information on retry behavior in case of failures, see the Retry Policy section in the Webhook Overview.
Security
Each request includes an HMAC signature in the X-Altur-Signature
header. Refer to the Securing Your Webhooks section for instructions on validating webhook requests.
Example Use Cases
-
CRM Integration
Use the
on_call_end
webhook to update call logs and user interaction data in your CRM system. -
Analytics
Process transcripts and user status to generate insights or trigger follow-up actions.
-
Data Enrichment
Automatically store extracted data, like account numbers or due dates, in your system for further use.