> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hubtalk.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ: events before and after the call

> Webhooks, call functions, tool calls and observers for adapter campaigns; V2 post-call integrations.

# FAQ: events before and after the call

> [accordion] What is available and where it is configured
>
> | Mechanism | Where it is configured | When it fires | Where to track it |
> | - | - | - | - |
> | [Post-call webhooks](https://docs.hubtalk.ai/v4/webhooks.md) | Agent settings → **Webhooks**: the URL and the events `call_ended`, `call_analyzed`, `observer_incident` | After the call; `call_analyzed` waits for post-call analytics and the recording (up to 30 s) | Call panel → **Data** → **Webhook deliveries**: status, attempts, the **Retry** button. After eight failed attempts the delivery waits for a manual retry |
> | [Pre-call functions](https://docs.hubtalk.ai/v4/platform/call-functions/before.md) | Agent → global flow settings → call functions; versioned together with the flow | Before dialing, up to 60 s; can return the decision `proceed`, `cancel` or `retry` | Transcript → pre-call function events and `call_decision`; the contact is **Cancelled by a pre-dial function** or deferred |
> | [Post-call functions](https://docs.hubtalk.ai/v4/platform/call-functions/after.md) | Same place | Once after post-call analytics, with a condition | Transcript → post-call function event; no retries and no delivery log |
> | Tool calls inside the dialogue (HTTP, MCP) | Agent flow nodes | During the conversation | Transcript: the tool call and response |
> | Observers | Organization library or agent; reactions are on the agent | During the call | The [**Incidents**](https://docs.hubtalk.ai/v4/platform/incidents.md) section, the incident layer in the transcript; the **Notify** reaction sends the `observer_incident` webhook |
>
> 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.

> [accordion] The V2 client's post-call integration is silent
>
> 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.

> [accordion] The webhook has no batch\_id or foreign\_id of the client
>
> 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.

> [accordion] The webhook did not arrive
>
> 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.

> [accordion] Contacts close without dialing, and the campaign is paused
>
> 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](https://docs.hubtalk.ai/v4/platform/call-functions/diagnostics.md).

> [accordion] How to send an SMS after the call
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.