Key takeaways
- A help desk fixes problems one ticket at a time. A service desk is the single front door for everything people need from IT.
- A help desk is usually a subset of a service desk. Both are one part of IT service management (ITSM).
- Customer-facing support teams run help desks. Internal IT teams run service desks.
- A small e-commerce team almost always needs a help desk, not a service desk.
- You can run both, and one tool can sometimes cover both.
A help desk fixes problems. A service desk delivers a service. That one word explains most of the gap: a help desk waits for something to break, while a service desk also handles requests, access and changes that were never broken. A help desk is usually one part of a service desk, and both sit inside ITSM, the discipline of running IT as a service.
People mix the two up because the same software often does both jobs, and because “help desk” also names customer support. This guide gives you the difference in a table, defines each side, and ends with a short test for which one you need.
Run your customer support from one shared inbox
Help desk vs. service desk: the key differences
A help desk is the team and tool that receives problems from users and fixes them, usually as tickets. A service desk is the single point of contact between a service provider and its users for incidents and service requests, backed by wider ITSM processes. The first is about repair. The second is about running a service. In everyday use, “help desk” often means customer-facing support and “service desk” means internal IT.
[TABLE: Help desk vs. service desk at a glance]
| Dimension | Help desk | Service desk |
|---|---|---|
| Audience | Customers, or employees with a fault | Employees and internal stakeholders |
| Scope | Problems and simple questions | Incidents, service requests, access, changes |
| Core job | Fix what broke | Deliver and improve a service |
| Processes | Ticket in, ticket resolved | ITIL-style incident, request, problem and change workflows |
| Typical metrics | Ticket volume, first response time, CSAT | SLA compliance, request fulfillment time, repeat incidents |
| Typical tools | Ticketing, shared inbox, live chat, AI agent | ITSM platform with a service catalog, asset records and approvals |
| Best for | Customer support, small IT teams | Internal IT at mid-size and large companies |
| Where it fails | Same issue returns because nobody owns the root cause | Too heavy for a team of five, slow to set up |
Two rows do most of the work: Audience and Scope. If the people asking for help are your customers, you need a help desk. If they are your colleagues and the requests go beyond fixing faults, you need a service desk.
What is a help desk?
A help desk is a team, and the tool it works in, that receives problems from users and fixes them. The tool logs each problem as a ticket, assigns it and tracks it to closure. The help desk is the first point of contact, so it handles quick fixes and sends harder cases to specialists.
Typical help desk tasks:
- Answer questions about orders, accounts and how a product works
- Log every request as a ticket with an owner and a priority
- Fix common faults, such as a password reset or a failed payment
- Escalate harder problems to a specialist team
- Publish answers in a knowledge base so the same question needs fewer tickets
Where it stops: a help desk reacts. It resolves what users report, and it has no built-in process for planning changes, managing assets or finding the root cause of a problem that keeps coming back. Modern tools add automation and an AI agent that answers the repeat questions, but the model stays the same: a request comes in, and the team resolves it.
What is a service desk?
A service desk is the single point of contact between a service provider, usually the IT team, and the people who use its services. It handles incidents (something is broken) and service requests (something is needed, such as a laptop, an account or access to an app), and it communicates with users throughout. ITIL, a widely used ITSM framework, defines the service desk this way.
Typical service desk tasks:
- Take incidents and requests through one portal, chat or email address
- Offer a service catalog where employees order what they need
- Route approvals, such as access to a finance tool
- Link incidents to problem records and changes
- Track assets and report against service level agreements (SLAs)
Where it stops: a service desk needs defined processes, trained staff and a platform that supports them. A team of five without a formal IT function usually spends more time maintaining the setup than using it. And a service desk built for employees does not fit customer conversations well. It has no shared inbox for Instagram or WhatsApp messages and no live chat widget for your store.
Key differences between a help desk and a service desk
The table gives you the short version. These six differences are where the two actually diverge, and what each means for you.
Audience
A help desk serves whoever has a problem, which is most often a customer. A service desk serves people inside the organization, such as employees and contractors, and sometimes partners.
What this means for you: ask who sends the requests. External customers point to a help desk, internal employees point to a service desk.
Scope
A help desk covers problems and simple questions. A service desk covers those and more: access requests, new equipment, software installs and planned changes.
What this means for you: if more than half of your requests are “I need X” rather than “X is broken”, you have outgrown a plain help desk.
Reactive or proactive
Many guides say a help desk is reactive and a service desk is proactive. That’s a tendency, not a rule. Both respond to requests. The difference is that a service desk is wired into problem management, which looks for the cause behind repeat incidents, and change management, which plans updates so they cause fewer incidents.
What this means for you: a help desk can be proactive too. Reading ticket tags every week and fixing the top cause is the same idea at a smaller scale.
Processes
A help desk usually follows a simple loop: ticket in, answer, ticket closed. A service desk follows ITIL-style workflows, with separate paths for incidents, requests, problems and changes, each with its own approvals and records.
What this means for you: formal workflows pay off when many people touch a request. For a team of three, they add steps without adding value.
Metrics
Help desks track ticket volume, first response time, resolution time and customer satisfaction (CSAT). Service desks track those too, then add SLA compliance, request fulfillment time and how often the same incident returns.
What this means for you: choose metrics that match your promise. A store promising a reply within an hour should watch first response time. An IT team promising laptops in three days should watch fulfillment time.
Cost and setup
A help desk is quick to start. A shared inbox with ticketing can run the same day. A service desk takes longer because you define the catalog, the approval paths and the SLAs before it pays back.
What this means for you: start with the lighter tool and move up when the work demands it, not before.
Use live chat to support your customers in real-time
Where ITSM fits: a ladder, not three options
Help desk, service desk and ITSM are not three competing choices. Read them as a ladder:
- Help desk: fixes problems.
- Service desk: adds requests and a single point of contact.
- ITSM: the whole discipline of designing, delivering and improving IT services, with the service desk as its front door.
ITSM usually includes incident management, problem management, change management, IT asset management and request fulfillment. A service desk touches most of them. A help desk typically covers incident management and simple requests.
How help desks and service desks work together
In a company with both, the two share one flow. The service desk is the front door and the help desk is the first line behind it. Picture one afternoon at an online store:
- A customer writes that an order never arrived. This is a customer problem. The support team works it in its help desk: ticket, tracking check, reply, refund if needed.
- A new support agent starts on Monday and needs a laptop and inbox access. This is an internal request. It goes to the service desk, which runs it through approvals and the asset list.
- The checkout page throws an error twice in one week. The help desk fixes the first case. The service desk side links both incidents to a problem record, so someone finds the root cause.
Tidio’s role is the customer side. Tidio Helpdesk is a customer-facing help desk. It turns conversations into tickets, sets priorities and routes them automatically, and keeps email, Instagram, Messenger, WhatsApp and live chat in one inbox. It isn’t built as an ITIL service desk, so look elsewhere for a service catalog or asset tracking. Most small online stores don’t need either.
Help desk or service desk: which one do you need?
Choose a help desk if:
- Your requests come from customers, not from colleagues
- You need tickets, a shared inbox and fast replies across chat, email and social messages
- Nobody on your team runs formal IT processes
- You want to start this week, not after a long rollout
Choose a service desk if:
- Your requests come from employees: new hires, access, equipment, software
- You have an IT team that manages assets, changes and approvals
- You need to report on SLAs or pass an audit
- A basic help desk is full of requests it can’t route or approve
Use both if you support customers and run an internal IT function. Keep the two in separate queues, because the people, the tone and the metrics differ.
Here is a short test. Answer these three questions in order:
- Who asks for help, customers or employees? Customers: help desk. Employees: go to question 2.
- Is it mostly “this is broken”, or also “I need this”? Mostly broken: a help desk is enough. Both: a service desk.
- Do you have people who own processes such as change approval? Yes: service desk. No: start with a help desk and add structure later.
For a small e-commerce team, the default is a help desk. If you are comparing tools, start with the guides to help desk software, help desk software for small businesses and e-commerce help desks. For internal IT, the enterprise help desk roundup covers tools that go further.
The verdict: match the tool to who asks for help
Ask who you are supporting before you pick a tool. Customers need a help desk. Employees need a service desk. A growing company often needs both, in separate queues. Start with the lightest tool that covers the requests you have today.
FAQ
A help desk fixes problems for users, usually as tickets. A service desk handles problems and requests, and sits inside a wider ITSM process. A help desk is usually a subset of a service desk.
No. ITSM is the discipline of delivering and improving IT services. A service desk is one part of it, the front door where users report incidents and request services.
Rarely. A small business that supports customers needs a help desk with ticketing and a shared inbox. A service desk makes sense once you run internal IT with formal processes, such as approvals and asset tracking.
Sometimes. Many ITSM platforms include a help desk module, and some help desk tools add request forms. Check whether the tool supports the processes you actually run, such as a service catalog and change approvals, before you rely on it for both.
Not exactly. A help desk is the tool and team that handles support requests. Customer service is the wider function that includes the help desk, live chat, phone and self-service. See what customer support covers.
A help desk is usually cheaper to buy, set up and run. A service desk costs more because of the platform, the process design and the training. Some help desk tools have a free plan. Prices change often, so check each vendor’s pricing page.
Set up a customer help desk with chat, email and tickets
