Escalation Rules
Define automated actions that fire when AI response confidence falls into specific bands
Escalation rules define automated actions that fire when a conversation's confidence score falls into a specific band. Rules are evaluated in order — the first matching enabled rule wins.

With no enabled rule, no turn triggers an action. Each rule you add appears as a row, evaluated top to bottom.
Escalation runs after the answer has already been delivered. AskRAI answers the user first, and your rules are then evaluated against the record of that turn. Escalation is therefore a follow-up mechanism — it can open a ticket for a human to pick up, but it cannot intercept, alter, or withhold a response the user has already received. To stop an answer, use a guardrail: one on the Input stage refuses the question before an answer is generated, and one on the Output stage can withhold or rewrite the answer before anyone reads it.
Escalation Rules opens to the holders of View escalation rules and Manage escalation rules, Platform Admins among them. View reads the rules read-only and keeps Test Rule, which changes nothing; Manage changes them. Anyone else does not see Escalation Rules in the Admin sidebar. Rules are still evaluated for every user's queries — only authoring them is restricted. Two exceptions are worth knowing: the Sandbox only previews which rule would match and never runs its action, and a turn whose retrieval failed is skipped by rule evaluation entirely, so no ticket opens for it. See Access for the role model.
Rule structure
Each rule consists of:
| Field | Description | Required |
|---|---|---|
| Name | Display label for the rule | Yes |
| Confidence Band | Which band triggers this rule — High, Medium, or Low | Yes |
| Action Type | What happens when the rule matches (see below) | Yes |
| Enabled | Toggle to activate or deactivate the rule without deleting it | Yes |
| Order | Priority position — drag a row, or use its Move up and Move down arrows | Auto |
Each rule row also carries Move up and Move down arrows, which move the rule one place and work from the keyboard, and a trash icon (Remove rule) that deletes the rule from the list. Like every other change on this page, the removal is staged in the browser and only takes effect when you click Save changes.
Action types
A rule takes one of two actions.
| Action | What it does | Configuration |
|---|---|---|
| Create Ticket | Opens a support ticket for a person to follow up | Priority (Default/Low/Medium/High/Critical), Assigned To, Include AI Context |
| Auto Respond | Takes no follow-up action: the answer has been delivered, and nothing else happens | None |
Expand a rule row to configure action-specific settings. Only Create Ticket has any, so an Auto Respond row has nothing to expand.
An Auto Respond rule still claims its band. Only the first enabled rule in a band fires, so an Auto Respond rule placed above a Create Ticket rule in the same band stops that ticket from ever opening. Use one deliberately to say that a band needs no follow-up, and check the order of your cards when a band you expect to escalate opens no tickets. A rule stored under an action this page does not offer shows as Auto Respond and acts as one, band included.
Every ticket a Create Ticket rule opens also sends a notification to everyone who holds Manage escalation rules, Platform Admins among them, whatever its Assigned To.
For Create Ticket, all three settings are honoured. Priority left at Default stores the ticket as Medium, and Assigned To takes a free-text user or group ID (it is copied onto the ticket verbatim and is not validated). Include AI Context is much narrower than its name suggests. It gates only the ticket's AI context, which on a new ticket holds the confidence score alone. It is on by default, and rules created before the setting existed keep including the AI context, so clearing it is an explicit opt-out.
Include AI Context is not a privacy control for the answer. The assistant's answer is copied onto every escalation ticket regardless of the toggle, and is always shown under Answer in the ticket drawer. Clearing the toggle removes only the confidence score, so the AI Confidence badge disappears from the ticket card and drawer. There is no setting that keeps a model-generated answer out of a ticket queue.
Older tickets may also carry a copy of the model's raw response, which the drawer shows as AI Response (Raw) where it differed from the delivered answer. A rule with the toggle cleared kept that copy off the ticket too. New tickets carry no such copy, whatever the toggle.
Apart from the confidence score, a ticket created with Include AI Context cleared is unchanged: it still carries the question, the answer text, the reporting user, the chat (session) id, the priority, the assignee and the originating Audit ID, and renders normally. A rule-created ticket also records the Channel of the conversation that triggered it, so the Channel field in the ticket drawer shows where the conversation took place.
Creating a rule
Open Escalation Rules
Open the Admin plane from the top navigation bar, then select Escalation Rules in the Admin sidebar.
Add a Rule
Click Add Rule. A new rule row appears at the bottom of the list with default values (Low confidence, Create Ticket action).

A new rule row appears with default settings ready to configure.
Configure the Rule
Enter a name, select the confidence band and action type, then expand the row to set action-specific options. Every rule needs a name: while any row's name is blank, Save changes stays disabled and says why, and the blank name is marked on its row once you move on from it. A name the server refuses is marked on its row the same way, and your edits stay on the page to finish.
Reorder if Needed
Drag rule rows, or press a row's Move up or Move down arrow, to change evaluation order. A screen reader announces the rule's new position after each move. The first matching enabled rule is the one that fires — disabled rules are skipped entirely.
Save changes
Click Save changes to persist all rule modifications. Saving replaces the tenant's entire rule set with what is currently on screen — rules you removed are deleted, and reordered rows are stored in their new order.
Discard, next to Save changes, reverts every staged edit — additions, removals, reorders and field changes — back to the last saved state. Both buttons stay disabled until there is something unsaved.
Edits on this page are staged in the browser until you save. With unsaved changes, leaving for another page of the console, whether through a link, a button or your browser's Back button, first opens a Discard Changes? dialog: Keep editing stays on the page, and Discard changes drops the edits and leaves. Reloading or closing the browser tab asks through the browser's own prompt. Click Save changes before you leave.
Testing rules
Click Test Rule to open a dialog where you can set a confidence score (0–100%) and see which rule would match. The test result shows the confidence band the score falls into and, if a rule matches, its name and action type — otherwise it reports that no rule matches. Testing evaluates the last saved rule set, so while the page holds unsaved changes Test Rule is disabled and the page says why: Test Rule checks the saved rules — save or discard your changes to test them.
Rules are evaluated in the order shown. If multiple rules match the same confidence band, only the first enabled rule fires. Drag rows, or use their Move up and Move down arrows, to set the right priority.
Related pages
- Confidence Thresholds — configure the bands that trigger escalation rules
- Tickets — view tickets created by escalation rules
- Conversation Logs — review audit records with escalation decisions