AI Agent Alerts | Get Notified About Keywords, Caller Intent and Caller Sentiment

AI Agent Alerts | Get Notified About Keywords, Caller Intent and Caller Sentiment

Overview

Alerts tell you, while a call is still in progress, that something needs attention. Your AI Agent listens to the live conversation and, when a rule you set up is triggered, sends a text message, an email or a message to a web address (a webhook) to whoever you choose. There are three kinds:

KindTriggers whenExample
Keyword AlertsA specific word or phrase is spokenThe caller says "cancel" or "speak to a manager"
Intent AlertsThe AI judges that the caller is trying to do something you described, even if no exact words match"Caller says they want to cancel their service"
Sentiment MonitoringThe caller's mood falls below a level you chooseThe caller sounds increasingly angry

Alerts do not change what the agent says or does on the call. They are a signal to your team. To have the agent actually hand the caller to a person, see: Call Routing Rules (Flow State).

Prerequisites

  • An AI Agent already set up and taking calls. See: Setup AI Agent.
  • At least one place to send alerts: a mobile number for text messages, an email address, or a webhook address that your other system provides.
  • For Sentiment Monitoring and Intent Alerts, a plan that includes them. On other plans the section shows a note that it is not included and its switch is unavailable. Keyword Alerts are not shown with a plan restriction.

Open the Alerts tab

  1. Open your agent.
  2. Select the Alerts tab. Its intro reads "What the agent should tell you about after a call, words it heard, how the caller sounded, and what they were trying to do." 

  3. You will see three cards, Keyword Alerts, Sentiment Monitoring and Intent Alerts, each with its own on/off switch.

Each card is saved only if you changed something in it. Save with the tab's normal save control. If a card is not in your plan, saving the other cards still works.

Notification destinations (the same for all three kinds)

Every alert needs at least one destination: where the notification goes. Select Add destination and fill in a row:

TypeWhat to enterExample
SMSA mobile number with country code+15551234567
EmailOne email addressalerts@example.com
WebhookA web address starting with http:// or https:// that your other system (or Zapier) gives youhttps://hooks.example.com/alert

You can add several destinations to one alert, for example a text to the duty manager and an email to the shared inbox. Use the bin icon at the end of a row to remove it. An alert with no destinations cannot be saved.

What the recipient receives: a short message naming the kind of alert (Keyword Alert, Intent Alert or Sentiment Alert), the agent, what triggered it (for a keyword, the word and what was said), the caller's number when known, and the time. A webhook receives the same information as structured data.

Set up Keyword Alerts

  1. On the Keyword Alerts card ("Get notified in real-time when specific words or phrases are detected during a call."), turn the switch on.
  2. Set Cooldown (seconds). This is the minimum time between repeat alerts for the same keyword on the same call. The default is 300 (five minutes). It stops a caller who repeats a word from flooding your phone.
  3. Select Add Keyword Alert.
  4. In the first box, type the word or phrase, for example cancel or speak to manager.
  5. Next to Monitor, choose Caller only (default) or Caller and agent. Choose "Caller and agent" if you also want to know when the agent itself says a particular phrase.
  6. Under Notification destinations, select Add destination and complete at least one row.
  7. Add more keyword alerts as needed, then save.

How matching works: the keyword is matched anywhere in what was said, ignoring capital letters. The word "cancel" will therefore also match "cancellation". Only the words you type are matched; synonyms are not (use an Intent Alert for that).

Set up Sentiment Monitoring

  1. On the Sentiment Monitoring card ("Get alerted when caller sentiment drops below a threshold during a call."), turn the switch on. If it says it is not included in your plan, contact your account manager.
  2. Drag the Alert Threshold slider. The scale runs from -1.00 (very negative) through 0 (neutral) to 1.00 (very positive), in steps of 0.05, with faces along the bar: Very angry, Angry, Upset, Unhappy, Neutral, Content, Very happy. Alerts fire when the caller's mood score drops below the value you pick. The default is -0.60, between Upset and Angry. A value nearer 0 alerts more often; a value nearer -1 alerts only for very upset callers.
  3. Set Rolling window (seconds): the recent stretch of conversation over which mood is judged ("Sentiment is averaged over this time window."). Default 30, minimum 5.
  4. Set Cooldown (seconds): minimum time "Between alerts". Default 120.
  5. Add at least one destination under Notification Destinations.
  6. Save.

Set up Intent Alerts

Use these when the exact words will vary. You describe the situation in plain English and the AI decides whether the caller's latest words match it.

  1. On the Intent Alerts card ("Use AI to detect caller intents in real-time and trigger notifications. Define intents by description, no exact keyword match needed."), turn the switch on. If the card says it is not included in your plan, contact your account manager.
  2. Set the section settings:
    • Window (seconds): how far back the AI looks at the conversation when deciding. Default 60, minimum 5.
    • Cooldown (seconds): minimum time before the same intent can alert again on the same call. Default 300.
    • Monitor: Caller only or Caller and agent. This applies to all intents in the section.
  3. Select Add Intent.
  4. Enter an Intent name, for example wants_to_cancel. This is the label your team will see.
  5. In Description, say when it should trigger, for example "Caller expresses intent to cancel their service". The description is what the AI matches on, so be specific. Mention what does not count if it is easy to confuse.
  6. Add at least one destination under Notification Destinations.
  7. Save.

Error messages you may see

Saving checks everything first and shows "Fix the highlighted alerts before saving." Common causes:

  • "A keyword is required", "A name is required", "A description is required" (the intent description is what the AI matches on).
  • "Add at least one destination".
  • "A destination is required", "Enter a valid phone number", "Enter a valid email address", "The URL must start with http:// or https://".
  • "The window must be at least 5 seconds."

Tips and troubleshooting

  • Test it. Call your own agent (or use the AI Agent Tester) and say the keyword. Remember the cooldown: a second test inside the cooldown does not alert. Start a new call to reset it.
  • Cooldowns are per call. A new call starts fresh, so two separate callers who both say the keyword each trigger an alert.
  • Too many alerts. Use a longer cooldown, narrow a keyword to a longer phrase ("cancel my account" rather than "cancel"), or lower the sentiment threshold towards -1.
  • No alerts arrive. Check that the card's switch is on and the changes were saved, the destination is typed correctly (SMS numbers need the country code), and, for email, check the spam folder. A webhook address must be reachable from the internet.
  • Intent alert fires on the wrong calls. Make the description more specific and shorten the window so older conversation does not influence it.
  • Don't send callers' sensitive details by text or email unless your policy allows. Alerts can include what the caller said.
  • Alerts are sent live during the call. For a written recap after the call, see: Call Summaries and Zapier Post-Call Automation.
  • see: Call Summaries
  • see: Zapier Post-Call Automation
  • see: AI Agent Webhook
  • see: AI Agent Email
  • see: Call History | Transcripts, Recordings, AI Analysis and Tool Calls
  • see: Call Grading and Feedback
  • see: AI Agent | Team Messaging: Ask, Transfer to, and Notify a Team Member