Help Desk vs Service Desk
A help desk is reactive, incident-focused support (and the ticketing tool behind it); a service desk is the broader ITIL practice that also owns service requests and ties into change, problem and release management.
You are deciding whether the team needs a customer-support workspace, a broader service-management model, or both.
Support owns customer conversations in a help desk while internal access requests follow governed service-desk workflows.
Buying an ITIL-shaped process for work that needs fast customer context—or treating every internal service request like a ticket reply.
The two terms describe different scopes, not different products. A help desk is reactive and narrow: someone is blocked, they contact you, you unblock them. In ITIL terms it maps to a single practice — incident management — and its job is to restore service fast. A service desk is the broader construct that ITIL defines as the single point of contact between a provider and its users: it handles incidents and service requests (a new laptop, access to a system, a password reset), and it plugs into the wider service-management machinery — problem, change and release management — rather than closing tickets one at a time. Atlassian's ITSM guide is a serviceable plain-language reference for the framing.
The split is historical. The help desk grew out of IT-centric, break-fix support; the service desk was ITIL's attempt to reframe support as a managed service with a lifecycle. ITIL 4 underlines the shift by reclassifying the service desk from a function (ITIL v3) to a practice — a move in emphasis from "a team that answers phones" to "a capability that owns the user relationship end to end."
For a customer-support audience the distinction is mostly borrowed from internal IT, and it is worth being honest about that. In the customer-support market, "help desk" almost always just means the ticketing tool — Zendesk, Freshdesk, Zoho Desk, Help Scout — that routes and tracks external conversations. "Service desk" is the internal-IT / ITSM label (ServiceNow, Jira Service Management), and vendors slide between the two words because "service desk" reads as the more strategic, higher-tier purchase. What actually differs is the capability underneath, not the noun on the pricing page.
What it hides: the label is frequently marketing. Rebranding a help desk as a "service desk" does not add change, problem or service-request management — those are practices you have to build, not a tier you can buy. And for an external customer-support team, the full ITSM apparatus a true service desk implies is often scope you will never use; adopting its vocabulary, or paying for it, can import internal-IT process overhead into a job that only ever needed a fast, well-run queue.