Skip to content

Escalation

Adrià Castany 3 min

What is escalation?

Escalation is handing a conversation to somebody with more knowledge or more permissions to resolve it. It can go from one support tier to another, from an automated agent to a person, or from support to engineering, and in every case whoever receives it has not seen the case until that moment.

Also called

handoff, hand-off, transfer

Topic
Support concepts
On this page
  1. Escalating is not reassigning
  2. Why it matters
  3. What has to travel with the conversation
  4. Escalating early is not failing
  5. Escalation from an AI agent
  6. What to measure
  7. Types of escalation
  8. How Intake handles it
  9. Frequently asked questions

Escalating is not reassigning

Reassigning is passing a conversation to a colleague at the same level, for workload or shift reasons.

Escalating is passing it to someone with more knowledge or more permissions. The difference matters when measuring, because many reassignments say something about distribution and many escalations say something about the documentation or the product.

Why it matters

It is the most expensive operation in support and the one done worst.

Expensive because it doubles the time spent and usually interrupts somebody more expensive; done badly because the history almost never travels with the conversation, so the customer explains the problem again and whoever picks it up repeats the diagnosis that had already been made.

What has to travel with the conversation

What the customer asked, what has already been checked, what has been ruled out, and why it stopped.

If any of the four is missing, whoever receives the case starts from zero, and the customer, who has already been waiting a while, has to tell the whole story again.

Escalating early is not failing

An agent wrestling for half an hour with something outside their remit costs more than one who escalates in two minutes.

What gives a bad escalation away is that it arrives with no information, or at the wrong person.

Escalation from an AI agent

It is the least flashy part of an automated agent and the one that shows most.

A system that always answers, even when it does not know, leaves the person with an angry customer and a conversation that has to be undone. One that recognizes its limit and hands the case to a person with everything it found out saves time.

What to measure

The percentage of conversations escalated, where they go, and how many come back down a tier.

A high return rate means the wrong things are being escalated; a high rate of escalations to engineering means there is a product problem.

Types of escalation

They differ in who receives the conversation and why.

  • Functional. To whoever has the knowledge, such as second tier, engineering or billing.
  • Hierarchical. To whoever has the authority, such as a manager who approves an exception.
  • Automatic. Triggered by a rule, such as a deadline about to expire or a high priority.
  • From an AI agent to a person. When the agent does not know, cannot act or the customer asks.

How Intake handles it

Frequently asked questions

When should a ticket be escalated?

When resolving it needs knowledge or permissions the person handling it does not have, or when the customer asks. Setting a maximum time before escalating stops a case circling at the wrong tier.

What information should an escalation include?

The original question, what has already been checked, what has been ruled out, and the reason for the handoff. Without that, whoever receives it repeats work already done.

How does an AI agent escalate a conversation?

It should hand over with the case assembled. The history, the data it looked up and why it stopped. A handoff that only says "let me get a person" is worse than not having intervened.

What is an escalation matrix?

It is the table that says, for each type of case and each severity, who it goes to, through which channel and by when. It stops the decision depending on who is in that day and who they happen to know.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment