Service desk
A service desk is the single point of contact between an organisation and the people who use its technology services. Beyond resolving incidents, it handles service requests, changes and access, and works through formal processes: a service catalogue, service level agreements and approval flows.
What is service desk?
A service desk is the single point of contact between an organisation and the people who use its technology services. Beyond resolving incidents, it handles service requests, changes and access, and works through formal processes: a service catalogue, service level agreements and approval flows.
Also: IT service desk
A service desk is not a help desk
A help desk fixes problems: something broke and needs repairing. A service desk does that and also manages the service lifecycle, including requests where nothing is broken, such as onboarding somebody, asking for a licence or approving access. In practice plenty of people use the two terms interchangeably, and the commercial tools do nothing to help tell them apart.
Why it matters
What changes in a SaaS
The distinction matters when you are comparing tools, because it decides the price and the complexity. A service desk platform brings approval flows, asset management and a service catalogue, and it costs, in money and in maintenance, exactly what that costs. If your case is supporting customers of a product, almost none of it applies and you will be paying for processes you never use.
Service desk in detail
Internal versus external
A service desk mainly serves the organisation itself: employees who need something from IT. SaaS support serves customers outside it. Everything changes: the contractual relationship, the urgency, the tone and what happens if you do not answer.
Where the term comes from
From IT service management practice, where it is formally defined alongside incident, problem, request and change. That vocabulary belongs there, which is why it sounds like corporate process when it is used at a twenty-person company.
When you genuinely need one
When you have to demonstrate the process to somebody: an audit, a contract with committed service levels, a large customer who requires traceability. If nobody is going to ask for that demonstration, the formality is cost with nothing on the other side.
How Intake handles it
Questions about service desk
What is the difference between a service desk and a help desk?
The help desk resolves incidents; the service desk adds the handling of requests, changes and access, with formal process around it. A service desk includes what a help desk does, not the other way round.
Does a small SaaS need a service desk?
Almost never. Service desk formality solves the problems of large organisations with auditable processes. To support customers of a product, a well-run shared inbox covers the same ground at a fraction of the cost.
Are service desk and CSM related?
Barely. The service desk is a technology function pointed at internal services; the CSM is a commercial role pointed at customer retention. They overlap only in that both talk to users.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Help desk — Help desk
A help desk is the team and the tool that receive user questions and resolve them. It centralises in one place whatever arrives by email, chat or form, turns each question into a ticket with a status and an owner, and keeps the history of what was answered.
SLA — Service level agreement
A service level agreement is the written commitment to respond within set deadlines. It fixes maximum times — usually first response and resolution — defines the hours in which they count, and normally states what happens when they are missed.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
Escalation
Escalation is handing a conversation to somebody with more knowledge or more permissions to resolve it. It can go from one support tier to another, from an automated agent to a person, or from support to engineering — and in every case whoever receives it has not seen the case until that moment.
Support tiers
Support tiers are the usual way of splitting questions by what it takes to resolve them. Tier 1 handles the known and documented, tier 2 what requires technical knowledge of the product, and tier 3 what ends up with whoever wrote the code.
CSM — Customer Success Manager
A Customer Success Manager (CSM) is the person responsible for making sure a customer gets the outcome they signed up for. They work proactively across a book of accounts, own adoption, retention and expansion, and their success is measured in renewals, not in closed tickets.
