The short answer on help desk vs service desk: a help desk fixes problems people bring to it, and a service desk manages a whole catalogue of services, including requests, changes and the assets behind them, usually following the ITIL framework. A help desk is reactive and narrow. A service desk is broader and includes help desk work as one part.
Which one you need depends mostly on who you support. If your team answers customers about orders, accounts and how your product works, you need a customer help desk, or something lighter. If you run IT for your own employees, with laptops to issue, software access to approve and changes to track, a service desk starts to make sense once the company is big enough to need the process.
Two meanings of "help desk"
Much of the confusion comes from the word itself. It is used for two different jobs:
- An IT help desk supports a company's own employees: password resets, broken laptops, printer problems, VPN access. This is the help desk that gets compared with a service desk in IT circles.
- A customer service help desk supports a company's customers: "where is my order", "how do I export my data", refund requests. Zendesk, Freshdesk and Help Scout all call themselves help desks in this sense.
Service desk, in turn, is almost always an IT term. When an article says a service desk is "more strategic" than a help desk, it is comparing two ways of running internal IT support. If you are a five-person team answering customers, most of that comparison is about someone else's job, and the useful question becomes how much process your support actually needs.
Help desk vs service desk side by side
| Help desk | Service desk | |
|---|---|---|
| Main job | Fix the problem someone reports | Deliver and manage IT services end to end |
| Approach | Reactive: wait for an issue, solve it | Reactive and proactive: also prevents repeat issues |
| Who it serves | Customers or employees with a problem | Mostly employees, as users of IT services |
| Typical work | Questions, bugs, incidents | Incidents, service requests, changes, problems, assets |
| Framework | Usually none required | Usually ITIL, as part of ITSM |
| Channels | Email, chat, messaging, phone | Self-service portal, email, chat, phone |
| AI | Answers repeat customer questions, drafts replies | Routes and classifies requests, suggests fixes |
| Setup for a small team | Hours to days | Weeks, since catalogues, approvals and asset data come first |
| Pricing model | Mostly per agent seat, some per workspace | Mostly per agent seat, with asset and ITSM tiers |
| Example tools | Zendesk, Freshdesk, Help Scout | Freshservice, Jira Service Management, ServiceNow |
The pattern across every row: a service desk does what a help desk does, then adds structure for planned work. That structure is valuable when an IT team manages hundreds of devices and dozens of systems. For a customer support team it is mostly overhead.
Where ITIL and ITSM come in
ITSM (IT service management) is the discipline of running IT as a set of services for the rest of the organisation. ITIL is the most widely used framework for it, a collection of practices covering how incidents, requests, changes and problems should be handled.
The service desk is one of those practices. ITIL 4 gives its purpose as capturing demand for incident resolution and service requests, and treats the desk as the single point of contact between the IT provider and all of its users, as summarised in this ITIL 4 service desk guide. That's why service desk tools come with concepts a help desk doesn't need:
- Service catalogue: a menu of things employees can request, like a new laptop or access to a system, each with its own form and approval steps.
- Change management: a record and approval process before anyone changes a production system.
- Problem management: finding the root cause behind repeated incidents, so the same outage doesn't keep coming back.
- Asset and configuration management: knowing which hardware and software exists, who has it and how it connects.
- SLAs per request type: separate response and resolution targets for each category of request.
None of this is required to call something a help desk. A help desk can grow some of these habits over time, such as tracking repeat issues or writing down SLAs, without adopting ITIL.
Who you support decides most of it
The single most useful question is who sends the requests.
If it's customers, they want a fast, friendly answer on the channel they already use, whether that's chat on your website, email or a messaging app. They will never fill in a service request form or care about your change process. What matters is response time, one history per customer and a clean way to hand a conversation between teammates. That's help desk territory, and for small teams often just a well-run shared inbox.
If it's employees, the trade-off changes. Internal users can be asked to use a portal, requests repeat in predictable categories (new hire setup, access, hardware), and the IT team needs approvals and an audit trail. A lightweight IT help desk works for a small company. Once you need structured requests, approvals and asset tracking, a service desk tool earns its cost.
Some companies need both: a customer-facing help desk for support and a separate service desk for internal IT. They are rarely the same tool, and they rarely should be.
Channels, AI and setup effort
Customer help desks are built around the channels customers use: website chat, email, and messaging apps like WhatsApp or Instagram. AI on these tools mostly answers repeat questions from a knowledge base and hands off to a person when it's unsure. The work is conversational, so the tool has to be fast to reply from.
Service desks are built around a portal and a request form. Employees choose what they need from the catalogue, the request is routed, approved if needed and fulfilled. AI there mostly classifies and routes requests, and suggests articles before a ticket is raised.
Setup effort follows from that. A customer help desk for a small team can be live the same week: connect the support address, add the chat widget, invite teammates, write a few saved replies. A service desk needs its catalogue, categories, approval chains and often an asset inventory defined before it is useful, which is why ITSM rollouts tend to be projects with an owner, a timeline and sometimes an outside consultant.
What each costs
Help desk and service desk software are usually priced per agent seat, so cost grows with headcount. These customer help desk prices are from each vendor's pricing page, checked on 2026-09-06:
| Help desk | Plans per agent per month | Five agents |
|---|---|---|
| Zendesk | Support Team $19; Suite Team $55; Suite Professional $115 | $275 (Suite Team) |
| Freshdesk | Growth $19; Pro $55; Enterprise $89 | $275 (Pro) |
| Help Scout | Free $0; Standard $25; Plus $45; Pro $75 | $125 (Standard) |
| Sellio (shared inbox and live chat) | Free $0; Mini $20; Essentials $95; Plus $295, per workspace | $20 (Mini, 5 seats) |
Sources: Zendesk, Freshdesk, Help Scout. AI answering is billed on top for all of them: Zendesk charges per automated resolution, Help Scout's AI Answers is $0.75 per resolution, and Freshdesk's AI agent is $49 per 100 sessions after a one-time trial allowance.
Service desk platforms are priced per agent too, often with separate tiers for asset management and ITSM features, and the largest ITSM suites are sold through sales quotes. Budget for the time to configure them as well as the licence. To compare per-seat and per-workspace pricing for your own team size, use the seat vs workspace pricing calculator, and for what each conversation costs you today, the cost per support ticket calculator.
Which one a small team needs
Most small teams that search this are deciding how much tool to buy. Here's the short version.
Choose a help desk if
- You support customers, not employees.
- Requests are mostly questions and problems, not standard orders from a catalogue.
- You need several channels (email, chat, messaging) in one place.
- You want to be live within days without a project plan.
Choose a service desk if
- You run IT for your own staff and the company is growing past the point where one person can keep track in their head.
- You need approvals before changes, or an audit trail for compliance.
- You manage enough hardware and software that asset tracking matters.
- Someone on the team knows ITIL, or you are prepared to learn the parts you need.
Choose neither, yet, if
- You are two to five people answering customers by email and chat.
- Your volume is a few dozen conversations a day.
- Your main problem is that messages are scattered across inboxes and nobody knows who replied.
That third group is very common, and a full help desk with ticket fields, SLA policies and macros can be more than it needs. A shared inbox solves the real problem first: one queue, clear ownership and one history per customer. You can add ticket statuses and rules as volume grows. For a closer look at the help desk end of the spectrum, see our guide to help desk software for small business, and if you're choosing between two per-seat tools, our Freshdesk vs Help Scout comparison runs the numbers for a five-person team.
Where a shared inbox fits
A shared inbox sits below a help desk in complexity. Everyone on the team works from one list of conversations, can see who is handling what and replies from the same address or chat widget. Many small teams find that covers most of what they wanted from a help desk.
Sellio is built for that stage: a shared inbox and live chat for support teams of about 2 to 20 people, where website chat, email, Telegram, Slack and Discord conversations land in one queue (WhatsApp and Instagram are coming soon). It adds tickets, automations and support analytics over the same conversations when you need them, and is priced per workspace rather than per seat. It isn't a service desk: there's no service catalogue, change management or asset tracking, so internal IT teams that need ITIL processes should look at a dedicated ITSM tool.
FAQ
Is a service desk the same as a help desk?
No. A service desk includes help desk work, fixing reported issues, but also handles service requests, changes and asset management under a framework like ITIL. In everyday use the terms get mixed up, and some vendors use them interchangeably.
Is a help desk part of ITSM?
An IT help desk can be part of ITSM, usually as the incident handling piece. A customer service help desk is a separate thing: it supports customers rather than employees and doesn't follow ITSM practices.
Does a small business need ITIL?
Rarely at the start. ITIL is useful when an IT team manages many services, users and changes. A small business can borrow single ideas from it, such as written response targets or tracking repeat problems, without adopting the framework.
What is the difference between a service desk and a call center?
A call center handles high volumes of phone calls, often for sales or customer service. A service desk is the point of contact for IT services, across phone, portal, email and chat, and also manages what happens to each request after the first contact.
Can one tool be both a help desk and a service desk?
Some platforms sell both, often as separate products with separate pricing. For most companies, customer support and internal IT have different users, channels and processes, so using two tools, or two clearly separated setups, works better than forcing one to do both.
