Most teams that argue about whether they run a help desk or a service desk are arguing about scope, not software. The tool you bought matters a lot less than what your team has actually agreed to own.
The short answer
A help desk fixes problems: it takes incidents, troubleshoots them and closes tickets. A service desk is broader. It’s the single point of contact for IT services, handling incidents, service requests and changes under ITIL processes and SLAs.
Every service desk includes a help desk. Plenty of help desks never grow into a service desk, though, and for a lot of smaller teams that’s completely fine.
What is a help desk?
A help desk is the break-fix function. Someone’s laptop won’t connect to the VPN, or an app throws an error on login. The help desk’s job is to get that person working again as fast as possible.
It’s reactive by design. Work arrives as a problem, gets logged, gets fixed and gets closed. The metrics follow that shape: first contact resolution, time to resolve and ticket volume. In a lot of mid-market companies the help desk is a shared inbox, a #it-help channel and one or two people who know where everything lives.
What is a service desk?
A service desk is the single point of contact between IT and everyone it supports, which is how ITIL 4 (the framework PeopleCert maintains) describes the service desk practice. It still fixes broken things, but it also takes requests that aren’t problems at all: access to a new app, a laptop for a new hire, a change to a firewall rule.
That’s the real difference. A service desk works from a catalog of services people can ask for. Each one runs through a defined process with an owner and an SLA, and the desk connects to the rest of IT service management: change, asset and knowledge management. You’ve probably seen this in the request types inside ServiceNow, Jira Service Management or Freshservice.
Help desk vs service desk, side by side
Help desk | Service desk | |
|---|---|---|
Main job | Fix problems and restore service | Single point of contact for all IT services |
Request types | Incidents and how-to questions | Incidents, service requests, changes, catalog items |
Process | Usually informal, ticket in and ticket out | Defined ITIL processes with owners and SLAs |
Focus | Reactive, one ticket at a time | Reactive and planned, across the service lifecycle |
Typical metrics | First contact resolution, time to resolve, volume | SLA compliance, request fulfillment time, CSAT |
Who it serves | Employees with IT problems | Employees across IT, and often HR and Ops too |
Typical tooling | Shared inbox, Slack channel, lightweight ticketing | ITSM platform with a catalog, workflows and reporting |
How do help desk, service desk and ITSM fit together?
Think of them as nested. ITSM (IT service management) is the whole discipline of designing, delivering and improving IT services. The service desk is the front door of ITSM, where users meet all of it. The help desk is one room behind that door, the part that handles things that broke.
A lot of the confusion goes away once you stop treating them as competing products. You can run ITSM processes without calling anything a service desk, and you can have a perfectly good help desk without a single ITIL process. When a vendor tells you their help desk is “really a service desk”, ask to see the catalog and the request workflows, because that’s where the difference actually lives.
Which one does your team need?
If almost everything your team handles is break-fix, a help desk is enough. Bolting ITIL processes onto it will slow you down more than it helps. I don’t think a 200-person company needs a change advisory board to approve a printer driver.
You’ve outgrown a help desk when the work stops looking like problems. These are the signals worth watching:
Requests outnumber incidents. Access, onboarding and hardware requests are planned work, and they need approvals and owners, not just a fix.
More than one team takes requests. Once HR, People Ops or Finance start fielding the same kinds of asks, you need shared intake and routing.
Someone asks for evidence. SOC 2 auditors want to see who approved access and when, and a shared inbox can’t give them that.
Requests get lost in DMs. If your team spends real time on asks that never became a ticket, you don’t have a single point of contact yet.
Most mid-market teams hit two or three of these at once, which is usually when the “help desk vs service desk” search starts.
Where does an agentic service desk fit?
There’s now a third model, and it changes the comparison. A help desk logs and fixes; a service desk logs, routes and manages; an agentic service desk also carries out the request.
Say someone asks for access to an app. An agentic service desk checks their role in the HRIS, routes the approval to the right owner, triggers the provisioning in your identity provider and logs the result, all in the conversation where they asked. A human still owns anything irreversible or ambiguous. The agent hands those over with full context instead of guessing.
The catch is that agentic only works on top of service desk fundamentals. If your request types, approvers and owners aren’t defined, an agent has nothing reliable to execute. The order still matters: define the services first, then automate them.
Running a service desk in Slack and Teams with Ravenna
Ravenna gives you the service desk without the portal nobody opens. Requests start where your employees already work, in Slack or Microsoft Teams. They still get request types, routing, approvals and SLAs, just like they would in any ITSM platform.
Our agents answer questions from your existing knowledge and trigger the actual work in Okta, Google Workspace, Workday, BambooHR and Jamf, with human confirmation where you configure it. Ravenna doesn’t create identities or replace your identity provider; it triggers, routes, gates and logs, which also gives your auditors the trail they ask for. And because IT, HR and Ops can share the same front door, the “more than one team takes requests” problem gets solved in the same place.
If you’re trying to work out whether you’ve outgrown your help desk, we’re happy to look at your queue with you, or you can poke around the docs first.
Frequently Asked Questions
What does a service desk analyst do?
A service desk analyst is the first point of contact for IT requests and incidents. They log and classify what comes in and resolve what they can on first contact. The rest goes to the right team with enough context that nobody has to ask the user again. In a service desk they also handle service requests, like access or hardware, through defined workflows.
Is a service desk role IT or non-IT?
It’s an IT role, since the service desk is part of IT service management. That said, the same model now shows up outside IT, in HR and facilities, which is usually called enterprise service management.
Is a service desk the same as ITSM?
No. ITSM is the whole discipline of managing IT services, and the service desk is one practice inside it. The service desk is where users interact with ITSM, which is why the two get mixed up so often.
Can a help desk grow into a service desk?
Yes, and most do it gradually. Start by separating requests from incidents, define your top request types with an owner and an approver, and add SLAs once the volume is predictable. You don’t need to adopt all of ITIL at once to get there.
