Alerts
Get told when a call needs attention, and when a call metric slips.
Alerts tell you something happened without you watching a dashboard. Creating a new alert needs a plan that includes alerts.
Two kinds of alert
They share a name and a bell icon, and nothing else.
| Call alerts | Metric alerts | |
|---|---|---|
| Question | "Did that call need me?" | "Is this agent getting worse?" |
| Fires on | One finished call, straight after its analysis | A metric drifting or crossing a bound across many calls |
| Where | The Alerts page in the customer portal | The Alerts page in the workspace sidebar |
| Delivered by | Email, text message, Slack | The Alerts page, email or Slack |
| Quiet hours | Yes | No |
The rest of this page covers call alerts. For rules that watch a number across many calls, see Metric alerts.
Managing either kind requires the workspace owner or admin role.
When a call alert fires
A call alert fires once a call has ended and been analysed. Every matching trigger fires independently, so a call that is both urgent and a new lead sends both. Chat conversations, test calls and evaluations fire nothing.
The seven triggers
| Trigger | Fires when |
|---|---|
| New leads | A first-time caller interested in what you do. |
| Urgent calls | A caller who sounds upset or time-sensitive, worth a quick callback. |
| Abandoned or dropped calls | The caller hung up before they got what they rang for, or the call dropped. |
| Messages taken | Your agent took a message or callback detail for you. |
| Bookings | Your agent captured a booking or appointment. |
| Unfinished jobs | The caller asked for something and the call ended before it got done. |
| Every call | A copy of every call, whether it needed attention or not. |
In the New alert form, New leads shows as New enquiries and Abandoned or dropped calls as Missed calls.
Built-in rows and custom rows
A built-in row cannot be retriggered on something else or deleted, and the Alerts page keeps its name. It is switched off instead, which keeps its recipients and wording.
New alert adds a row of your own, running the same trigger to a different list of people with different wording. A custom row can be removed.
The Unfinished jobs trigger is available on its built-in row only; custom alerts use the other triggers.
Who gets them
Each row carries its own recipients, separated by commas:
- Email, any number of addresses. They do not need an account here, so a shared team mailbox works.
- Text message, any number of mobile numbers, with the country code.
- Slack, any number of connected channels, set through the MCP server's
create_call_alertandupdate_call_alert. A channel is an incoming webhook connected on the workspace Alerts page under Delivery settings, the same list metric alerts post to. The message carries the caller's name and number, the agent, the call time, the summary, a Go to call button and, when the recording link is on, a Recording button.
A channel is on when it has at least one recipient. Send me a sample emails the sample to you, not to the row's recipients.
Texts are sent from the sender name VerticalAI and cannot be replied to.
Skipping the team's own calls
skipTeamCallers, set through the MCP server, drops a call from one of the
team's own numbers. The runtime marks those calls as it saves them, so a feed
of every call to a demo line carries real callers only, not the team testing
the line. It is off by default.
Scope and recordings
When the workspace has more than one line, All lines covers calls to every agent. Turn it off to pick lines one by one. Save alert stays off until at least one line is picked, so an alert can never be scoped to nobody.
Include a recording link adds a link to play the call. Opening it needs a sign-in. An email only carries it when the recipient may download recordings, unless the workspace lets everyone download them.
Wording
Leave the message fields blank to use the standard copy, which tracks any improvements we make. Fill a field in and it becomes your own.
Fields and variables
The email takes a From name, a Subject and an Email body. The text
takes a Text message. Both accept variables you can drop in at the cursor:
{{caller_name}}, {{caller_number}}, {{agent_name}}, {{did}},
{{call_time}}, {{business_name}}, {{summary}}, {{transcript}} and
{{call_link}}.
Subject: New lead from {{caller_name}}
Body: {{caller_name}} rang {{agent_name}} at {{call_time}}.
Call back on {{caller_number}}.
{{summary}}
{{call_link}}Email is sent from notifications@verticalai.com.au. The From name changes the
display name your inbox shows, not the address.
Use Send me a sample on the Alerts page to get a row's email as it will arrive, sent to your own address.
Quiet hours
Quiet hours hold real-time call alerts overnight, set once for the whole workspace:
- Pause alerts overnight turns the quiet window on or off.
- From and Until, as hours of the day. The window may cross midnight. The times are in the workspace timezone.
- Let urgent calls through, on by default.
What a held alert does
An alert that would fire inside the window is dropped, not queued: it is never delivered later. With the urgent override on, only urgent alerts come through; everything else is dropped, though the calls are still in the call list.
Summaries are not affected by quiet hours.
Daily and weekly summaries
A summary is an emailed digest instead of a message per call. Turn one on with Set up under Summaries.
| Daily summary | Weekly summary | |
|---|---|---|
| Covers | The previous day | The previous seven days |
| Schedule | A time you pick, defaulting to 7am | A day and time you pick, defaulting to Monday 7am |
Times are in the workspace timezone. Each summary has its own recipients, agent scope and subject line.
A summary with nothing to report sends nothing rather than an empty email, and each one is sent at most once per period.