Configure Escalation
Open in CMSThis tutorial walks you through the simplest end-to-end escalation setup in the CMS: enable escalation, add one trigger condition, write the response message, assign a supervisor, and test it in the Preview queue.
Before you start
- Read Hand Off to a Human for how escalation works and the short preparation checklist.
- Your agent answers well in Preview. See Preview and Publish Changes.
- The people who will act as supervisors are users of your organization. See Manage Who Can Use and Build.
Scenario used in this tutorial
| Field | Value |
|---|---|
| Agent | Atlas, Kirana Group's operations assistant |
| Trigger sample | An employee asks for an exception to an approval limit that SOP-FIN-007 does not allow |
| Target handoff | The Operations duty supervisor: Rina Wijaya, Kirana's operations lead |
Step 1: Open Escalation settings
Move your pointer over the icon sidebar on the left edge of the CMS to expand it (on a narrow screen, click the menu button (☰) at the top left instead). Then open Conversation → Escalation.
You see the Escalation page with the sections Escalation, Trigger conditions, Escalation response, Supervisors, Webhook notifications, and Escalation queue. A single Save button at the bottom saves them all.
Step 2: Enable escalation
In the top Escalation section, switch Enable escalation on. The hint says: "The agent hands a conversation to a supervisor when a trigger condition is met."
Once escalation is on and the agent has been published, the section also shows an Escalation queue row with an Open escalation queue button, which opens the supervisor queue in a new browser tab.

Step 3: Add a trigger condition
In Trigger conditions, click Add (or the Add trigger condition row at the bottom of the list) and fill in the two fields. At least one condition is required when escalation is enabled, and each label must be unique.
| Field | Value for Atlas |
|---|---|
| Label | Decision outside the SOPs |
| Description | Escalate when the user needs a decision the SOPs do not cover, asks for an exception to an approval limit, or reports a safety emergency on site. |
Click Add under the fields to confirm. To edit a condition later, click its row, change it in place, and click Save. To remove it, open the menu (⋮) at the end of the row and choose Delete. The condition goes at once, and an Undo button stays for a few seconds. Save the page to keep the change.
Write the description as a natural instruction for the AI ("Escalate when..."), not as a technical label. Name the concrete signals: here, a missing rule, an exception request, and a safety emergency. The label is what supervisors see as the trigger on each case, so keep it short and readable.

Step 4: Write the escalation response message
In the Escalation response section, fill in Response message. The hint explains: "The user gets this message word for word when the agent hands over to a person. Leave it empty and the agent writes its own." It can be up to 500 characters.
For Atlas:
This needs a person to decide. I have passed your conversation to the Operations duty supervisor, who will continue here shortly.
Make it explicit that a person now has the conversation. Avoid vague wording like "please wait" without saying who was notified.
Step 5: Set the summary language
In the same section, choose Summary language: the language your supervisors read the case summary in. For Atlas, keep English.
Choose a language your supervisors use daily, so summaries are actionable without translation.
Step 6: Set the phone country code
Still in the same section, choose Phone country code. It applies when someone types a local number, such as 0812 3456 7890: the agent turns it into an international number with this country code, so supervisors can contact the user (for example through a WhatsApp link). The default is Indonesia (+62), which is right for Kirana.
Pick the country where most of this agent's users are.

Step 7: Assign supervisors
In Supervisors, add the organization users who can claim and handle escalated conversations:
- Click Add (or the Add supervisor row at the bottom of the list).
- In Organization user, type a name and pick the person. For Atlas, pick Rina Wijaya.
- Optionally, restrict the supervisor with Topic and Area: type a value and press Enter to add it. Leave both on ALL.
- Click Add to confirm.
| Field | Purpose |
|---|---|
| Topic | The subjects this supervisor covers, for example approval limits or site safety |
| Area | The part of the business this supervisor covers, for example a region or business unit |
For your first setup, assign one supervisor with ALL topics and areas, as Kirana does with Rina Wijaya. Add topic and area scopes later, after the first successful test. Each supervisor shows with their topics and areas as pills under the name. To change them, click the row, change the pills, and click Save. The menu (⋮) at the end of the row has Edit and Delete. In the supervisor queue, topics and areas work as filters to focus the list.

Step 8: Save
Click Save at the bottom of the page. A Saved dialog confirms Escalation settings saved.
If something is missing, a Save failed message explains what. For example, with escalation enabled and no supervisor, it says At least one supervisor is required when escalation is enabled. Fix the card and save again.
Like other agent settings, escalation settings are saved as a draft first. The Preview uses them right away; live users get them only after you click Publish (see Preview and Publish Changes).
Step 9: Open the escalation queue
The Escalation queue section at the bottom has two rows:
- Preview queue, with the Open preview queue button: opens the escalation queue for this agent in preview mode. Use it to test your escalation setup before publishing.
- Published queue, with the Open published queue button: opens the live escalation queue for your published agent. Supervisors handle real user escalations here.

Start with Open preview queue. Use the published queue once your draft flow passes end to end (trigger, claim, summary, and completion) and you have published.
Check the result
Before moving to real-time operations, verify:
- Enable escalation is on
- At least one trigger condition exists
- The response message says what you want users to read (or is empty, if you prefer the agent to write its own)
- Phone country code matches the country of most of your users
- At least one supervisor is assigned
- Save succeeds without errors
Then test in the Preview chat. Click the reload button to start a fresh conversation, and send a message that matches your trigger condition. For Atlas:
I need an exception: can I approve a USD 1.2 million project myself? The Regional Director is on leave and the vendor deadline is tomorrow.
Atlas says it cannot approve an exception to the approval limits and asks for a name and phone number, so a person can follow up. Reply with the contact details, in this test Rina Wijaya, 0812 0000 0000. Atlas then confirms that it handed the urgent approval exception request to the Operations duty supervisor, who will continue in the same conversation.

Open the preview queue: a new Pending case with the trigger Decision outside the SOPs appears. The local number 0812 0000 0000 is stored as 6281200000000, thanks to the phone country code.
Next steps
- Next in the journey: Receive and Manage Escalations, to claim and complete the case you just created.
- Notify other tools: Send Escalation Events to a Webhook.