It is for IT managers, product owners and operations leads who want to hand part of their application support to a partner without tickets bouncing between teams. Netbase keeps live software running through application maintenance and support and moves ageing systems onto supported technology through legacy modernization.
In this guide
- What do L1, L2 and L3 mean for a business application?
- Who owns what at each tier when support is outsourced?
- When should a ticket move from L1 to L2, and from L2 to L3?
- How can L1, L2 and L3 be split with a partner?
- How to set up tiered support with a partner
- How do you know the tier split is wrong?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: other ways to organise support and how to choose
- Limits of this guide
- Frequently asked questions
- Next step
What do L1, L2 and L3 mean for a business application?
The tier labels come from help-desk practice. A common description of multi-tiered technical support has Tier 1 gather information and resolve basic issues, Tier 2 investigate more complex problems, and Tier 3 handle the hardest cases with subject-matter experts, often the developers who know the back end. For a business application, the useful definition is not seniority but what each tier is allowed to touch.
- L1, first response. Receives the ticket, confirms who is affected, applies known fixes from the knowledge base and routes everything else. Works from the application's user interface and the ticket tool, with no code or database access.
- L2, application support. Diagnoses problems L1 cannot fix: reads logs and monitoring, reproduces the issue on a test copy, corrects configuration and data through approved scripts, and decides whether a code change is needed. Needs read access to logs and controlled access to data.
- L3, engineering. Changes code, schema or infrastructure, writes the regression test and ships the fix through the normal release route. Needs write access to the repository and release rights.
The access line is the real boundary: a tier that can read logs but not change code cannot fix a defect. Splitting tiers between two companies works when the access each side holds matches the work each side owns.
Who owns what at each tier when support is outsourced?
Every ticket needs one accountable owner at any moment, even when people from both companies work on it. The matrix below names the owner, the access the tier needs and the condition that ends its part of the ticket.
-
L1
- Owns
- Intake, severity, user contact, known fixes, routing
- Access needed
- Ticket tool, knowledge base, application front end
- Exit condition
- Fixed with a known article, or escalated with the template complete
-
L2
- Owns
- Diagnosis, reproduction, configuration and data fixes, workarounds
- Access needed
- Logs, monitoring, test copy, approved data scripts
- Exit condition
- Fixed without code, workaround in place, or escalated with a reproduction
-
L3
- Owns
- Code, schema and infrastructure changes, regression tests, releases
- Access needed
- Repository, CI pipeline, release rights
- Exit condition
- Fix released and verified, knowledge article handed back to L1
-
Service owner
- Owns
- Severity disputes, priorities, budget, vendor escalation
- Access needed
- Contract, reports, tracker
- Exit condition
- Decision recorded on the ticket
The service owner row matters most in an outsourced model. When L1 sits with a partner and L3 with your team, someone must settle disputes about severity and priority without a meeting each time. Keep that role on the client side, because it holds the budget and the business priorities.
When should a ticket move from L1 to L2, and from L2 to L3?
Escalation works when the triggers are written down and a ticket that meets one moves without anyone asking permission. Base triggers on evidence and time, not on confidence.
-
L1
- To
- L2
- Escalate when
- No knowledge article fits; the same symptom reaches several users; the issue touches payments, orders or personal data; the L1 time limit for the severity passes
- Hand over with
- User, steps, screenshots, time, severity, articles tried
-
L2
- To
- L3
- Escalate when
- The cause is in code, schema or infrastructure; a data fix would need a change to code; the workaround fails or creates risk
- Hand over with
- Reproduction steps on a test copy, log extract, suspected area
-
Any tier
- To
- Service owner
- Escalate when
- Severity is disputed; a fix needs budget, a release outside the calendar or another vendor
- Hand over with
- Options with impact, the decision needed
Atlassian describes three types of escalation policy: hierarchical (by seniority), functional (by expertise) and automatic (by rule, when an alert is not acknowledged in time). Tier escalation in application support is functional: the ticket moves to the people with the skills and access to fix it. Add an automatic rule as well, so a ticket that waits past its limit moves even when nobody acts.
Escalation also needs a route back down. When L3 ships a fix, it writes or updates the knowledge article, and L1 confirms with the user and closes the ticket. The Consortium for Service Innovation's Knowledge-Centered Service method makes this capture part of the daily work, so answers found at L2 and L3 become L1 fixes the next time.
How can L1, L2 and L3 be split with a partner?
The split depends on who owns the code, who can release, who may see production data, and how many tickets arrive. Four patterns cover most cases.
| Option | Partner runs | You keep | Choose it when |
|---|---|---|---|
| Keep all tiers | Nothing | L1 to L3 | Volume is low and one team knows the code; not when fixes wait behind feature work |
| Outsource L1 | Intake, known fixes, routing | L2, L3, releases | Many repeat questions; not when most tickets need code or data access |
| Outsource L1 and L2 | Intake, diagnosis, configuration and data fixes | L3, releases | The application is stable and documented; not when logs or data cannot be shared |
| Outsource L1 to L3 | All tiers under an agreed scope | Service owner, priorities, final approval | The partner built or took over the application; not when nobody can review its changes |
L2 is the hardest boundary to draw, because it needs application knowledge and data access. If you outsource L2 but keep L3, give the partner's L2 a reproduction environment and a direct channel to your engineers; otherwise L2 escalates everything, and you pay for an extra hop.
How to set up tiered support with a partner
-
List ticket categories
Take three months of tickets, group them by symptom, and mark which categories L1 could close with an article.
-
Write the tier matrix
Use the table above, fill in your owners and access, and name the service owner.
-
Agree severity and time limits per tier
Put severity levels, response and resolution targets and escalation contacts in the contract, not in a slide deck.
-
Grant access by tier
L1 gets the ticket tool and knowledge base, L2 gets read access to logs and a test copy, L3 gets the repository and release rights; review access when people change.
-
Use one ticket tool for both companies
A ticket keeps its history across tiers, so nobody asks the user to repeat the problem.
-
Write the first knowledge articles together
Start with the categories from step 1 so L1 can close tickets from day one.
-
Review the split monthly
Look at the measures below and move categories between tiers when the numbers say so.
How do you know the tier split is wrong?
Watch a few measures by tier, not across the whole team. A high bounce rate, where tickets go back down because the hand-over lacked information, shows a weak escalation template. A high reopen rate after L1 closes tickets shows known fixes that do not work. A low share of tickets L1 resolves in a category that should be routine shows missing knowledge articles. When L2 escalates almost everything to L3, L2 lacks the access or the knowledge to diagnose, and the extra tier adds delay rather than capacity.
Major incidents are different from tickets. During an outage, tier boundaries give way to one incident lead and clear roles; the Google SRE book's chapter on managing incidents separates incident command, operations, communication and planning so responders do not trip over each other. Write in the contract who leads an incident when the partner detects it first.
Where AI fits
AI helps most at L1 and L2, where volume is high. A model can suggest a category and severity from the ticket text, find matching knowledge articles, summarise logs around an error for L2, and draft the knowledge article after L3 ships a fix. Engineers and support staff still confirm severity, decide every escalation, approve every data or code change and check that drafted articles are correct before L1 relies on them. Netbase works with the major commercial and open-source AI tools and models, chosen per project.
- Available capability
AI-assisted ticket triage under human review
Suggested categories and drafted articles are checked by a person before use; not yet tied to a published support case.
What delivery record exists, and what does not
Netbase runs, maintains and upgrades what it builds, remotely and alongside the client's in-house team, under an agreed support scope, with response targets set per contract. Engagement models include on-demand support and fully managed delivery, and most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly team retainer and KPI-linked models are also offered.
Progress is tracked in Jira, Redmine, Trello or GitHub, where clients can check it at any time, and the project workflow ends in delivery and maintenance under contract. Delivery teams combine business analysts, project managers, solution architects, developers, QA and UI/UX. Published security practices include role-based access control and secure code review, with SLAs on request.
Netbase delivered the Netztech migration from Magento 1 to Magento 2; see the Netztech record. No ticket volume, resolution rate, response time or other support result is published, and none is claimed here.
Alternatives: other ways to organise support and how to choose
- One team, no tiers. The engineers who build the application also answer every ticket. Choose it for a small internal tool with few users; it breaks down when tickets interrupt feature work every day.
- Shared operations without a tier split. Both teams work the same queue under a written ownership matrix; see shared operations with an in-house team. Choose it when the partner adds capacity on named duties rather than taking a tier.
- On-call rota for incidents only. A small team covers out-of-hours incidents and leaves normal tickets to office hours; see on-call and incident response for small engineering teams.
Choose by who owns the code, how many tickets repeat and how much access you can give a partner. Once tickets reach engineering, a bug-fix workflow with regression tests keeps fixes from coming back, and an end-of-life runtime review shows whether old versions drive the ticket load.
Limits of this guide
- The triggers and exit conditions are a starting point; set your own in the support agreement.
- It covers application support, not desktop, network or hardware help desks.
- It does not set response or resolution targets, which depend on your business and are agreed per contract.
Plan the next step with a Netbase consultant
Frequently asked questions
Most companies start with L1, because intake and known fixes need the least access to code and data. Move L2 to the partner once its knowledge articles and diagnosis notes are good enough, and keep L3 with whoever owns and releases the code.
Yes, if the partner built the application or has taken it over and holds the access each tier needs. Keep a service owner on your side who sets priorities, settles severity disputes and approves releases.
It should include the affected users, steps to reproduce, screenshots or error messages, the time it started, the severity and the knowledge articles already tried. A ticket that arrives without this goes back to L1 and the clock keeps running.
Name one incident lead in the contract for each case, for example the partner when it detects the incident and your team when a release caused it. During the incident, tier boundaries give way to that lead and clear roles.
Next step
If you plan to outsource part of the support for a live application and want the tier split and escalation written down before you sign, book a solution review.
Related services and solutions
AI-assisted legacy modernization that keeps your orders and data safe Netbase provides legacy application modernization services for commerce and operations teams to move ageing platforms, such as Magento 1 stores, onto supported technology without losing orders, customers or data. AI speeds up code analysis and data mapping; every migration runs on a written, human-approved plan with rehearsal, staged cut-over and rollback, proven by Netztech's move to Magento 2.
Learn More
Application maintenance and support for live web, mobile and business software Netbase maintains and supports software that is already live: web platforms, online stores, mobile apps, ERP and CRM systems and internal tools, including software another vendor built. We take it over after a code and environment review, then fix defects, keep frameworks current, monitor it, make small changes and report monthly, under service levels agreed in your contract.
Learn More
Multi-vendor marketplace development: vendors, catalog, payouts and AI search on one platform A multi-vendor marketplace is a commerce platform where many independent sellers list, sell and get paid through one storefront. Netbase's marketplace solution covers vendor onboarding, a shared catalog, split payments and payouts, with AI for search, listing enrichment and fraud checks. For an EU fashion-tech marketplace, Netbase's work grew gross merchandise value (GMV) and cut vendor onboarding time.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.