What information should be included in every escalation handoff?

At minimum: customer identity, order number, a description of the issue in the customer's words, what was already attempted (including any actions taken by AI), and the specific reason the current tier couldn't resolve it. Anything less forces the receiving agent to start over.

How do you prevent unnecessary escalations?

By expanding Tier 1 resolution authority and knowledge base coverage. Analyze your escalation queue monthly: if the same issue types keep escalating, either the AI doesn't have the information or the agents don't have the authority to resolve them — both are fixable.

Should customers be able to request escalation at any time?

Yes. Customers who feel they need to speak to a higher authority should be able to request it without friction. Blocking escalation requests erodes trust. The goal is to make Tier 1 resolution so good that most customers never want to escalate — not to make escalation hard.

Glossary

Escalation Path

An escalation path is the documented, operational process by which a customer issue is moved from one support resource to a more capable one — typically from AI or Tier 1 to Tier 2 — including the triggers that initiate escalation, the information transferred, and the SLA at each level.

Book a demo See pricing

What it means

Key insight

An escalation path that loses context is just a transfer — the customer has to repeat themselves, and trust drops with every repeated explanation.

Escalation paths define what happens when the current support resource cannot resolve an issue. A poorly designed escalation path is one of the most common sources of customer frustration: the customer explains their problem, gets transferred, explains again, gets transferred again, and arrives at a specialist who may have only a fraction of the original context. A well-designed escalation path ensures that each transfer includes a complete handoff package — the customer's issue description, what has been attempted, why it couldn't be resolved at the current level, and any relevant account or order data — so the receiving agent can pick up exactly where the previous one left off. Escalation triggers should be clearly defined: which issue types automatically go to Tier 2, which require the customer to explicitly request escalation, and which allow AI to decide based on confidence level.

Why it matters

Escalation experiences have a disproportionate influence on CSAT because they occur at moments of heightened customer frustration. If the escalation compounds the frustration — through lost context, additional wait times, or reaching someone with no more authority than the previous agent — the brand risks a deeply negative experience. Getting escalation paths right protects the brand's most vulnerable support interactions.

How Bookbag helps

Structured Escalation Summaries

Every escalation Bookbag initiates includes a machine-generated summary: customer details, order data, issue description in the customer's own words, steps already taken, and the reason for escalation — everything a Tier 2 agent needs in one view.

Configurable Escalation Triggers

Merchants define exactly which conditions trigger an escalation from Bookbag: customer requests a human, issue type matches an escalation category, confidence score falls below threshold, or refund amount exceeds a limit.

In-Channel Escalation

Bookbag escalates within the same channel — chat session, email thread — so customers don't lose their conversation history when a human agent takes over.

Frequently Asked Questions

See Bookbag in action

Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.