Glossary · Customer service

Escalation (customer service)

Moving a customer contact from an automated channel or front-line agent to someone with more authority or skill, ideally with the full context attached.

Escalation in customer service is moving a contact from the channel or person currently handling it, such as a chatbot, an AI agent or a front-line representative, to someone with more skill or authority to resolve it.

Why contacts escalate. Common triggers are a customer asking for a person, a request outside what policy lets the first line approve (a refund above a limit, an exception), repeated failure to understand the request, and situations that call for human judgment or care. For automated channels, escalation is the safety valve. Microsoft’s guidance for customer-facing agents lists “no human handoff” as an anti-pattern, because customers get stuck with no recourse, and recommends handing off to a person with the full context. The CFPB’s 2023 report on chatbots in consumer finance documents customers caught in loops and unable to reach a human.

Measuring it. Copilot Studio’s metrics reference defines escalation rate as the share of engaged sessions handed off through its Escalate topic or a Transfer conversation node. Escalation rate and containment rate are two sides of the same count, and abandonment is a third outcome that neither should hide.

Context is the hard part. An escalation that drops the history makes the customer start over. A good hand-off carries who the customer is, what they asked, what was already tried or promised, and why it escalated.

In agent-to-agent exchanges. A2A has no escalation state of its own. A server agent can keep a task in TASK_STATE_WORKING while a person reviews it, or move it to TASK_STATE_INPUT_REQUIRED or TASK_STATE_AUTH_REQUIRED when it needs more from the client, and the exchange continues on the same task ID. That keeps the calling agent waiting on one task instead of starting over, and keeps the whole exchange in one record the person can read.

Emissar. Emissar’s Handoff module passes a task to a person, with the full exchange attached, into the help desk a support team already uses, and sends the person’s decision back to both agents. Its first connector is Zendesk. Status: In development.

Neighbouring terms. Containment rate counts the contacts that did not escalate. Live agent handoff is the transfer step itself.

Sources

  1. Agent metrics reference (Microsoft Copilot Studio, Microsoft Learn) (accessed )
  2. External engagement pattern (Microsoft Learn, agent adoption patterns) (accessed )
  3. CFPB: Chatbots in consumer finance (6 June 2023) (accessed )
  4. A2A Protocol Specification (task states) (accessed )
  5. Emissar: Handoff module (accessed )