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

# Webhooks and Callbacks

> How SentiVue Talk exchanges call events with telephony providers

SentiVue Talk sets up its own webhooks with your telephony provider. You do not host or configure them.

## What SentiVue Talk does

When a call starts, SentiVue Talk:

1. Hands the provider the URLs it should call back on.
2. Verifies the signature on every incoming request, so a forged callback is rejected.
3. Tracks the call through its lifecycle: `initiated`, `ringing`, `answered`, then `completed`, `busy`, `no-answer`, or `failed`.
4. Streams audio both ways for the duration of the call, in whichever format the provider uses.

## What you configure

For **outbound** calls, nothing. SentiVue Talk passes its callback URLs to the provider each time it places a call.

For **inbound** calls, you set one webhook URL in the provider's console so incoming calls reach SentiVue Talk. The exact field name differs per provider — each provider's page under [Telephony](/talk/integrations/telephony/overview) gives the URL and where to paste it.

## When inbound calls do not arrive

Check the provider's console first: it logs the response it got from each webhook attempt, which tells you whether the call reached SentiVue Talk at all.

Then confirm, in your telephony configuration:

* The number is listed.
* It has an **Inbound workflow** assigned.
* The webhook URL in the provider's console matches the one on that provider's page exactly.

For providers that scope numbers to an application or connection — Telnyx and Vonage among them — also confirm the number belongs to the same application whose ID you configured in SentiVue Talk.