What is Tiered Support?

Converge Converge Team
•

Organizing support into levels (L1, L2, L3) based on complexity

What is Tiered Support?

Tiered support organizes your team into levels based on issue complexity. L1 (Tier 1) handles common questions, known issues, and standard requests—password resets, order status, billing inquiries. L2 (Tier 2) handles complex problems requiring deeper product knowledge or system access—integration troubleshooting, advanced configuration, dispute resolution. L3 (Tier 3) typically involves engineering or product teams for bugs, feature requests, and infrastructure issues.

The goal is matching issue complexity to agent expertise. L1 agents handle 60-80% of incoming volume using knowledge bases and templates, freeing specialized L2/L3 agents for the 20-40% that genuinely requires their skills.

Why Tiered Support Matters

Tiered support improves both efficiency and quality. Without tiers, your most skilled (and expensive) agents spend time answering "what are your business hours?" while complex technical issues wait. Proper tiering ensures simple questions get fast answers from L1, and complex issues get expert attention from L2/L3 without delay.

Tiering also creates career paths. L1 agents can grow into L2 roles as they develop expertise, and L2 agents can move into L3 or team lead positions. This progression reduces turnover by giving agents visible growth opportunities within the support organization.

Tiered Support in Practice

An e-commerce company implemented a 3-tier structure: L1 agents handled order status, shipping, and return requests (75% of volume) using quick-reply templates. L2 agents handled payment disputes, product defects, and VIP customers (20% of volume). L3 involved the engineering team for website bugs and integration issues (5% of volume). Average resolution time improved from 8 hours to 3 hours because each tier was optimized for its issue type.

Related Terms

support tierslevel 1 supportEscalation

Related Reading

→ Auto-Routing Configuration → Role Setup → Response Time Optimization → Enterprise Support

Frequently Asked Questions

Most teams need 2 tiers (general and specialist). Add a 3rd tier only if you have technical issues requiring engineering involvement. Startups with under 5 agents usually work best with a flat structure—tiering adds overhead that isn't worth it below a certain team size.
Target 65-80% L1 resolution. Below 60% means L1 agents need better training or tools (knowledge base, templates). Above 85% might mean L1 is attempting issues beyond their capability, risking quality. Track FCR by tier to calibrate.
Create a routing matrix based on issue type, not customer emotion. Angry customers don't automatically need L2—they need a fast, empathetic L1 response. Reserve L2 for genuinely complex problems: issues requiring system access L1 doesn't have, multi-step troubleshooting, or decisions requiring authority L1 lacks.

More Team Terms

Support Agent →Support Team →Queue →Assignment →Handoff →Collision Detection →