“Tier 1,” “Tier 2” and “Tier 3” are common support labels, but they only help when everyone understands what belongs in each tier. The goal is not to make a user navigate a hierarchy. It is to resolve issues quickly while sending complex work to the right people at the right time.
Tier 1: the front line for everyday support
Tier 1 is the first response for common employee issues. This can include access requests, password help, basic device troubleshooting, software questions, onboarding steps and ticket triage. A strong Tier 1 experience communicates clearly, records useful context and resolves routine issues without unnecessary escalation.
For co-managed teams, Tier 1 may be handled internally, by an MSP service desk or through a shared model based on hours and location.
- User account and access requests.
- Standard laptop, application and printing issues.
- Request intake, documentation and initial troubleshooting.
Tier 2: deeper troubleshooting and operational ownership
Tier 2 support addresses issues that require more technical investigation or access to business systems. These technicians may work on recurring device problems, Microsoft 365 administration, network troubleshooting, application permissions, endpoint security tools and vendor coordination.
In a co-managed model, Tier 2 is frequently shared. Internal team members may retain systems knowledge while the MSP provides coverage, repeatable processes or support for technologies that are not used every day.
- Multi-step incidents that cannot be resolved at first contact.
- Cloud administration, endpoint management and network diagnosis.
- Problem management for recurring issues.
Tier 3: specialist expertise and complex change
Tier 3 support involves senior specialists who can diagnose complex infrastructure issues, design changes and lead projects. This may include firewall architecture, identity design, server and cloud engineering, cybersecurity response, data recovery or advanced vendor escalation.
Most organizations do not need every Tier 3 specialty on payroll. What they need is a reliable path to those skills when the issue calls for them.
- Complex security, network and infrastructure escalations.
- Technology projects, migrations and architecture decisions.
- Root-cause analysis and recovery planning.
Make the escalation path visible
The real value of tiers is clarity. Staff should know where to ask for help, internal IT should know what the MSP owns and both teams should know when a critical issue requires escalation. That definition is part of every effective Co-Managed IT service.
Review the model regularly. New systems, more employees and changing security needs can shift what belongs in each tier.
Talk Through the Right Support Model
Need a clearer support and escalation model? Contact Atomic Guardian to discuss how your internal IT team and MSP support can work together.