Escalations
How tickets get escalated to a human, what the bot does when it happens, and how to work the Escalations queue
An escalation is TicketCord's way of saying "a person needs to look at this ticket". It is raised when the AI cannot answer confidently, when a user asks for a human or presses Talk to Staff, or when an SLA target is missed.
Each escalation appears in a queue on the dashboard's Escalations page, where your team sees what happened and opens the ticket to take over. This page covers the triggers, the settings that control them, and the queue.
Escalations are for servers using the AI features or response targets (Staff → Response targets); a server with neither never sees one.
AI-driven escalations (low confidence and human requests) need the Pro plan or higher, because they come from the knowledge base and ModMail AI. SLA breach escalations need Enterprise. The Escalations page itself is visible on every plan, in the sidebar under More tools on the dashboard home.
To transfer an existing ticket between teams, configure Escalation destinations under Staff and use /escalate, or Escalate in the dashboard ticket menu. Team transfers keep the conversation and are separate from this AI/SLA queue.
What triggers an escalation
| Trigger | Shown in the queue as | When it fires |
|---|---|---|
| Low confidence | AI was unsure | The knowledge-base AI (in a ticket or a ModMail DM) handed the ticket to staff itself: its answer said a person needs to take over, or the customer supplied the details it asked for. A question it simply cannot answer is not escalated; the customer is offered Talk to Staff instead |
| Explicit request | Asked for a person | The user pressed the Talk to Staff button under an AI reply, the AI detected the user asking for a person, or a staff member escalated on the user's behalf |
| SLA breach | Reply target missed | A ticket missed its first-response or resolution target from SLA Management and is not already escalated. Only the first missed target escalates |
The queue's reason filter also lists Upset member, High priority, and No reply. Those reasons exist as categories but no escalations are currently created with them; tone alerts and automatic priority annotate the ticket instead. See Tone alerts and Automatic priority.
What happens in the ticket
What the bot does depends on how the ticket was escalated.
When the AI hands over, or someone presses Talk to Staff
- The bot posts a card in the ticket: Staff Assistance Requested when the user or the AI escalated, or Escalated by Staff when a staff member did. Depending on the ping setting below, the staff role is mentioned.
- The AI stops replying in that ticket so staff and the user are not talking over an assistant. It stays out for the time set in When Atlas can't help (Stay out 7 days by default), then answers again whether or not staff have replied. Stay out for the rest of the ticket keeps it out for good, and Stay quiet once staff reply on the same card keeps it quiet once a staff member answers.
- The escalation is added to Escalations with status Pending.
- When the ticket is closed, its escalation is resolved automatically.
When an SLA target is missed
- Nothing is posted in the ticket, and the escalation itself pings nobody. Your team hears about it from the breach alert, Response target missed, in the Late ticket warnings channel, which mentions the people chosen under Who gets pinged, and from entries in your logs channel. See SLA Management.
- The ticket still counts as escalated, so the AI stops replying in it for the time set in When Atlas can't help, exactly as after a hand-over. A Talk to Staff button on an earlier AI reply now returns "This ticket has already been escalated to staff." (TC015).
- The escalation is added to Escalations with the reason Reply target missed and status Pending.
- When the ticket is closed, its escalation is resolved automatically.
Pressing Talk to Staff a second time returns "This ticket has already been escalated to staff." (TC015). Only the ticket creator or a staff member can press it; anyone else gets "Only the ticket creator or staff members can escalate." (TC002).
Settings that control escalation
AI escalation (knowledge base settings)
Go to AI assistant → Atlas → Answer questions in ticketsGo to AI assistant → Atlas → Answer questions in tickets, on the What Atlas does tab. Atlas always hands a ticket over when it cannot help: it offers the member a Talk to Staff button, and raises an escalation with the reason AI was unsure when the member supplies the details it asked for. Two settings on the card shape what happens next:
| Setting | Allowed values | Default | What it does |
|---|---|---|---|
| When Atlas can't help | Stay out for the rest of the ticket, Stay out 1 day, Stay out 3 days, Stay out 7 days, Stay out 14 days, or Stay out 30 days | Stay out 7 days | How long Atlas stays silent in an escalated ticket before it answers again, whether or not staff have replied. It applies to every escalation, including SLA breaches. Stay out for the rest of the ticket means it never resumes in that ticket |
| Ping staff roles on hand-over | on or off | off | Mention staff when escalating. It pings the roles the ticket's opening ping used: the button's own Ping staff, or Staff roles or Chosen roles from Who gets pinged in Opening tickets → New ticket defaults. When the button uses Ping nobody for this button, the card is posted without a mention. Otherwise (no ping set, or New ticket defaults set to Nobody), all staff roles from Staff → Staff roles are pinged. Off means the card is posted without a mention |
SLA escalation (Response targets settings)
When SLA tracking is on, the first target a ticket misses creates an escalation, unless the ticket is already escalated. Missing its other target later adds no second entry. The Warning alert and Critical alert thresholds and Escalate automatically in Staff → Response targets, and the Late ticket warnings channel in General → Where the bot posts (the logs channel while it is Same as logs), control the alerts your team receives before the breach. See SLA Management.
Go to Staff → Response targetsThe Escalations queue
Escalations lists every escalation across the bots you own or manage, 50 to a page with Previous and Next below the list, and a Refresh button that has a short cooldown. Until the first escalation arrives, the page only explains what will show up there.
Go to EscalationsFilters: a search box ("Search by question, reason or status"), a status filter (All statuses, Pending, Assigned, In progress, Resolved), a reason filter (All reasons, AI was unsure, Upset member, High priority, Reply target missed, Asked for a person, No reply), and a sort order (Newest first, Oldest first, Recently updated, Least recently updated). Up to 100 characters of search text are accepted.
Each card shows the status and reason, a Reply target missed marker when relevant, the priority, when it was escalated, what the Member asked, the AI's answer (click to expand it) with its confidence percentage and a Knowledge base sources list, the bot and server, and an Open button.
| Status | Meaning |
|---|---|
| Pending | Waiting for your team; the ticket is still open |
| Resolved | Closed out automatically because the ticket was closed or deleted |
The status filter also lists Assigned and In progress. Escalations currently go from Pending straight to Resolved when their ticket closes.
Working an escalation
Open it
Click Open on the card. The page's title says why the ticket was handed over (for example "Someone asked for a person."), with the server and when under it.
- What happened shows what the Member asked and the AI's answer.
- Details shows when it was Escalated, the Bot, the Server, How it started (for example "The member pressed Talk to Staff"), who it is Assigned to and the Reply target when there are any, and the Time to resolve once it is resolved.
Handle the ticket
Click Open ticket to jump to the ticket on Tickets, or answer in Discord. Claim the ticket as usual so your team knows who has it.
Close the ticket
Closing the ticket resolves its escalation automatically. The dashboard has no separate claim or resolve button for escalations.
Limits and gotchas
- One escalation per ticket at a time. While a ticket is escalated, further AI hand-overs, another Talk to Staff press, and SLA breaches add no entries. Once Atlas is back after the When Atlas can't help time and answers a question from your help content, the ticket is no longer escalated, so a later hand-over adds a new entry; the earlier one stays Pending until the ticket closes.
- SLA breaches add at most one entry per ticket. A ticket that misses both its first-response and resolution targets has one Reply target missed entry, and a ticket that is already escalated by the AI or Talk to Staff when it misses a target gets none.
- An escalation is resolved only by closing or deleting its ticket. It stays Pending while the ticket is open.
- The AI pause applies to the ticket where the escalation happened, not to the user's other tickets.
- Ping staff roles on hand-over needs a role to ping: with Staff roles (or no opening ping set) at least one staff role in Staff → Staff roles, with Chosen roles at least one of them still in Discord. Otherwise the card is posted without a mention even when the switch is on.
- The queue shows escalations from bots you own and bots where you are dashboard staff. Server members who are staff only in Discord cannot see it.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No escalations ever appear | Answer questions in tickets is off, the plan is below Pro, or there is no help content so the AI never runs | Turn the card on, check the plan, and add sources under AI assistant → Atlas → Sources |
| Staff are not pinged when the AI escalates | Ping staff roles on hand-over is off, the ticket's button uses Ping nobody for this button, or no role to ping is configured | Turn it on, and check the button's Ping staff and Opening tickets → New ticket defaults |
| The AI keeps answering after an escalation | The time in When Atlas can't help passed | Choose a longer time or Stay out for the rest of the ticket, or turn on Stay quiet once staff reply |
| The AI stopped answering in a ticket nobody escalated | The ticket missed an SLA target, which escalates it | Expected. It answers again after the time in When Atlas can't help |
| The AI never comes back to an escalated ticket | When Atlas can't help is set to Stay out for the rest of the ticket | Pick a number of days instead |
| "This ticket has already been escalated to staff." (TC015) | Talk to Staff was pressed on a ticket that is already escalated | Nothing to do; staff have been asked |
| "Only the ticket creator or staff members can escalate." (TC002) | Someone else in the ticket pressed the button | Have the ticket creator or a staff member press it |
| The queue is empty but tickets are clearly unanswered | The triggers are AI and SLA based, not inactivity based | Use SLA Management for time-based alerts, or reminders in Closing tickets → Auto-close and reminders |
Common questions
How does a user ask for a human? By pressing Talk to Staff, which the bot offers when it cannot answer (in ModMail it arrives in the user's DM), or by simply asking for a person, which the AI detects in tickets and ModMail conversations. Both create an escalation with the reason Asked for a person and stop the AI in that ticket.
Does an escalation notify staff in Discord? For AI and Talk to Staff escalations, a card is posted in the ticket. Staff are mentioned only when Ping staff roles on hand-over is on and the ticket's button does not use Ping nobody for this button. An SLA breach escalation posts nothing in the ticket: the Response target missed alert in the Late ticket warnings channel under General → Where the bot posts is the notification, and it mentions the people chosen under Who gets pinged.
Can I turn AI escalation off? Not on its own: Atlas always hands over when it cannot help, so members are never stuck with it. To stop AI answers, and with them AI escalations in tickets, turn off AI assistant → Atlas → Answer questions in tickets. To keep Atlas out of an escalated ticket for good, set When Atlas can't help to Stay out for the rest of the ticket.
When does the AI start answering again after an escalation? When the time in When Atlas can't help (default Stay out 7 days) has passed, whether or not staff replied. This applies after an SLA breach escalation too. Choose Stay out for the rest of the ticket to keep it out of that ticket for good, or turn on Stay quiet once staff reply to keep it quiet once a staff member answers.
A ticket missed both response targets. Why is there only one escalation? SLA breaches escalate a ticket once. The first missed target creates the Reply target missed entry, and the second adds none, although both breaches are still announced in the Late ticket warnings channel. The entry stays Pending until the ticket is closed.
Why does an escalation disappear from Pending when I close the ticket? Closing a ticket resolves its escalation automatically. You do not need to resolve it separately.
Can I claim or resolve an escalation on the dashboard? No. The Escalations page shows what happened and links to the ticket with Open ticket. An escalation is resolved automatically when its ticket is closed or deleted, so close the ticket once it is handled.
Do sentiment or priority create escalations? Not at the moment. Those reasons appear in the filter, but sentiment and priority detection mark the ticket rather than raising an escalation. Only low confidence, human requests, and SLA breaches create queue entries.
Confidence-based handoff rules, the short version
Join our Discord server for support
Was this page helpful?
Last updated on