Help Desk vs Service Desk vs ITSM: What’s the Difference? (2026)

The short answer: a help desk fixes problems as users report them. A service desk is the single point of contact between IT and the whole organisation: it handles those fixes too, but also takes service requests through a catalog and connects every ticket to wider IT service management (ITSM) processes such as change, problem and asset management. ITSM is the overall discipline; the service desk is its front door. If you mostly need to answer questions and fix issues, a help desk is enough. If you need to manage services, approvals, assets and changes, you need a service desk.

This guide is for IT managers and support leads deciding how to structure internal support or which kind of tool to buy. It explains the difference in scope, goals, processes, metrics and tools, and when to move from one to the other.

Help desk vs service desk vs ITSM at a glance

What is a help desk?

A help desk is where users go when something does not work. Its job is to take the report, troubleshoot and resolve it, ideally on first contact. It is the right model for many small IT teams and for most customer support teams.

A typical help desk tool offers ticketing across email, chat and phone, assignment and status tracking, a knowledge base and basic reporting. For a full definition and features list, see what is help desk software, and for tools, our best help desk software guide.

What is a service desk?

A service desk is broader. In ITIL terms it is the single point of contact between the service provider (IT) and its users, handling incidents and service requests and communicating with users about changes and outages. The key difference is context: a service desk understands which services a user relies on, what was promised about them (service level agreements), which assets are involved and what has changed recently.

That context comes from the processes behind it:

• Service request management through a catalog: access, software, hardware and onboarding requests with approvals built in.
• Incident management with priorities, SLAs and a major incident procedure.
• Problem management to investigate root causes of repeat incidents.
• Change enablement so users hear about planned work and agents can see recent changes when an issue appears.
• Asset and configuration management linking tickets to devices, applications and services.

What is ITSM?

ITSM (IT service management) is the discipline of running IT as a set of services for the business. It covers everything from defining services and their targets to handling incidents, controlling changes, managing assets and improving over time. The service desk is one part of ITSM, the part users interact with. We explain the processes and the ITIL framework in detail in what is ITSM.

What is the main difference between a help desk and a service desk?

Scope and intent. A help desk is incident-focused: it exists to fix what is broken. A service desk is service-focused: it exists to deliver agreed services, which includes fixing incidents but also fulfilling requests, keeping users informed about changes and outages, and feeding information into problem and change management so fewer things break.

A simple test: if your team mostly answers “can you fix this?”, you run a help desk. If it also regularly handles “can I have this?”, “when will this change happen?” and “why does this keep breaking?”, you run, or need, a service desk.

Is a service desk the same as ITSM?

No. The service desk is a function within ITSM. ITSM also includes processes the service desk rarely owns directly, such as service design, capacity and availability management, release management and supplier management. In practice, many vendors sell “ITSM tools” that include a service desk module, which is why the terms get blurred.

Help desk vs service desk: examples

• A user’s laptop will not connect to Wi-Fi. Both a help desk and a service desk log an incident and fix it. A service desk also checks whether others are affected and whether a recent network change is the cause.
• A new hire needs accounts, a laptop and software. A help desk may handle this by email and memory. A service desk uses a catalog item with an onboarding workflow, approvals and tasks for each team.
• The same app crashes every Monday. A help desk closes each ticket. A service desk links them to a problem record, finds the root cause and tracks a permanent fix through change management.
• A server upgrade is planned for Saturday. A help desk may not know. A service desk sees the change on the schedule and can warn users in advance.

Which one does your organisation need?

A help desk is usually enough when:

• Your IT team is small and your environment is simple.
• Most tickets are break-fix or how-to questions.
• You do not need formal approvals, change control or audit trails.
• You are supporting external customers, not employees. For that, see our ticketing system guide.

You need a service desk when:

• Requests for access, software and equipment make up a large share of tickets.
• You have SLAs to meet or report on.
• Changes to production systems need approval and a record.
• Auditors or security teams ask who approved access or changes.
• You want to link tickets to assets and see which services an issue affects.

How help desks and service desks are staffed

Both usually work in tiers, but a service desk formalises them and connects them to other teams:

• Tier 1 (first line): logs every contact, resolves common issues and requests using knowledge articles, and escalates the rest. In a service desk this tier also fulfils standard catalog requests.
• Tier 2 (second line): specialists for applications, networks or devices who take escalated incidents and more complex requests.
• Tier 3 (third line): engineers, developers or vendors who fix underlying causes, often through problem and change management.
• Shift left: a common service desk goal is to move resolution to earlier tiers and to self-service by writing better knowledge and automating routine requests.

Types of service desk

ITIL and common practice describe several ways to organise a service desk. The right one depends on where your users are and when they work:

• Centralised: one team in one location serves everyone. Easier to manage and measure.
• Local: teams sit close to the users they support, useful where language, regulation or on-site hardware support matters.
• Virtual: agents in different places work as one team through a shared tool and queue.
• Follow the sun: teams in several time zones hand work over so support runs around the clock.

Help desks rarely need this much structure. Once you have more than one location or support outside office hours, a service desk model with shared queues, SLAs and handover rules becomes much easier to run.

Help desk software vs service desk software

Many products sit on a spectrum. Customer-support help desks such as Freshdesk and Zoho Desk focus on ticketing, channels and knowledge. Service desk and ITSM tools such as Freshservice, Jira Service Management, HaloITSM and ManageEngine ServiceDesk Plus add a service catalog, change and problem management, asset management and a CMDB. Enterprise platforms such as ServiceNow extend the same model across HR, facilities and operations.

Features to look for when you move up to a service desk:

• Separate incident and request types with their own SLAs
• A service catalog with approval workflows
• Problem and change modules that link to incidents
• Asset management or CMDB with discovery
• A self-service portal and knowledge base
• Integrations with identity, endpoint management and monitoring tools

We compare the main options in our guide to the best IT service desk software.

How to move from a help desk to a service desk

1. Split incidents from requests in your current tool so you can see how much of your volume is routine.
2. Build a small catalog of the most common requests with forms and approvals.
3. Agree priorities and SLAs with business stakeholders and publish them.
4. Start a change log for production systems, even a simple one, then formalise approvals.
5. Create a basic asset register and link it to tickets. Our IT asset management guide covers tools.
6. Add problem management once you have enough data to spot patterns.
7. Choose a tool that can grow with you, so you can switch on processes as you mature.

Frequently asked questions