Short answer
Escalation rate is the percentage of customer contacts that get handed off from an automated system or a first-line agent to a human or a higher tier of support. It is the inverse view of containment: where containment counts what stayed inside the bot, escalation counts what had to be passed up.A low escalation rate is not automatically good, and a high one is not automatically bad. A clean escalation, where the AI recognizes its limits and hands off with full context, is a feature. A failed escalation, where the customer had to fight through a bot before reaching a person, is a defect that the same headline number can hide. The shape of the escalation matters more than the count.
Escalation rate vs containment rate at a glance
| Dimension | Escalation rate | Containment rate |
|---|---|---|
| What counts | contacts handed to a human or higher tier | contacts handled end to end by automation |
| Healthy direction | no universal target, clean handoffs matter more | higher only if contained contacts were resolved |
| Misread risk | reading every handoff as failure | mistaking trapped customers for wins |
Aide, the AI platform for customer service, designs escalation as a deliberate boundary, not a leak. Automation is deployed intent by intent and tested before it goes live, so the AI resolves the intents it can and hands off when confidence is low instead of guessing, which means customers are never trapped by an overconfident bot. The goal is not to suppress escalation. It is to make every handoff a good one, carrying customer context so the human starts ahead.