Quick answer: L1, L2 and L3 support are the three tiers of a technical support desk. L1 handles first contact and known fixes, L2 handles deeper troubleshooting that needs system access and product knowledge, and L3 handles defects and design-level problems that need engineers or the vendor. Most companies outsource L1 first, then L2, and keep L3 close to engineering.
The tier model exists for one reason: the cost of handling a ticket rises with the skill of the person handling it. You want every issue solved at the lowest tier that can solve it properly. A desk where senior engineers reset passwords is expensive. A desk where frontline agents guess at database problems is slow and risky.
This guide explains what each tier of L1 L2 L3 support does, the skills and SLAs to expect, how escalation should work, and how to decide which tiers to hand to a partner.
What is L1, L2 and L3 support?
L1 L2 L3 support is a way of sorting incoming issues by complexity and routing each one to the people best placed to fix it. You will also see the tiers written as Tier 1, Tier 2 and Tier 3 support, or as first line, second line and third line. The names differ, the structure is the same.
L0: self-service
L0 is support without a person. It covers the help center, knowledge base articles, in-app guidance, chatbots and automated password resets. It is not always counted as a tier, but it belongs in the model, because every issue a customer solves alone is one that never reaches a paid agent.
L1: first contact and known fixes
L1 is the front door. Agents answer the call, chat or email, log the ticket, confirm who the user is, and resolve anything that has a documented fix.
- Example tickets: password resets, locked accounts, how-to questions, software installs from an approved catalog, basic connectivity checks, known errors with a published workaround.
- Skills: clear communication, patience, disciplined ticket logging, working knowledge of the product and of common operating systems.
- Tools: ticketing or ITSM platform, knowledge base, remote access tool, phone and chat.
L1 agents follow runbooks. That is a strength, not a weakness. Consistency at this tier is what keeps quality predictable across hundreds of contacts a day.
L2: troubleshooting and administration
L2 takes what L1 cannot close. Engineers at this tier investigate instead of following a script.
- Example tickets: a configuration that breaks a workflow, an integration that stopped syncing, permission conflicts, slow performance for one customer, a bug that has to be reproduced before anyone can fix it.
- Skills: administrator-level product knowledge, networking and operating system depth, log reading, some scripting, structured problem solving.
- Tools: admin consoles, remote monitoring and management tools, log viewers, test environments.
L3: engineering and vendor escalation
L3 is where the issue stops being a support problem and becomes an engineering one. The people here are developers, architects or senior infrastructure specialists.
- Example tickets: code defects, data corruption, firmware bugs, architecture limits, failures that require a patch or a case with the hardware or software vendor.
- Skills: deep product internals, root cause analysis, ability to change code or infrastructure.
- Tools: source code, debuggers, production databases, vendor support portals.
L1 vs L2 vs L3 support at a glance
The table below summarizes the tiers. SLA wording here describes the focus of each tier, not a universal standard. Your own targets should come from your priorities and your contract.
| Tier | Handles | SLA focus | Outsource? |
|---|---|---|---|
| L0 | Self-service, bots, help center | Article quality, deflection | Build in-house, partner can maintain |
| L1 | First contact, known fixes | Fast response, first-contact resolution | Usually first to outsource |
| L2 | Troubleshooting, config, admin tasks | Time to resolution, clean escalations | Often outsourced after L1 is stable |
| L3 | Defects, design issues, vendor cases | Time to workaround and permanent fix | Usually kept close to engineering |
How much ticket volume should each tier handle?
In most desks L1 handles the majority of volume, L2 handles a much smaller share, and L3 sees only a thin slice. There is no single correct split. A consumer app with simple questions will resolve nearly everything at L0 and L1. A storage or networking product with complex deployments will push more to L2.
What matters is the direction of travel. A healthy desk moves work down the tiers over time, a practice often called shift-left. Each time L2 solves a recurring issue, the fix should become a knowledge base article that L1 can follow next time. Each time L1 answers the same question fifty times, the answer should move to self-service.
Watch the escalation rate from L1 to L2. If it climbs, one of three things is usually true: the knowledge base is out of date, L1 lacks access to a tool it needs, or a product change has created a new class of issue nobody documented.
What SLAs should you set for each support tier?
Each tier needs different measures, because each tier does a different job.
L1 measures are about speed and completeness at first contact:
- First response time by channel
- First-contact resolution rate
- Correct categorization and priority on every ticket
- Customer satisfaction on resolved contacts
L2 measures are about closing harder problems without bouncing them around:
- Time to resolution by priority
- Reopen rate
- Share of escalations to L3 that were truly L3 issues
- Knowledge articles created or updated
L3 measures are about restoring service and removing the cause:
- Time to workaround for critical incidents
- Time to permanent fix
- Root cause documented and shared back to L1 and L2
Tie every target to a priority matrix. A P1 outage affecting all users and a P4 cosmetic issue should never share one clock. Keep the list short as well. Four or five measures per tier beat fifteen that nobody reads.
How should escalation between tiers work?
Escalation is where L1 L2 L3 support succeeds or fails. Good escalation is fast, rule-based and complete. Poor escalation produces ticket ping-pong, where an issue travels between tiers while the customer waits.
Five rules cover most of it:
- Set clear criteria. Define which issue types L1 may attempt and which go straight to L2. Agents should not have to decide case by case.
- Time-box each tier. If L1 has not resolved a ticket within the agreed window, it moves up. Holding tickets to protect a resolution rate hurts the customer.
- Hand over everything. An escalated ticket must include the steps already tried, error messages, logs, environment details and business impact. The next tier should never have to ask the customer the same questions again.
- Keep one owner. Someone stays accountable for updating the customer, even while engineering works on the fix.
- Close the loop. After every L2 or L3 resolution, ask whether L1 could have fixed it with better documentation or access. If yes, write the article.
Where does the knowledge base fit?
The knowledge base is the mechanism that makes the tier model economical. Without it, every agent depends on memory and on asking colleagues, and tickets drift upward to whoever knows the answer.
Treat documentation as part of the job at every tier. L2 and L3 engineers should write or update an article as part of closing a ticket, not as a side project. L1 agents should flag articles that are wrong or unclear. Customer-facing versions of the most used articles then feed L0.
A partner running your L1 desk should show you how articles are created, reviewed and retired.
Which support tiers should you outsource first?
Start with the tier that is highest in volume and best documented. For nearly every company that is L1.
L1 is the natural first step. The work is repeatable, the runbooks exist or can be written, and the need for evening, weekend and overnight coverage is strongest here. L1 support outsourcing also frees your own engineers from interruptions, which is often the larger benefit.
L2 follows once the partner knows the product. After a few months of L1 work, a good partner has agents ready to step up. Moving L2 across requires proper knowledge transfer, access to admin tools and a tested escalation path into your engineering team. For software companies, our guide on when to outsource L1 and L2 help desks for SaaS products covers the timing in more detail.
L3 usually stays close to engineering. If the fix requires changing your code, the people who own the code should own the ticket. The exception is infrastructure and third-party products. When L3 work means managing servers, networks or vendor cases instead of writing your own software, a specialist partner can run it well.
Budget is part of the decision too. Pricing differs sharply by tier and by model, and we break down the options in our article on IT help desk outsourcing cost and pricing models.
How SSGSERV handles L1 L2 L3 support
We run multi-tier technical support services from delivery centers in Bengaluru and Srinagar, under each client's brand and inside the client's own ticketing tools.
- L1: our L1 helpdesk teams cover voice, chat and email around the clock, with a 30-second first response SLA.
- L2: remote and deskside engineers handle escalated issues, log analysis and administration tasks.
- L3: our L3 engineering and escalation specialists resolve complex issues and manage vendor cases through to closure.
Delivery is certified to ISO 9001 and ISO 27001, and assessed at CMMI Level 3. For companies that sell support as part of their own product, the same teams work as a white-label support operation that customers never see as a third party.
One example: we provide L1 and L2 technical support for a CRM software platform, which gave its users faster ticket turnaround without the client building a larger in-house desk. The full story is in our CRM SaaS support case study.
Frequently asked questions
What is the difference between L1 and L2 support?
L1 resolves known issues using documented steps and handles first contact with the user. L2 investigates issues that have no documented fix, using admin access, logs and deeper product knowledge. The simplest test is whether the agent is following a runbook or diagnosing a new problem.
Is L1 support the same as a help desk?
Mostly, yes. A help desk or service desk is usually the L1 function, the single point of contact that logs, resolves or routes every request. Some service desks also include L2 engineers on the same team, so check how a provider defines the term before comparing quotes.
What is L0 support?
L0 is self-service: knowledge base articles, chatbots, automated resets and in-product help. No human agent is involved. Strong L0 reduces L1 volume, which lowers the total cost of the desk.
Can L3 support be outsourced?
Yes, when the L3 work is infrastructure, platform administration or vendor escalation management. It is harder when L3 means fixing your own source code, because that work depends on your developers and your release process. Many companies outsource L1 and L2 fully and keep a defined handoff into their in-house L3 team.
How many L2 engineers do you need for each L1 agent?
There is no fixed ratio. It depends on product complexity, documentation quality and how much L1 is allowed to do. Measure your escalation rate for a month, then size L2 to clear that volume within your resolution targets.
If you are deciding which tiers to keep and which to hand over, we can map your current ticket mix against the three tiers and show where a partner would help most. Talk to our team to start that review.
Faizan Kanth founded SSGSERV with a vision to build a scalable global delivery model, connecting Bangalore, one of India's leading technology hubs, with Srinagar, an emerging center for skilled tech talent. Under his leadership, SSGSERV has grown into a specialized operations partner for global technology companies, serving clients across the United States, the Middle East, the United Kingdom, and the Philippines. With over a decade of experience across leading global technology, automotive, and business process organizations, Faizan brings deep expertise in operations management, business strategy, and market evaluation to every engagement. A postgraduate of a premier Indian management institute, he is driven by an entrepreneurial approach to solving complex operational challenges for enterprises worldwide. Beyond building SSGSERV, Faizan is focused on positioning Kashmir as a hub for Global Capability Centers, having grown the company's Srinagar delivery center to over 500 professionals and counting.









