Short answer
"Help desk vs service desk" comes down to scope. A helpdesk fixes IT problems as users report them. A service desk is the single point of contact for everything users need from IT, including requests and changes, and it usually contains the helpdesk.
We build SherpaDesk, a helpdesk and PSA (professional services automation) tool a small IT team can run alone.
Key takeaways
A helpdesk is mostly reactive: it restores what broke. A service desk adds a proactive side, looking after the services behind the tickets. The borders overlap. A well-run helpdesk has defined paths to resolution, tracks response and resolution time, and keeps a knowledge base. The service desk column adds coordination around the same tickets.
| Aspect | Helpdesk | Service desk |
|---|---|---|
| Main job | Restore the user's work when something breaks | One front door for every IT service users rely on |
| Time horizon | Today's ticket | Today's ticket and the months ahead |
| Usual processes | Incidents and direct user help | Incidents, requests, changes, problems, knowledge, portal, SLAs, reporting |
| Where it came from | Mainframe-era computing | ITIL and formal ITSM |
| A user is locked out | Reset the password and close the ticket | The same reset, plus the self-service option kept current for the next user |
| Outlook fails every Monday | Restore Outlook for each user who reports it | The same restore, plus a problem record with an owner for the cause |
| A new hire starts Monday | Run the onboarding checklist: laptop, accounts, access | The same checklist, plus coordinating dependent steps with HR, facilities, and vendors |
| Who does the work | The desk resolves the issue or routes it to a specialist | The desk coordinates; network, server, or vendor specialists may do the fix |
In one line each: a helpdesk is a support function. A service desk is the point of contact that also coordinates. ITSM is the discipline of managing IT services, not a third kind of product.
The jump from helpdesk to service desk is a set of habits, not a new department. If you already set up new hires, you run service requests, whatever the desk is called. Growing teams rarely switch overnight: a helpdesk picks up tools and people until it works as a service desk.
The jump from helpdesk to service desk is a set of habits, not a new department.
A helpdesk is the person, team, or tool users go to when something stops working: a failed login, a system outage, a billing error. TechTarget calls it a tactical resource. The work starts when a user reports a problem and ends when they can work again.
The Bureau of Labor Statistics files the people who staff it under computer user support specialists, "also called help-desk technicians", who help users outside IT.
Definition
Helpdesk: the first place users go with an IT problem. It logs the issue as a ticket, fixes it or passes it on, and closes it when the user can work again.
In a small MSP or school district, the helpdesk is often one shared inbox and a phone number. Work comes in by email, text, and the hallway. It's judged on two questions: did the user get a reply, and is the problem gone?
A service desk is the central point of contact between an IT provider and its users. PeopleCert's ITIL 4 certification page says the service desk practice "serves as the central point of contact between the service provider and the users". TechTarget describes it as a wider umbrella with the helpdesk inside, the one place where IT meets the people it serves.
The word "service" is the point. A helpdesk answers "my laptop is broken". A service desk also answers "I need a laptop for Monday's new hire" and "we're moving the firewall on Saturday". Those are requests and changes, not incidents.
TechTarget's description of a service desk covers:
Problem management is the difference you'll feel first. It asks why the same ticket keeps returning, then deals with the cause, for example by planning an upgrade before the next failure.
IT service management (ITSM) is the strategic approach to designing, delivering, managing, and improving the IT services a business runs. It spans a service's whole life, from development and change to incidents, problems, assets, and knowledge. ITSM is a discipline, not a third kind of desk. The service desk is where users meet it.
ITIL is the de facto framework for ITSM, used by many organizations to keep IT in line with what the business needs. It isn't the only one. FitSM is a scaled-down framework for organizations that don't need a fully developed one.
Read it from the inside out: the ticketing system records the work, the helpdesk fixes what breaks, the service desk takes everything users ask for, and ITSM manages it all. Shopping for the tool? See our guide to ticketing system software.
There's no official tier chart for IT. The ladder below follows a TechTarget guide to customer service tiers, which teams adapt to IT, with a university IT department's tier map as the IT example. Some teams add a tier 4 for vendors; others merge self-service into tier 1.
Nobody on your team touches it. The user finds the answer in a knowledge base, FAQ, portal, or chatbot, often for password resets and how-to questions.
Common mistake: letting articles go stale. Technicians read the same articles users do, so an outdated one misleads both.
A generalist takes the common, already-solved issues and follows the written fix. At San José State University's engineering IT group, tier 1 triages each report and solves it by phone where possible: password resets, basic computer and software questions.
Someone with more system access takes configuration problems and anything that needs digging rather than a script. At SJSU, tier 2 is a technician who goes to the office or lab for hardware, software, and printing issues.
The most senior people take the hardest cases and look for the cause behind them. At SJSU, tier 3 is the last stop: network and server requests and issues the earlier tiers couldn't close.
Output: a fix, plus updated documentation that flows to the tiers below.
When the cause sits with a vendor or cloud provider, the fix depends on them. For an MSP, that's the ISP, the line-of-business software vendor, or Microsoft support.
Written triggers. The same TechTarget guide names three kinds: a time limit, a complexity threshold, and the impact on the user. Skill isn't the only reason to hand off. One Spiceworks member expects a tier 2 technician to bring in tier 3 under "priority based pressure", not only when stuck.
The ticket must travel with its history: what the user reported, what's been tried, and what you found. The guide warns that users made to repeat their story at each level judge the whole experience harshly. Another Spiceworks member put it from the technician's side: hand over everything you've tried so the next tier doesn't "start from the ground up".
Our helpdesk SOP templates include a copyable escalation procedure with the trigger, the owner, and what "done" means.
"There isn't anything official," one Spiceworks member wrote; each business builds its own and adapts it over time. Another said tiers "describe scope and ownership more than strict technical ability." Some teams compress them: "T2 does everything T1 can't," wrote one member, and another runs a single tier: "I do the lot!"
So map tiers to people, not job titles. Here's one way for a three-person MSP or district IT team.
| Tier | Who | Takes | Hands off when |
|---|---|---|---|
| Tier 0 | The user, with your portal and articles | Password self-service, Wi-Fi setup, how-to questions | The article doesn't fix it |
| Tier 1 | Whoever is on the queue today | Account access, printers, new-hire setup from a checklist | No documented fix, the time limit passes, or the impact is high |
| Tier 2 | The senior technician | Microsoft 365 configuration, laptop rebuilds, line-of-business apps | A server, network, or security cause is likely |
| Tier 3 | The owner or lead engineer | Network, servers, security incidents, root-cause fixes | The cause sits with a vendor |
Nobody has to climb every rung. Send an outage or a security incident straight to the person who can fix it. At SJSU, tier 1 assigns a ticket it can't solve by phone to tier 2 or tier 3 based on the type of request. The same person can sit in two rows. What matters is that the hand-off rule is written down, not remembered.
To see how much tier 1 resolves itself, take one finished sample: tickets that started at tier 1 and were closed this month. Leave out open and cancelled tickets. Self-service answers fall outside the sample because they didn't start at tier 1. Split the sample in two: closed at tier 1, and closed after a hand-off.
Share of tier 1 tickets resolved without a hand-off
resolved at tier 1 ÷ (resolved at tier 1 + handed off) × 100. Your numbers stay in the browser.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Most small teams need a well-run helpdesk plus the service desk practices their failures point to. TechTarget's guidance is that smaller organizations with limited support needs can often be served by a dedicated helpdesk. The right fit depends on size, infrastructure maturity, business needs, staffing, and budget. These four questions show which practice to add first.
Each "yes" points to one practice; add it to the helpdesk you have. A separate ITSM system earns its setup time only for needs your current tool can't meet. Think multi-step approvals, linked incident, problem, and change records, reporting across services, or coordination across several teams.
An MSP, an internal IT team, and a school district can each land at any of these levels. A district may report mostly broken things, yet summer reimaging and device rollouts are planned changes and requests. New to the MSP model? Start with what an MSP is. Choosing software for internal IT? Our list of IT helpdesk software compares tools for small teams and schools, with prices.
Most mistakes come from copying a large organization's model onto a small team, or from changing the label and nothing else.
Tier labels don't carry over between organizations, especially smaller ones, as one Spiceworks member noted. Another has worked only with roles, never tiers: a "Service/Help desk role" for employees and an infrastructure role for the back end.
Start documentation with the repeat requests you already solve the same way every time. In the TechTarget guide, self-service is the cheapest tier, which is why support teams try to answer questions before they turn into tickets.
How this works in SherpaDesk
A helpdesk and PSA a small IT team can run alone. You can run it as an internal helpdesk for your own staff or as client-facing ticketing for the businesses you support. Routing rules send tickets of a chosen class to one technician, and business rules assign by issue type, organization, or severity to a technician or a group. Unassigned tickets can wait in a group queue until a technician picks them up.
Levels & Escalations move a ticket through your tiers, and from your inbox you can reply with cmd escalate or cmd deescalate. Technicians can attach public knowledgebase articles to their replies. For tier 0, your portal can show the same articles to users.
Base Camp is $45 per agent per month ($40 billed annually), and your first agent is free, forever. 14 days free, no card. No contract. No implementation project. No dedicated admin.
Ticket Management In SherpaDesk →
Who this isn't for
If you need a service catalog, formal change approval, and a named owner for every process, look at a full ITSM suite. With SherpaDesk you get a helpdesk and PSA, not enterprise ITSM. It fits teams that want tickets, tiers, time, and invoices in one place without a dedicated admin.
Not quite, though the terms are often used interchangeably. A helpdesk centers on fixing reported issues fast. A service desk is the wider single point of contact that also runs requests, changes, problem management, and the knowledge base. A helpdesk is often seen as a subset of a service desk. See the comparison table.
One practice at a time, starting where work keeps failing. Give requests their own type and checklist, have one person own each repeat issue until its cause is fixed, write down escalation triggers, and turn fixed issues into articles. Most teams grow into a service desk by adding tools and people over time. See which one you need.
Tier 1 is the first person a user reaches. They take common issues that already have a written fix and pass the rest up. At one university IT group, typical tier 1 work is password resets and basic computer and software questions, solved by phone where possible. Where each tier stops differs from team to team.
Level 1 follows written fixes. Level 2 has more system access and takes configuration problems and issues that need digging rather than a script. The line moves between organizations: one Spiceworks member said tier 2 at their IT company does "everything T1 can't". See how tiers work.
No. ITIL is the de facto framework for IT service management, used by many organizations, but it isn't required. FitSM is a scaled-down framework for organizations that don't need a fully developed one. Our advice for a team of three: start with routing, written escalation triggers, and a knowledge base, and add more only when a failure calls for it.
Patrick co-founded SherpaDesk. Two founders who ran their own MSP have built it since 2001.