Escalation rate measures the percentage of customer interactions that are transferred from one level of support to another — typically from AI or frontline agents to specialized or senior agents. It's a key indicator of how well the first point of contact can handle incoming volume.

Escalation rate = (Escalated interactions / Total interactions) x 100

A healthy escalation rate depends on context. For an AI-first support model, some escalation is expected and desirable — the AI should escalate when it encounters situations outside its competence, when the customer requests a human, or when the conversation involves sensitive judgment calls. An escalation rate of zero would indicate either trivial ticket volume or an AI that's overstepping its boundaries.

What matters more than the raw rate is the quality of escalation:

• Clean handoff: Does the escalated agent receive the full context of the AI conversation, or does the customer have to start over?

• Appropriate triggers: Is the AI escalating for the right reasons (genuine complexity, customer distress, policy exceptions) or for the wrong ones (knowledge gaps, integration failures)?

• Resolution at escalation: Are escalated interactions resolved on the first human touch, or do they bounce further?

For CX leaders managing AI deployments, tracking escalation rate over time reveals the AI's learning trajectory. A decreasing escalation rate (with stable CSAT) indicates the AI is getting better at handling more complex cases. A stable rate despite expanding AI scope suggests the AI is being deployed responsibly. A rising rate despite stable scope signals a problem.

Related terms: first contact resolution, AI guardrails, human-in-the-loop