Why Tiered Support Matters
Most SMEs run a flat IT support model: one or two IT staff handle everything from password resets to server failures. This creates two problems:
- 1Senior engineers waste time on trivial issues - a ₹80,000/month engineer spending 40% of their time on password resets is a ₹32,000/month waste.
- 2Complex issues get delayed - when the same person handles L1 and L3, critical infrastructure problems queue behind routine requests.
A tiered model fixes both.
The Three Tiers
L1 - Service Desk (First Contact)
Who: Junior IT staff or trained non-IT staff using a knowledge base
Handles: ~70–80% of all tickets
Target resolution time: < 2 hours
Typical L1 issues:
- •Password resets and account unlocks
- •Software installation from approved catalogue
- •Printer and peripheral setup
- •Email configuration (Outlook, Gmail)
- •VPN connectivity (standard troubleshooting)
- •Hardware swap for known-faulty devices
L1 success factors:
- •A well-maintained knowledge base with step-by-step guides
- •Clear escalation criteria (if not resolved in 30 min → escalate)
- •Access to remote desktop tools for guided resolution
- •Canned responses for top-20 ticket types
L2 - Technical Support (Specialist)
Who: Experienced IT staff with system administration skills
Handles: ~15–25% of all tickets (escalated from L1)
Target resolution time: < 8 hours
Typical L2 issues:
- •Active Directory / Google Workspace administration
- •Network configuration (VLAN, firewall rules)
- •Server performance issues
- •Application errors requiring log analysis
- •Complex hardware failures requiring diagnosis
- •Security incidents (malware, suspicious activity)
L2 success factors:
- •Full access to server and network infrastructure
- •Monitoring dashboards (Grafana, Zabbix, or equivalent)
- •Runbooks for common L2 scenarios
- •Clear handoff protocol from L1 (full context, steps already tried)
L3 - Engineering / Vendor Escalation
Who: Senior engineers, architects, or vendor support
Handles: ~2–5% of all tickets
Target resolution time: Varies (hours to days)
Typical L3 issues:
- •Infrastructure outages affecting multiple users
- •Database corruption or data recovery
- •Custom application bugs requiring code changes
- •Vendor-specific issues (ERP, CRM, cloud provider)
- •Security breaches requiring forensic investigation
Escalation Criteria
L1 → L2 Escalation Triggers
- •Issue not resolved within 30 minutes of active troubleshooting
- •Issue requires admin-level system access
- •Issue affects more than 3 users
- •Issue involves data loss or security concern
- •Customer is a senior manager or executive (VIP handling)
L2 → L3 Escalation Triggers
- •Issue not resolved within 4 hours
- •Root cause requires infrastructure change or code deployment
- •Issue is a recurring problem (3rd occurrence in 30 days)
- •Vendor involvement required
Knowledge Base Strategy
The L1 resolution rate is directly proportional to knowledge base quality. Target: one article per top-50 ticket type.
Article Structure
Each KB article should include:
- 1Symptom description (what the user sees)
- 2Step-by-step resolution (numbered, with screenshots)
- 3Escalation trigger (when to stop and escalate)
- 4Related articles
Maintenance
- •Review articles with > 3 "not helpful" ratings monthly
- •Add new article within 48 hours of any novel L2 resolution
- •Archive articles for retired software/hardware
Cost Comparison by Tier
| Tier | Avg. Salary (India) | Cost per Ticket | Tickets Handled |
|---|---|---|---|
| L1 | ₹25,000–₹40,000/mo | ₹80–₹150 | 70–80% |
| L2 | ₹50,000–₹80,000/mo | ₹300–₹600 | 15–25% |
| L3 | ₹80,000–₹1,50,000/mo | ₹800–₹2,000 | 2–5% |
The business case: Improving L1 resolution rate from 60% to 80% reduces average cost per ticket by ~35%.
Implementation Roadmap
Month 1
- •Categorise last 3 months of tickets by type and resolution tier
- •Identify top-20 L1-resolvable ticket types
- •Write KB articles for top-20 types
Month 2
- •Train L1 staff on KB usage and escalation criteria
- •Implement ticket routing rules in ITSM
- •Set up L1/L2/L3 queues with separate SLAs
Month 3
- •Measure L1 resolution rate (target: > 70%)
- •Review escalation patterns - identify tickets that should have been resolved at L1
- •Expand KB to top-50 ticket types