After Call Actions

Overview

Open Tools and select the After Call Actions tab ("Automatically trigger actions when a call ends with a specific disposition"). There are two kinds of action:

Actions are triggered by dispositions — the call outcomes you define in the agent editor under ⚙️ Tools & Data → Dispositions (for example Appointment Booked, Needs Callback, Complaint). At the end of each call the AI picks the disposition that fits; every action whose trigger list includes it runs. Matching ignores upper/lower case.

Organization admins and members with write access to Tools can create and change actions. Others can view the list.

Required Setup

After Call Actions only run for agents that send their end-of-call data to VINSI. Do this once per agent (and per direction):

1. On the After Call Actions tab, in the Required setup box, click Copy to copy the webhook URL (it ends in /api/webhooks/ai-phone-agent).
2. Open the agent in AI Phone Agents. On the Inbound Agent tab, go to ⚙️ Tools & Data and paste the URL into After Call Webhook.
3. If the agent also makes outbound calls, paste the same URL on the Outbound Agent tab.
4. Make sure the agent has Dispositions on each tab you use — they are what your actions trigger on.
5. Click Save.

Create an Email Action

1. On the Email tab, click Add Email Action (or + Add your first email action).
2. Scope to agent — leave All agents to run for calls from any agent, or pick one agent. Each agent is listed as "Name — Inbound" or "Name — Outbound", so you can target one direction.
3. Disposition trigger(s) — choose one or more dispositions. The list comes from the selected agent (or from all agents).
4. Send email to — the recipient address, e.g. team@company.com.
5. Subject — can include variables.
6. Email body — HTML supported, can include variables.
7. Optionally tick attachments.
8. Check the Preview with sample data tab, then click Create action. The button stays disabled until at least one disposition, a recipient, and a subject are filled in.

The action is named automatically, e.g. On "Appointment Booked, Needs Callback" → Email. Emails are sent from VINSI.AI <noreply@vinsi.ai>.

Template Variables

Click in the Subject or Email body, then click a variable chip to insert it at the cursor. You can also type them.

When you scope the action to an agent that has Call Data, its fields appear as chips (e.g. {{call_data.customer_name}}). Otherwise example chips are shown — replace KEY with your own field key. If the caller never provided a Call Data field, the email shows Not provided. A misspelled variable is left as-is in the email, so check the preview.

<p>New callback request from {{call_data.customer_name}} ({{user_phone}}).</p>
<p><strong>Outcome:</strong> {{disposition}}</p>
<p><strong>Summary:</strong> {{summary}}</p>
<p><a href="{{recording_url}}">Listen to the recording</a></p>

Attachments

Create a Ticket Action

1. On the Ticket tab, click Add Ticket Action.
2. Set Scope to agent and Disposition trigger(s) as for email.
3. Assign to user (optional) — a member, or Unassigned. Assign to group (optional) — a ticket group, or No group. Assigned users and group members get the usual ticket assignment email.
4. Optionally tick Send email notification when ticket is created, enter Send ticket notification to, and choose attachments.
5. Click Create action (a disposition is the only required field).

Each matching call creates a ticket in VINSI Desk with:

The notification email is titled Ticket #… Created — [disposition] and includes the summary and a View Ticket in Vinsi Desk button. Ticket workflows set to run on ticket creation also run.

Edit, Duplicate, Delete

Each tab lists its actions with Name, Type, Description, Ownership, and Actions. Use Search by disposition or email... to find one.

• Edit — click the row or the edit button, change settings, and click Save changes.
• Duplicate — creates Copy of … with the same settings, handy for a second recipient.
• Delete — confirm in the dialog. This can't be undone.

Actions have no on/off switch — delete an action to stop it.

Examples

After Call Webhook (Your Own Endpoint)

Instead of the VINSI URL, you can enter your own HTTPS endpoint in ⚙️ Tools & Data → After Call Webhook (placeholder https://api.domain.com/endpoint) to push call results into your CRM, Zapier, Make, or a custom app. Inbound and outbound tabs each have their own field. The agent won't save an invalid URL ("Please enter a valid url for the after call webhook").

When a call ends, VINSI sends one POST request with a JSON body to that URL. It isn't signed and isn't retried, so make your endpoint quick and reliable.

Webhook Payload

{
  "user_phone": "+16615550123",
  "agent_phone": "+16615550199",
  "variables": { "firstName": "Ada" },
  "organization_id": "org_...",
  "disposition": "Appointment Booked",
  "summary": "The caller booked a cleaning for Tuesday at 10 AM.",
  "transcript": "BOT: Thank you for calling...\nHUMAN: Hi, I'd like to...",
  "recording_url": "https://...",
  "call_id": "c_...",
  "call_data": {
    "customer_name": { "value": "Ada Lovelace" }
  },
  "transferred_to": null
}

Conversations from the website widget's text chat send the same fields except variables, with user_phone and agent_phone set to text_chat, recording_url null, and an extra "call_type": "widget_text".

See also Call Logs for the same data in the dashboard, and Go High Level for a built-in CRM integration.

Troubleshooting & FAQ