The four-tier support model
A mature MSP runs a four-tier support model where each tier has a defined scope, skill level and escalation path. The model is a funnel — most contacts resolve at L1, the hard ones escalate up, and L4 owns strategy and the relationship. The tiers are not a hierarchy of value but of specialisation; clear handoffs between them are what keeps resolution time and customer satisfaction healthy.
| Tier | Scope | Typical resolution |
|---|---|---|
| L1 | Triage, password resets, known fixes, FAQ | Minutes — first contact |
| L2 | Config changes, app troubleshooting, deeper diagnostics | Hours |
| L3 | Infrastructure, servers, network, identity, security | Hours–days |
| L4 | Strategy, architecture, vendor/escalation, account health | Project cadence |
L1 support best practices
L1 is the front door — speed, accuracy and tone define the customer experience. Build a knowledge base of repeatable fixes (password resets, account unlocks, common app config) so L1 resolves by checklist, not memory. Use templates for ticket creation and response so metadata is consistent. The L1 metric is first-contact resolution and time-to-respond, not deep diagnosis.
- Maintain a checklist knowledge base of repeatable fixes
- Use ticket templates for consistent metadata
- Capture accurate reproduction steps before escalating
- Metric: first-contact resolution and time-to-respond
L2 troubleshooting techniques
L2 owns deeper diagnostics and configuration changes. The discipline is structured troubleshooting: reproduce, isolate, hypothesise, test, document. Use a consistent diagnostic method (the OSI layers, or a known runbook) so the same problem is solved the same way every time. L2 should resolve the majority of non-trivial tickets and only escalate to L3 when the issue is infrastructure, identity or security-level.
1. Reproduce the issue from the user's context
2. Isolate: scope, time, affected users, recent changes
3. Hypothesise: pick the most likely cause
4. Test: one change at a time, observe the result
5. Document: root cause + fix in the ticketL3 infrastructure management
L3 is the infrastructure tier — servers, virtualization, network, identity, databases, security. L3 engineers own the runbooks for infrastructure incidents and changes, and they are the ones who execute the disaster recovery plan. L3 also owns proactive work — patching, capacity, replication health, backup verification — that prevents L1/L2 tickets in the first place.
- Own infrastructure incident and change runbooks
- Execute and verify the disaster recovery plan
- Run proactive maintenance: patching, capacity, replication
- Feed root-cause analysis back into L1/L2 knowledge base
L4 strategic planning
L4 is the architecture and relationship tier — the technical account manager and solution architect. L4 owns the client's technology roadmap, vendor escalations, quarterly business reviews, and the translation between business goals and infrastructure investment. L4 is where recurring incidents become design changes: if L3 keeps fixing the same problem, L4 changes the architecture so it stops happening.
- Own the client technology roadmap and QBRs
- Handle vendor escalations and product gaps
- Convert recurring incidents into architecture changes
- Translate business goals into infrastructure investment
Ticket management and escalation
The PSA (ConnectWise Manage, Autotask, Halo) is the system of record. Every contact is a ticket; every ticket has an owner, priority, SLA and status. Define escalation paths clearly — when L1 cannot resolve in X minutes, it escalates to L2 with full context; L2 to L3 with diagnostics attached. Avoid the anti-pattern of "reassigning" a ticket without context — each handoff must include what was tried and the result.
| Priority | Definition | Response SLA | Resolution SLA |
|---|---|---|---|
| P1 Critical | Business down, no workaround | 15 min | 4 hours |
| P2 High | Major impact, workaround exists | 1 hour | 8 hours |
| P3 Medium | Limited impact | 4 hours | 24 hours |
| P4 Low | Request / minor issue | 1 business day | 5 business days |
SLA management and customer satisfaction
SLAs are the contract; CSAT is the relationship. Track SLA compliance per priority and per client, and review breaches in a weekly NOC meeting — a breach is a process signal, not just a metric. Pair SLA tracking with CSAT surveys after ticket closure, and act on the feedback. The combination — SLA met + high CSAT — is what renews contracts. Under-promise on SLA and over-deliver on experience.
- Track SLA compliance per priority and per client
- Review breaches weekly — they are process signals
- Survey CSAT after closure and act on the feedback
- SLA met + high CSAT is what renews contracts
Lessons learned
- Clear handoffs with context — never reassign without what-was-tried
- L1 resolves by checklist; L2 by structured diagnostic method
- L4 converts recurring incidents into architecture changes
- Track SLA and CSAT together — both are required to renew
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.