// Glossary · support

Support Tier

Also: ticket tier · support level · escalation tier

A classification system for support tickets by complexity, with Tier 1 covering routine queries, Tier 2 handling intermediate debugging, and Tier 3 escalated to engineering or security.

Support tiers are the standard way customer support orgs sort incoming tickets by complexity so each ticket lands with the right level of expertise. Tier 1 covers routine work like password resets, basic how-to questions, billing lookups, and FAQ answers. Tier 2 handles intermediate issues that need product knowledge: configuration help, integration debugging, and product-specific troubleshooting. Tier 3 covers escalated cases that need engineering, security, or executive involvement: data corruption, account compromise, breaking bugs, and contract disputes. The tier model exists because routing every ticket to a senior engineer would be expensive, and routing complex tickets to a generalist would produce bad answers and angry customers.

The volume distribution across tiers follows a predictable shape in most SaaS support orgs. Tier 1 absorbs 60 to 75% of total tickets, Tier 2 handles 20 to 30%, and Tier 3 takes the remaining 5 to 10%. The cost-per-ticket scales sharply by tier. A Tier 1 ticket costs roughly $4 to $8 to resolve. Tier 2 runs $15 to $30. Tier 3 can run $80 to $200 once engineering time is counted. This is why support orgs invest heavily in deflection at Tier 1: even modest improvements in self-service or AI deflection move thousands of tickets out of the queue and free up senior staff for the work that actually needs them.

AI deflection lands first at Tier 1 because the question patterns are repetitive and the answers live in the knowledge base. The AI Support Department standard architecture handles 30 to 50% of Tier 1 volume without human handoff, with answers grounded in RAG against the help center and citations back to source articles. Tier 2 work is harder to automate because it requires reasoning across configurations and product internals, but copilots that draft responses for human agents lift productivity 30 to 60%. Tier 3 stays human because the stakes are too high and the situations too novel for current models to handle without supervision. The tiering model is the foundation for cost-effective AI deployment in support.

// Examples
  • A SaaS support org sees 8,000 tickets a month split 64% Tier 1, 28% Tier 2, and 8% Tier 3, with blended cost per ticket dropping from $18 to $11 after Tier 1 AI deflection lands.
  • A help-center copilot resolves password resets, plan changes, and basic configuration questions at Tier 1, escalating to human agents only when the user requests it or confidence drops below threshold.
  • An engineering escalation queue receives 240 Tier 3 tickets a quarter, with each one assigned a senior engineer for full root-cause analysis and a postmortem when the bug touches production data.
// Common questions
How are support tiers different from priority levels?
Tiers describe ticket complexity and the expertise required to resolve it. Priority describes urgency: P0 for outages, P1 for severe impact, down to P4 for low-priority requests. A Tier 1 ticket can be P0 if it affects many users, and a Tier 3 ticket can be P3 if the impact is limited. Both dimensions matter for routing.
What percentage of tickets should be Tier 1?
60 to 75% of total volume is the typical distribution for SaaS support. Higher percentages mean the product has a steep learning curve or insufficient documentation. Lower percentages mean either the product is unusually intuitive or the team is mis-tiering tickets that should be classified higher.
How much of Tier 1 can AI handle?
Production AI Support Department deployments typically resolve 30 to 50% of Tier 1 volume without human handoff. The remaining Tier 1 cases involve nuance the agent flags for human review. The lift on cost-per-ticket usually lands between 35 and 55% blended across the full ticket queue.
Should AI ever handle Tier 3?
Not directly, in most production deployments. Tier 3 cases involve novel situations, legal exposure, or high-stakes customer relationships where current models cannot be trusted without supervision. AI assists the human engineer through copilots that surface relevant context, but the human stays in control of the response.
// Related terms
// Ready to ship?

EOI runs fractional AI departments for funded teams under 50. Sales, Content, Ops, Support. Live in 14 days on a monthly retainer.