Destinations

Send every call's details somewhere useful after it ends — a note in your CRM, a message to your team, or your own webhook.

A destination is where a call's details go once the call is over. Set one up and every call that agent handles — answered or not — is written out automatically.

Open Integrations → Destinations.

What you can send to

The list shows what's available to your workspace today. There are two kinds:

Messaging — send a summary as a message when a call ends.
Your own webhook — post the call's details to any URL you control. This is the flexible one: point it at your own backend, or at an automation tool that accepts a webhook, and you can reach almost any system from there.

New destinations appear in this list as they're published — there's nothing to install.

Set one up

Choose a destination

Find it in the list and click Set Up.

Fill in what it needs

A webhook needs a URL. A messaging destination needs the account details it sends from. Anything secret is stored write-only — you can replace it later, but not read it back.

Switch it on for an agent

Open the agent, go to the Actions tab, and tick this destination under Send call details to (Destinations).

Setting a destination up doesn't start it sending. Step 3 is the one that matters — a destination that isn't ticked on an agent stays idle no matter how it's configured.

What a destination's status means

Badge	Meaning
Active	Set up and tested. Ready to receive call details.
Untested	Set up, but we haven't confirmed it works yet.
Inactive	Set up and switched off.

When it fires

Once per call, after the call ends — whether or not anyone answered. A missed call is still information worth having in your CRM.

Remove one

Click Remove on the destination. Agents stop sending to it immediately.