Skip to main content

FAQ: events before and after the call

What is available and where it is configured

All of this is configured on the agent or the organization and does not depend on where the campaign came from: the adapter adds no special events.
That is expected: the old platform’s post-call integrations were called by the V2 engine, while adapter campaign calls run in V4. The client needs V4 webhooks on the agent or a post-call function that calls its HTTP URL.
The webhook body carries no adapter identifiers. To let the client match a call to its record, map foreign_id to an agent variable with a map entry: contact variables arrive in the webhook together with the other call variables. The phone number is always in the webhook.
Check in order:
  1. the campaign’s agent has a URL;
  2. the URL is subscribed to the right event;
  3. the URL is not disabled;
  4. the call is not from a test campaign — test calls do not send webhooks;
  5. Webhook deliveries shows no rejection by the URL;
  6. the delivery has not used up its eight attempts — if it has, click Retry.
call_analyzed arrives later than call_ended: it waits for post-call analytics and the recording.
The pre-call function returned cancel: the contact is closed as Cancelled by a pre-dial function. retry defers it for at least a minute and runs out after the campaign end. If there are too many cancellations, the platform pauses the campaign.Look at the call_decision event in the transcript, check the function logic with a test run in the agent settings, and lift the pause. More in Function troubleshooting.
Campaigns have no separate «SMS after the call» rule. Options: a post-call function with an HTTP call that sends the SMS, or a call_ended webhook handler on the client side. SMS numbers belong to the organization and are configured in channels.