Helpdesk Concepts

Escalation

Definition

Escalation is the process of moving a support ticket to a higher tier, a specialist, or a manager when the current agent can't resolve it or when it risks breaching an SLA.

Also known as: ticket escalationtier escalationcase escalation

How it works

Escalation comes in two flavors. Functional (or hierarchical-by-skill) escalation hands a ticket to someone with more expertise — from tier 1 to tier 2, or to an engineer. Hierarchical escalation raises it to a manager, usually because of urgency, a VIP customer, or an approaching SLA deadline.

It can be manual (an agent decides they're stuck) or automatic (a rule escalates any ticket that's been open too long or is about to breach). When an AI agent is involved, a human handoff is itself an escalation — passing the conversation to a person with full context attached.

Why it matters

Escalation is the safety valve that keeps hard tickets from getting stuck. Done well, it moves the right ticket to the right person before the customer is frustrated or an SLA is breached. The escalation rate is also a useful signal — a high rate can mean tier-1 lacks tools or training, or that self-service isn't covering enough.

Frequently asked

What is the difference between functional and hierarchical escalation?

Functional escalation moves a ticket to someone with the right skills or expertise (a specialist or higher tier); hierarchical escalation moves it up the management chain, usually for urgency, priority customers, or SLA risk.

Is an AI-to-human handoff an escalation?

Yes. When an AI agent can't confidently resolve a ticket and passes it to a person — ideally with the full conversation and context — that's a form of escalation.

Related terms

Escalation Rate

Escalation rate is the percentage of support tickets that are escalated beyond the first agent or tier — to a specialist, manager, or higher support level — before being resolved..

Human Handoff

Human handoff is Macha's principle of keeping a person in the loop on anything customer-facing — most concretely through confirmation gates that pause an agent before any write action in interactive chat, and escalation patterns that route hard cases to your team..

SLA Policy

An SLA policy is the configured set of rules inside a help desk that assigns service-level targets — like first-response and resolution times — to tickets based on conditions such as priority, channel, or customer tier..

Tiered Support (L1/L2/L3)

Tiered support is a model that organizes a support team into escalating levels — commonly L1, L2, and L3 — where frontline agents handle simple, high-volume issues and progressively more specialized staff take on harder problems..

Ticket Priority

Ticket priority is a field that ranks how urgently a support ticket needs attention — commonly low, normal, high, and urgent — so agents and automations can work the most important issues first..

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial