AI Customer Service Escalation: When AI Hands Over
Most escalation rules for AI customer service are written around the AI's confidence: when it is unsure, pass the customer to a person. That rule fails in both directions. The AI is often confidently wrong about a refund, and often unsure about a troubleshooting question it could answer with one more lookup. In the support system from our case study, escalation is decided by what the request needs, not by how sure the AI feels.
Escalate by action, not by confidence
The test is one question: does answering this require someone to do something in the world? If the customer needs information, such as product facts, published policy, an order or shipping status, or troubleshooting steps, the AI answers. If the customer needs an action, such as an invoice, a refund, compensation, a reshipment, an exchange, a cancellation, an order change or an address change, the AI escalates.
This rule is easy to audit. Anyone can read a conversation and say whether it asked for information or for an action. "The AI was unsure" cannot be audited at all.
Chat and email escalate differently
A chat reply goes out the moment it is written and cannot be taken back. An email draft can wait for a person. So the two channels escalate in different ways:
- Chat: when a request needs an action, the AI does not agree to it, does not suggest a remedy and does not quote an amount. It creates a ticket, tells the customer the ticket number and the email address where the team will follow up, and the conversation continues on facts only.
- Email: every email gets a full AI draft with a proposed solution. Escalation here means approval: a person decides on anything that moves money or goods before the reply is sent.
We made the chat rule absolute after chat replies agreed to reissue invoices on their own. In the last 30 days the chat handled 15,445 conversations and agents stepped into the chat window zero times; the requests that needed people reached them as tickets.
Hand over the facts, not the transcript
An escalation that makes the agent reread the whole conversation wastes the time the AI just saved. The ticket the chat creates carries what the AI already established: what the customer wants, the order number, the verified order and shipping status, what the customer has already sent, and what is still missing. The agent starts from a decision, not from a transcript.
The same applies inside email. When a thread has many messages, earlier messages travel as a structured summary with sources and dates, never as raw text. We learned this when a model missed a refund promise buried in a 25-message thread.
Do not escalate to avoid answering
"Let me transfer you to a colleague" and "we are checking with the relevant team" are escalations that give the customer nothing. Our rule for every reply is that it answers what can be answered now and gives the customer a way forward, even when part of the request goes to a person. When the facts point to a likely cause, the reply says what that cause is and what to do next. Passing the customer around is treated as a failure, not as caution.
When a person is already on the case
Once an agent is following a ticket, the AI stops sending replies on that ticket by itself, apart from a short thank-you that closes a finished conversation. Two voices answering the same customer is worse than one slow one.
Do not let escalation block the work
Escalation adds a person, not a gate. Closing a ticket is never a precondition for anything else: an approved solution goes to the execution list when it is approved, whether or not the ticket is closed. And every decision is recorded on its own. An early version allowed one record per ticket and silently dropped a second reshipment on the same ticket.
An escalation checklist
- Write down the actions that need a person. Everything else the AI answers.
- In chat, turn those actions into tickets with a number and a follow-up address.
- In email, draft everything and route actions to approval.
- Send the facts with the escalation, with sources.
- Stop automatic replies once a person is on the case.
For the approval step itself, see human-in-the-loop AI agents; for how escalated work is sorted, see AI ticket triage. The free plan maps your escalation rules in two working days.