Why escalation tiers matter for ecommerce support
Without escalation tiers, every ticket goes into the same queue and every agent handles everything from a simple WISMO query to a complex fraud claim. This creates three problems: over-qualified agents spend time on simple tickets that could be deflected; under-qualified agents attempt complex tickets that need expertise; and customers with urgent, complicated issues wait in the same queue as people asking for a tracking number.
A tiered escalation structure fixes all three. Tier 1 handles the deflectable majority — instantly, via AI. Tier 2 handles the moderate-complexity tickets that need a human but not a specialist. Tier 3 handles the small percentage of genuinely complex or high-stakes tickets that need expert attention. Each tier is optimized for its ticket type, and routing is automatic.
In a typical ecommerce support queue, 60–70% of contacts are Tier 1 (AI-resolvable), 25–30% are Tier 2 (generalist human), and 5–10% are Tier 3 (specialist). Building and staffing to that distribution is dramatically more efficient than treating all contacts as equivalent.
The three-tier model
Tier 1 requires no human involvement for resolution. Tier 2 requires human judgment but not specialized expertise — a well-trained generalist agent handles it. Tier 3 requires either specialized expertise, elevated authority to approve exceptions, or involvement of a team outside support (finance, legal, operations).
| Tier | Handled by | Target resolution time | Typical volume |
|---|---|---|---|
| Tier 1 — Self-service / AI | AI agent (Bookbag) | < 60 seconds | 60–70% of contacts |
| Tier 2 — Generalist human | Trained support agent | < 10 minutes | 25–30% of contacts |
| Tier 3 — Specialist | Specialist (fraud, high-value, legal) | < 4 hours | 5–10% of contacts |
What belongs in each tier
Ticket categorization is the foundation of effective tiering. Every ticket type in your queue should be assigned a default tier. Here is the standard categorization for ecommerce:
Tier 1 — AI resolves autonomously
Order status and tracking inquiries. Standard return and refund requests within policy. Product questions answerable from the catalog. Shipping timeline and carrier questions. Discount code inquiries and eligibility. FAQ answers from the help center. Subscription status lookups.
Tier 2 — Generalist human agent
Return requests with minor edge cases (borderline eligibility, missing documentation). Wrong or damaged item resolutions within standard policy. Shipping exceptions that need a carrier inquiry. Customer complaints about experience quality. Requests for callbacks or account changes. Any ticket the AI escalated as low-confidence that doesn't require a specialist.
Tier 3 — Specialist or elevated authority
Fraud claims and disputed charges. Requests for large refunds above the generalist approval threshold. Legal or formal complaint language. Safety incidents involving a product. High-value account or bulk order inquiries. Wholesale and partnership inquiries. Escalated complaints that a generalist couldn't resolve.
Building your tier routing rules
Routing rules are the logic that assigns each ticket to the correct tier automatically. Configure them in your AI agent and helpdesk so that tickets land in the right queue without manual triaging.
- 1Set AI confidence thresholds — tickets above your autonomous confidence threshold (e.g., 90%) stay in Tier 1 and the AI resolves them. Tickets that fall below threshold are routed to Tier 2 with an escalation summary.
- 2Add topic-based rules — regardless of AI confidence, certain topics always route to Tier 3: fraud language, legal language, safety incidents, high-value refund requests above your threshold. Configure these as hard rules, not confidence-dependent.
- 3Add sentiment-based routing — high frustration signals detected in the customer's language route directly to a human in Tier 2, bypassing the AI's autonomous resolution attempt. Emotional customers need a human first.
- 4Set order value thresholds — tickets involving orders over a certain value (e.g., $500) route to Tier 2 or Tier 3 by default, even if the question is routine. The financial stakes warrant a human review.
- 5Configure repeat contact routing — if a customer is contacting about a ticket that was already escalated once, route them directly to Tier 2 or 3. Don't make them start again with the AI.
Cross-tier handoffs: keeping context intact
Tier escalations should be invisible to the customer. When a ticket moves from Tier 1 to Tier 2, or from Tier 2 to Tier 3, the receiving agent should arrive fully briefed — not with a blank screen.
- Tier 1 to Tier 2: the AI generates an escalation summary (customer, order, what was tried, why it escalated) that appears as the first item in the Tier 2 agent's view. The customer should not need to re-explain anything.
- Tier 2 to Tier 3: the generalist agent writes a brief handoff note when escalating — what they've done, what they've offered, why Tier 3 is needed. This saves the specialist 5–10 minutes of re-investigation.
- Proactively communicate tier transitions to the customer — 'I'm getting our specialist team involved, they'll follow up within 2 hours' sets an expectation and prevents the customer from feeling passed around.
- Track tier transition time as a metric — the time between a Tier 2 agent deciding to escalate and a Tier 3 agent picking up the ticket. If this exceeds your SLA, your Tier 3 capacity is the bottleneck.
Staffing and capacity for each tier
Once you have the tier model defined, staffing is straightforward: match headcount to tier volume. Most stores understaff Tier 2 (because Tier 1 AI deflection is underestimated) and understaff Tier 3 (because specialists are expensive and stores try to push complex tickets to generalists). Both mistakes create SLA failures.
- 1Calculate Tier 2 volume: multiply your total contact volume by your current escalation rate (or target rate once AI is deployed). That's your human queue. Divide by your target handle time and agent capacity to get headcount.
- 2Tier 3 specialists don't need to be full-time support roles. For small to medium stores, one or two people with elevated authority and specialist knowledge — a team lead or an operations-embedded support specialist — handle the Tier 3 volume effectively.
- 3Cross-train Tier 2 agents on the most common Tier 3 reasons — some escalations reach Tier 3 not because they're complex but because the generalist lacks the authority to approve them. Expanding Tier 2 agents' exception authority reduces Tier 3 load.
- 4Review tier volume quarterly and adjust routing rules. As the AI agent improves, Tier 1 handles more; your human capacity can focus on Tier 2 and 3 quality rather than volume.
Key takeaways
- Escalation tiers match ticket complexity to the right responder: AI for 60–70%, generalist human for 25–30%, specialist for 5–10%.
- Define what belongs in each tier explicitly — every ticket type should have a default tier assignment that drives automatic routing.
- Build routing rules based on AI confidence thresholds, topic triggers, sentiment signals, order value thresholds, and repeat contact flags.
- Cross-tier handoffs must transfer context automatically — receiving agents should never start from zero.
- Staff to tier volume: calculate Tier 2 headcount from your escalation rate and handle time; use team leads as Tier 3 specialists rather than separate roles.