Skip to main content

Live call triggers

A live call trigger listens to calls while they happen and acts when something is said: "when the caller says cancel, alert the supervisors and show the agent a hint". You define the triggers on the Live call triggers page (/admin/live-triggers, under AI). Administrators (settings:write) create and change them; supervisors (queues:monitor) and readers of the settings (settings:read) can see them.

What you need​

Triggers listen through the speech-to-text provider of live assist. Switch on Live assist in the AI settings (for the company, or for the queues you want) and set up a speech provider for it. Until then the page shows needs a speech provider and no trigger runs on calls.

Phrases need nothing more than speech-to-text. A topic (see below) also uses the live assist AI model.

What a trigger is made of​

PartMeaning
NameShown in the call history, the supervisor alerts and reports. Unique in the company.
Switched onOnly switched-on triggers listen to calls.
Which callsAll calls, or chosen queues and departments (and, through the API, chosen people), plus the direction: any, incoming, outgoing or internal.
Who says itThe caller, the agent, or either side.
PhrasesWords to listen for, one per line, optionally with a language code: en: cancel, es: darme de baja, de: kündigen. Upper and lower case and accents are ignored (resilier matches résilier) and only whole words count (cancel does not match cancellation). Chinese and Japanese phrases match anywhere in the sentence. A phrase with a language code is only used on calls in that language; * means any language.
TopicOptional: one sentence such as "The caller asks for their money back". The live assist AI decides when the topic comes up.
Fire again afterEmpty: the trigger fires once per call. Otherwise it may fire again after that many seconds (10 to 86400).
What to doOne or more actions, below.

Actions​

ActionWhat happens
Alert supervisorsA push to the supervisors' MonoPhone app (or to the people you chose). It opens the Supervisor area's alert list, which shows the trigger's name.
Post in chatA short message in a team chat group: which trigger fired on a call and who spoke.
Webhook eventThe event call.trigger_fired goes to your webhook endpoints that subscribe to it. It carries the ids, the trigger's name and the other party's number (caller), never a word of the call. The number is left out of what the events feed shows in the console.
CRM noteA note on the caller's record in a connected CRM.
Helpdesk ticketA ticket in a connected helpdesk (Zendesk, Freshdesk, ServiceNow).
Tag the callA tag on the call, shown with the fired trigger in the call history and usable in reports.
Hint for the agentA short text on the agent's live assist screen while the call goes on.

An action that needs an integration you have not connected is skipped; the tester tells you which.

Ready-made triggers​

Six templates come with the PBX, switched off, with phrases in English, Spanish, Portuguese, French, German, Italian, Russian, Chinese and Japanese. Click Enable to add one for all calls; you can edit it afterwards like any other trigger.

TemplateListens for (English examples)Starts with
Cancellation riskcancel, unsubscribe, switch providerAlert supervisors, tag, hint for the agent
Legal threatlawyer, sue, courtAlert supervisors, tag, webhook event
Complaintcomplaint, unacceptable, managerAlert supervisors, tag, hint for the agent
Competitor mentionedyour list (empty at first)Tag
Payment talkcard number, pay nowTag, hint for the agent
Positive feedbackthank you so much, excellentTag, webhook event

Competitor mentioned is added switched off because it has no phrases yet: add your competitors' names and switch it on.

Testing a trigger​

You can see what a trigger does without a real call:

  • Test the triggers: type a few sentences, one per line. Start a line with caller: or agent: to choose who says it. The answer lists every trigger that would fire, on which line and with which phrase, and which of its actions would run. This is a dry run: nothing is sent, stored or pushed. Tick Also test the ready-made triggers to try the templates before enabling them.
  • Speak to test: click Start speaking and talk into your microphone as on a call; the page shows your words and the triggers that fire. It uses your speech provider (the usage counts like a call), lasts at most five minutes, and is also a dry run.

Through the API the same dry run is POST /api/v1/ai/live-triggers/test:

{ "text": "caller: I want to cancel my contract\nagent: I can help with that", "locale": "en", "include_templates": true }

Where fired triggers show up​

  • Call history: the call detail lists Triggers fired with the trigger's name, the time and who spoke.
  • MonoPhone app: supervisors get the push and see the trigger in the Supervisor area's alerts.
  • Reports and API: GET /api/v1/ai/live-triggers/fires (filter by call, trigger, tag and time) and GET /api/v1/ai/live-triggers/report (fires per trigger).
  • Webhooks: call.trigger_fired, for triggers with a webhook action.

Privacy​

  • What was said is never stored. A fired trigger keeps only the trigger, the time, who spoke, the id of the matched phrase and the tags.
  • Chat posts, CRM notes and tickets say which trigger fired and who spoke, not what was said.
  • The words of the spoken test are shown only on your screen.
  • Triggers follow the company's AI settings: when live assist is switched off, no call is listened to.
  • Fired triggers are kept as long as the flag retention of the call quality settings (90 days unless you change it).

Working with the lists​

The trigger list works like the Users list: the trigger's name opens the editor, and the ... menu at the end of a row has Edit and Delete. Below 640 pixels wide the table turns into cards with no sideways scrolling. A list that cannot be loaded shows the reason and Try again.