What is IT support? Tiers, models & how to choose
Breaks IT support into five tiers with planning estimates for time and cost per ticket, compares six delivery models by company size, lists 2026 prices by model and industry needs, and scores four factors (size, complexity, compliance, budget) to pick a model before choosing a provider.
Updated: November 2026
IT support is the practice of helping users keep technology working - covering troubleshooting, maintenance, security, and proactive management of hardware, software, networks, and cloud services. Modern IT support is delivered across 5 tiers (Tier 0 self-service through Tier 4 vendor support) and 6 delivery models (in-house, outsourced, managed, co-managed, remote, and on-site). The right setup for any company depends on size, technical complexity, regulatory exposure, and budget predictability.
TL;DR
- The short answer. IT support covers troubleshooting, maintenance, user provisioning, patching, network operations and knowledge management.
- Five tiers. Tier 0 self-service through Tier 4 external vendor.
- Six delivery models. In-house, outsourced, managed, co-managed, remote and on-site.
- Cost in 2026. Managed plans run $50-$200 per user monthly for half of MSPs; hourly break-fix runs $101-$200 an hour (Kaseya, 2023).
- How to pick. Under 25 staff favors managed, 25-200 favors co-managed, above 200 favors in-house plus vendor escalation.
What is IT support?
IT support is the function that keeps end users, applications, networks, and infrastructure running for a business. It's the discipline of identifying technology problems, resolving them, and preventing the next batch. It spans frontline ticket handling (Tier 1), deeper troubleshooting (Tier 2), engineering-grade root-cause work (Tier 3), and vendor or self-service layers around the edges.
A working IT support function handles six things:
- Troubleshooting - diagnosing and fixing reported problems with devices, apps, accounts, and connectivity.
- System maintenance - patching, firmware updates, performance tuning, scheduled reboots, hardware refresh.
- User provisioning - onboarding/offboarding, account access, group membership, device setup, license assignment.
- Security and compliance - endpoint protection, identity management, vulnerability patching, audit trails, incident response.
- Network and infrastructure operations - LAN/WAN, Wi-Fi, VPN, firewalls, servers, virtualization, cloud workloads.
- Knowledge management - documentation, runbooks, knowledge base articles, training material - so the same problem doesn't get solved from scratch twice.
In a typical week, a mid-market IT support team works through password resets, device setups and refreshes, network and connectivity tickets, application configuration requests, security alerts and patch cycles, plus the occasional production-impact incident that pulls in Tier 3.
IT support vs help desk vs service desk vs tech support. These get used interchangeably, but each covers a different scope. The help desk is the front line - Tier 1 ticket handling for end-user issues. The service desk is broader: help desk plus service-request fulfilment plus IT process management (per ITIL). IT support is the umbrella term that includes the service desk plus Tier 2/3 engineering, network ops, security, and proactive maintenance. Tech support usually refers to consumer or product-specific help (helping a customer use your product) rather than internal business technology. In US businesses, "IT support" is the usual working term.
Types of IT support services
The IT support stack covers six layers that map to different problems and different skill sets:
End-user support
Day-to-day device, account, and application help for the people doing the work. Password resets, software installs, printer issues, MFA enrollment, mobile-device support, email configuration. Owned by Tier 1 and Tier 2 with self-service handling the long tail.
Help desk and service desk support
The ticketing-and-routing function that processes every inbound request. A help desk handles incident tickets. A service desk handles incidents plus service requests (new laptop, software license, access change) plus problem management. Expert help desk work sits behind the front line: Tier 2 and Tier 3 staff who take escalations, own problem management and write the runbooks Tier 1 follows. Our help desk guide covers the software and KPIs in depth.
Network support
LAN, WAN, Wi-Fi, VPN, firewalls, switches, routers. Connectivity uptime, network performance, traffic shaping, segmentation, secure remote access. Increasingly overlaps with cloud networking (SD-WAN, SASE).
IT infrastructure support
Servers (physical or virtual), virtualization platforms (VMware, Hyper-V, Proxmox), storage, backup infrastructure, on-prem identity (Active Directory), and the cloud equivalents. The deeper plumbing the help desk depends on.
Cloud and SaaS support
Microsoft 365, Google Workspace, AWS, Azure, GCP, plus the long tail of business SaaS - Salesforce, HubSpot, Slack, Atlassian, ERP/CRM stacks. Account management, license optimization, integration setup, security configuration.
Cybersecurity support
Endpoint detection and response (EDR), email security, identity management (Okta, Entra), vulnerability scanning, patching cadence, phishing-simulation training, incident response, compliance reporting. A growing share of IT support work, especially in regulated industries.
Backup, disaster recovery, and business continuity (BCDR)
Backup schedules, restore testing, recovery time objectives (RTO) and recovery point objectives (RPO), DR drills, failover plans. The work that turns "we have backups" into "we can recover."
The 5 IT support tiers explained
IT support is structured into tiers so that simple issues get resolved fast at low cost and complex issues escalate to people who can solve them. A common model has five tiers, T0 through T4; Atlassian, ServiceNow and the HDI framework all describe variants of this structure.
Tier 0 - self-service and AI
Knowledge base articles, FAQ pages, AI chatbots, password-reset portals, automated provisioning. The goal: resolve common requests before a human touches them, so analysts spend their time on work that needs judgment. Track the deflection rate as a share of total inbound and raise it as the knowledge base grows. Tools: ServiceNow KB, Confluence, agentic AI assistants, self-service portals built into ITSM platforms.
Tier 1 - basic help desk
The frontline. Password resets, account unlocks, account creation, basic software installs, common how-to questions, simple device issues. These tickets often close in minutes when the analyst has a runbook. The main KPI is the share of tickets Tier 1 resolves without escalation; when it drops, look at the knowledge base and training first.
Tier 2 - technical support
Deeper troubleshooting. Software configuration issues, complex device problems, application-specific support, mid-level network issues, escalations from Tier 1. These are technicians who can interpret logs, follow runbooks, and work with vendor documentation. Often the rotation slot where Tier 1 analysts grow into engineering tracks.
Tier 3 - expert / engineering support
Root-cause analysis, code or server-side fixes, infrastructure changes, security incidents, architecture decisions. Senior engineers and specialists - network, security, cloud, database, identity. Tickets can run from hours to days depending on complexity. Tier 3 also owns problem management (the ITIL practice of finding root causes after multiple incidents) and runs the post-mortem process. This tier is the most expensive seat in the org and the hardest to hire.
Tier 4 - external / vendor support
OEM support, software vendor support, specialist consultants, escalations to manufacturers. When the problem is in someone else's product and only they can fix it: Microsoft, Apple, Cisco, VMware, Salesforce. Tier 4 is paid via vendor contracts (premier support, enterprise support agreements) and typically has its own SLAs.
Tier comparison table
The time and cost columns are planning estimates for a US team, not published benchmarks; use your own ticket data once you have it.
| Tier | Handled by | Typical issues | Tools | Avg resolution | Cost per ticket (US, 2026) |
|---|---|---|---|---|---|
| T0 | Self-service / AI | Password resets, KB lookups, FAQ | KB, chatbots, agentic AI | Instant - 5 min | $1-$5 |
| T1 | Help desk analysts | Account unlocks, basic how-to, simple installs | ITSM ticketing, remote control | 8-15 min | $15-$30 |
| T2 | Technical analysts | Software config, escalations, complex device issues | ITSM + RMM + remote tools | 30 min - 4 hr | $40-$80 |
| T3 | Senior engineers / specialists | Root-cause, infrastructure, security incidents | Full stack + monitoring + scripting | 4-72 hr | $150-$400 |
| T4 | Vendor / OEM | Product defects, vendor-only fixes | Vendor portals + premier support contracts | Vendor SLA | Bundled in vendor contract |
The tier boundaries matter less than enforcing them. Teams that move fast write down escalation criteria, so a Tier 1 analyst knows when to escalate to Tier 2 and Tier 2 stays out of Tier 1 work. Without those rules, tickets skip tiers and land on the senior engineer's plate.
This r/ITManagers thread from a new IT support manager with a team of two shows how practitioners approach building toward a tiered help desk:
IT support delivery models
The tiers tell you what the work is. The delivery model tells you who does it and where they sit. There are six common models in 2026, plus a 24/7 service-level option that layers on top of any of them.
In-house IT support
A salaried IT team employed directly by the business. Pros: institutional knowledge, instant context, direct cultural alignment, control over tooling and process. Cons: higher cost per supported user at small scale, recruiting overhead, narrow skill coverage (a 3-person team can't be expert in everything from networking to cloud to security), vacation/sickness coverage gaps.
When it fits: over ~200 employees, regulated industries (banking, healthcare, defense) where data control matters, technology-first companies where IT capability is a competitive edge, businesses with deep custom systems that require ongoing development.
Outsourced IT support
External provider handles IT support on hourly, block-hour, or project terms. Pros: flexible, no headcount commitment, broad skill availability via the provider's bench. Cons: less context, slower response than on-site staff, hourly billing can blow up on busy months, weaker incentive to fix root causes (each fix is billable).
When it fits: very small businesses (under 25 employees), seasonal businesses with uneven IT demand, project work (migrations, refreshes, audits), companies in transition where the IT model isn't settled.
Managed IT support (MSP)
A Managed Service Provider takes ongoing responsibility for some or all of a company's IT under a per-user-per-month contract. Pros: predictable cost, proactive monitoring and patching, broad skill coverage, 24/7 NOC typically included, security and tooling baked in. Cons: slower change cadence (vendor pace, not yours), commodity service unless you've picked a good MSP, can feel impersonal at scale. For the tools an MSP runs behind the service, see our MSP platform guide.
When it fits: small to mid-market businesses (10-250 employees) that need full IT capability without building it in-house, growing companies that want to delay hiring an IT director, companies that need compliance and security tooling but can't justify dedicated headcount. Our guide to what an MSP does covers the model in more depth.
Co-managed IT support
A hybrid where in-house IT staff handles the day-to-day work and an external provider fills specific gaps: after-hours coverage, specialist skills (security, cloud, M365), surge capacity for projects, escalation backup. Pros: keeps institutional knowledge in-house while extending team depth, more economical than full in-house at mid-market scale, retains control while offloading what doesn't make sense to build. Cons: requires clear scope (who owns what), can blur escalation paths if not documented.
When it fits: the 25-200 employee window, especially companies with a 1-3 person in-house IT team that needs depth without growing payroll. Our co-managed IT guide covers how to split the work.
Remote IT support
Support delivered from anywhere via remote tools - screen sharing, remote control, chat, video, ticket portal. Pros: lower cost than on-site, faster response than dispatched techs, available across geographies. Cons: can't fix hardware issues, network outages, or anything requiring physical hands. Toolkit: RMM platforms (NinjaOne, Datto, ConnectWise, Atera), remote-control tools (TeamViewer, ScreenConnect, Splashtop), ITSM ticketing.
When it fits: the default mode for help-desk and Tier 2 work in 2026, since hybrid workforces, distributed offices and remote-first companies run almost entirely on remote support. AI remote support software adds triage and draft fixes on top of the remote session; our AI help desk roundup compares the options.
On-site IT support
Technicians physically present at the office. Pros: handles hardware refreshes, network installs, server work, regulated environments where data can't leave the premises, executive support. Cons: highest cost per ticket, geographic constraint, idle time between hands-on work.
When it fits: manufacturing floors, healthcare facilities, financial trading desks, retail point-of-sale rollouts, large hardware refreshes, regulated industries with strict data residency.
24/7 IT support (service-level add-on)
Round-the-clock coverage layered on top of any model above. Delivered via follow-the-sun teams, managed-provider NOCs, or AI-driven Tier 0 with on-call escalation. Cost: expect a higher monthly rate on any model, because someone has to staff nights and weekends; ask providers to price business-hours and 24/7 coverage side by side.
When it fits: e-commerce businesses, healthcare and 911-adjacent services, global teams across time zones, industries with regulatory uptime requirements (financial trading, payment processors).
Delivery model comparison table
| Model | Best for | Cost driver | Coverage | Strength | Watch out for |
|---|---|---|---|---|---|
| In-house | 200+ employees, regulated industries | Salaries + tooling | Business hours by default | Context + control | Skill breadth, vacation coverage |
| Outsourced | <25 employees, project work | Hourly or block-hour | Variable | Flexibility | Hourly cost creep |
| Managed (MSP) | 10-250 employees | $/user/month | Often 24/7 NOC | Predictable cost, broad coverage | Provider quality differs, so check references |
| Co-managed | 25-200 employees | In-house + partial MSP | Hybrid | Best of both | Scope clarity required |
| Remote | Distributed/hybrid workforce | Lower per-ticket | Geographic-agnostic | Speed | Can't do hardware |
| On-site | Manufacturing, healthcare, large refreshes | Per-visit or dedicated | Local + scheduled | Hands-on | Highest cost per ticket |
How much does IT support cost in 2026?
Price depends mostly on the delivery model. These are typical US figures, and our guide to small business IT costs breaks them down by company size:
| Model | Typical 2026 price | What drives it |
|---|---|---|
| Fully managed (MSP) | $50 to $200 per user a month, the range half of MSPs charged (Kaseya, 2023) | Security tooling, 24/7 coverage and compliance scope |
| Hourly break-fix | $101 to $200 an hour, the range 56% of MSPs charged (Kaseya, 2023) | Incident volume, which is hard to predict |
| In-house | About $96,000 a year per help desk technician and $154,000 per systems administrator, loaded | BLS median pay plus benefits, before tooling |
Round-the-clock coverage costs more on any model, and compliance regimes such as HIPAA or PCI add to every line. Our outsourced vs in-house breakdown shows where one hire stops being cheaper than a managed plan.
Hidden costs to budget for
The line items companies tend to underestimate when scoping IT support:
- Onboarding - first 30-60 days of discovery, documentation, tooling deployment
- Projects - migrations, upgrades, refreshes priced separately from the monthly plan
- Tooling pass-through - per-user licenses for security, backup, M365 management
- Training - certifications, vendor courses, ongoing skill development
- Compliance overhead - audit prep, evidence collection, control documentation
For a deeper look at where IT spend tends to leak, our breakdown on reducing IT costs covers the audit framework companies tend to skip.
IT support by industry
Different industries hit different walls. The common need is uptime and security; the difference is which compliance regime, which line-of-business software, and which devices dominate:
| Industry | What shapes IT support | Typical setup |
|---|---|---|
| Healthcare | HIPAA, business associate agreements, EHR platforms such as Epic and athenahealth, medical IoT | Managed or co-managed with a compliance practice |
| Dental and medical practices | Practice-management software (Dentrix, Open Dental, AdvancedMD), imaging systems, HIPAA | Managed |
| Legal | Confidentiality, document management (NetDocuments, iManage), e-discovery, billing systems such as Clio | Managed under 25 attorneys, co-managed above |
| Financial services and accounting | SOX, FINRA and PCI controls, tax software (UltraTax, Lacerte, Drake), tax-season load | Co-managed with audit-trail rigor |
| Construction | Field devices, Procore and Autodesk Construction Cloud, job-site connectivity | Managed with remote-first support |
| Manufacturing | OT and IT convergence (MES, SCADA, PLCs), ERP, network segmentation, line uptime | In-house or co-managed with on-site coverage |
| Nonprofit | Tight budgets, donor systems (Salesforce Nonprofit, Blackbaud), discounted licensing through TechSoup | Co-managed |
| Education | LMS platforms (Canvas, Google Classroom), Chromebook fleets, CIPA and FERPA | Small in-house team plus an MSP |
| Hospitality and restaurants | POS uptime (Toast, Square), kitchen displays, PCI on payment terminals | Managed with on-site dispatch |
| Architecture and engineering | CAD and BIM workstations (AutoCAD, Revit), large-file collaboration, GPU-heavy machines | Managed or co-managed with workstation expertise |
Regulated industries need a provider that can show its own compliance attestations; our guide to IT for regulated industries covers how to split that work.
How to choose the right IT support setup
There's no universally best model. The right one depends on four factors; score yourself on each.
1. Company size and growth trajectory
Size sets the cost-efficiency math. Under 25 employees, one in-house help desk technician at about $96,000 a year loaded costs more than a managed plan for 24 users at $250 per user a month ($72,000 a year), a rate that only 1% of MSPs exceeded in Kaseya's 2023 survey. Above 200, the math flips - dedicated in-house staff become cheaper per user than MSP pricing. The 25-200 band is where co-managed wins.
Growth trajectory matters too: a company growing 30%/year shouldn't commit to in-house hiring during the growth phase, because the model that fits 50 people will break at 150. Managed and co-managed scale more cleanly.
2. Technical complexity and uptime needs
A 50-person SaaS startup with cloud-only infrastructure has different needs than a 50-person manufacturer with a factory floor. Score complexity across: number of locations, network sophistication, line-of-business software depth, hardware variety, integration count.
Uptime needs map to SLA tier: business-hours-only is one price, 24/7 costs more, and sub-15-minute response on priority issues costs more again. Pay for the SLA your business needs.
3. Compliance and data sensitivity
HIPAA, PCI, SOX, FINRA, GDPR, HITRUST, CMMC, ISO 27001 - each compliance regime forces specific controls and audit trails. If you're regulated, the providers who don't have a documented compliance practice are non-starters. In some industries (defense, classified work, certain financial services), the only legal answer is in-house plus vendor escalation.
4. Budget and predictability
Some businesses can absorb variable monthly bills; others need predictable line items. Managed and co-managed give predictability. Hourly outsourced support doesn't. In-house gives the most control over spend but the highest fixed cost.
Quick decision rules
These give a starting answer:
- Under 25 employees, non-regulated: managed IT support
- 25-200 employees, mixed industry: co-managed (in-house generalist + MSP specialists)
- Above 200 employees, regulated or highly technical: in-house + vendor escalation, with co-managed for specific gaps
- Tech-first / SaaS / engineering-heavy: in-house with on-call vendor support
- Single-location, hardware-heavy (manufacturing, medical, hospitality): managed with on-site dispatch
- Distributed workforce, no central office: remote-first managed or co-managed
Treat these as starting points. The decision matrix - size × complexity × compliance × budget - should land each business in a model, then a procurement exercise refines the specific provider or hiring plan.
IT support software: what to look for
The software stack behind IT support has consolidated. A typical team runs one ITSM platform (ticketing, knowledge base and change management), one RMM (endpoint monitoring and remote control), one EDR (security) and a remote-support tool. Picking the ITSM platform is the highest-leverage decision because it shapes every workflow downstream.
What to look for in IT support software:
- Ticketing with intelligent routing and SLA management
- Knowledge base with version control and analytics
- Self-service portal with chatbot/AI capabilities
- Asset management / CMDB
- Integrations with M365, Slack, Teams, identity providers
- Reporting and dashboards (MTTR, FCR, ticket volume, deflection rate)
- Mobile app for technicians
- Open API for custom workflow
- Compliance and audit features
For tool-by-tool comparisons, see our roundups:
- ITSM software compared for larger IT teams
- SMB help desk software for lean teams
- IT ticketing software for ticket-first setups
Disclosure: Flamingo, which publishes this guide, builds OpenFrame.
OpenFrame is open, AI-native infrastructure for IT and security that covers large areas of RMM, PSA, ticketing, patching and documentation in one platform. Its AI agents, Fae and Mingo, take on routine support requests so technicians spend their time on escalations. Pricing is $1 per device a month with 10 million AI tokens included, and a 14-day free trial.
IT support best practices
Seven practices separate IT support teams that scale gracefully from ones that drown when headcount grows:
Build the knowledge base before you scale headcount
Every ticket that gets solved should produce a KB article (or update an existing one). Each article that lets a user fix a problem at Tier 0 frees analyst time, so the same team can support more users as the company grows.
Define and publish SLAs
Response time, resolution time, escalation thresholds. Per priority class. Per service. Make them visible to users so expectations match reality. SLAs that exist only in a contract and not on a dashboard don't shape behavior.
Measure the right KPIs
The IT support KPIs that predict performance, with common internal targets:
- MTTR (Mean Time to Resolve) - by tier and priority
- FCR (First-Contact Resolution) - target 70-80% at Tier 1
- CSAT - quick post-ticket survey, target 85%+
- Ticket volume per analyst per day - 15-30 is healthy
- Cost per ticket - tracked by tier
- T0 deflection rate - target 25%+
These feed the department-level numbers that go to leadership, which our guide to IT department KPIs maps to business objectives.
Automate the repetitive
Password resets, account provisioning, common diagnostics, group memberships. Anything that follows a script should not consume a human ticket. Modern ITSM platforms automate this natively; legacy stacks need scripts and integrations.
Standardize on a CMDB
A Configuration Management Database that tracks what depends on what. Without it, change management becomes guesswork and root-cause analysis takes far longer.
Invest in continuous training
Certifications - ITIL 4 Foundation, HDI Support Center Analyst, CompTIA A+ - signal competence and teach the vocabulary that escalations need. Pick one cert per career stage rather than chasing breadth: Foundation by year two, a Specialist or HDI cert by year four, a senior credential by year seven.
Use AI thoughtfully
Agentic AI for triage, smart routing, draft replies, KB summarization. The trap is treating AI as the resolution layer instead of the assist layer - escalating an AI-generated misdiagnosis to a senior engineer wastes more time than skipping the AI step. Use AI where the cost of a wrong answer is low; keep humans where context matters.
2026 trends shaping IT support
Five shifts changing how IT support gets delivered this year. For the budget side of these trends, our IT budget planning template sets out 2026 benchmarks by category:
-
Agentic AI ticket triage and resolution. LLM-driven agents handle classification, routing, draft responses, and resolution of simple Tier 1 categories, which frees analysts for the tickets that need judgment.
-
Cybersecurity load pushing more SMBs to managed and co-managed. The security stack (EDR, MDR, vulnerability management, identity, email security, compliance) is now hard for an in-house IT team under 50 staff to run alone. The math favors offloading to providers with security as a specialty.
-
Hybrid work permanence means remote support dominates. On-site IT support shrinks to specific use cases (hardware refresh, large installs, regulated environments). Default delivery is remote-first with on-site dispatch when needed.
-
ITSM and ITOM consolidation onto unified platforms. ServiceNow, Atlassian, Freshworks, and Microsoft are converging operations and service management into single panes. Tool-stack reduction is one of the cost levers IT leaders reach for first in 2026, since a mid-market IT team can often drop several tools by consolidating onto a single ITSM/ITOM platform.
-
Outcome-based pricing inching into managed contracts. A few MSPs are experimenting with pricing on resolution outcomes (tickets closed, uptime hit, security events contained) rather than seats. Still niche, but the direction of travel.
Pick the model, then the provider
The right IT support setup matches the company's size, complexity, compliance needs and budget, and leaves room for the next stage of growth. Put early spend into knowledge management and security, and ask each provider why its model fits your situation.
Work the four-factor framework. Pick the model first. Then run a focused procurement against three providers in that model. Comparing like with like makes the math clearer.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/what-is-it-support
Still deciding?
Ask Mingo answers from our docs and customer stories.