Skip to main content
Dialer events tell you what happened on a call placed by a Dialer campaign: the disposition the user recorded and, when the campaign uses one, the survey they filled in. Both events carry the campaign, the contact, and the user, so you can update your CRM without a follow-up API call. These are account-level webhooks, delivered to the endpoints you register under Account → Webhooks. See the overview. Dialer events require the Dialer add-on. Neither event carries call details such as duration or recording: join on call_uuid with call.ended or fetch the call from the API. All examples show the full request body, including the envelope. Fields with empty values are omitted from payloads: they are never sent as null. Fields shown in bold are always present. A bold field nested inside an optional object is always present whenever that object is. Everything else is optional.

The dialer object

Both events carry the same dialer object identifying the campaign:

dialer.disposition_created

Fires when a user records a disposition on a Dialer call: the outcome they chose, their note, the number that was dialed, and what the campaign will do with the contact next. Use it to log call outcomes in your CRM, create follow-up tasks for rescheduled calls, or suppress contacts who asked not to be called again.
Example

dialer.survey_filled

Fires when a user submits a survey response on a Dialer call. The payload carries every answer in full, together with the disposition the response belongs to. Use it to push qualification answers into your CRM or trigger workflows on specific responses.
Example
A survey can be submitted before or after the disposition on the same call, and the two events can arrive in either order. Correlate them on call_uuid, or on survey.response_id and disposition.survey_response_id when both are present.