Vendors use "help desk", "customer service software", "service desk", "ticketing system" and "CRM" as if they were one product with five names. They aren't, and the confusion costs buyers time: you end up demoing a contact centre when you needed a queue, or a CRM when you needed a help desk. Here's what each term means and how to tell which one you need.
The short version
A ticketing system is the queue: requests in, answers out, each one with an owner and a status.
A help desk is the ticketing system plus the things around it: a knowledge base, a customer portal, rules, reports.
Customer service software is the broad category that help desks belong to, and the name bigger vendors use when they add phone, chat and chatbots on top.
A service desk is the IT version, built around frameworks like ITIL, with change and asset management attached.
A CRM is the sales tool. It knows the customer; it doesn't run the queue.
Help desk software
A help desk takes every request, by email, web form or portal, and turns it into a ticket. The ticket has a number, an owner, a priority, a status and the whole conversation attached. Around the queue sit a knowledge base customers search before they ask, a portal where they send and track tickets, rules that route and close tickets, and reports that say how support is going.
It works for customers and for employees. The same product runs an outside support desk for a software company and an inside IT desk for a school. Older articles, including an earlier version of this one, called help desks "inward facing" and customer service software "outward facing". That distinction has mostly gone; a modern help desk does both, and the difference is who's writing in, not which tool you bought.
Customer service software
This is the category label, and it covers everything from a simple help desk to a contact centre with phone lines, live chat, chatbots and a hundred-agent floor. When a vendor says "customer service platform", expect the larger end: more channels, more automation, more price, and usually an administrator to run it.
The features overlap heavily with a help desk: a queue, a knowledge base, routing, reports. What the bigger products add is telephony, live chat, AI agents that answer first, and workforce tools for scheduling a large team. If you don't have a large team, you're paying for them anyway.
Service desk software
A service desk is the IT department's help desk, shaped by ITIL. Beyond incidents and requests it manages changes, problems, assets and a service catalogue, and it's built for the organisation that has a change board and an asset register. Jira Service Management, ServiceNow and Freshservice live here.
Most small IT teams need the help desk part of a service desk and not the rest. They want employees to submit tickets, a queue to work them, and sign-in with the Windows login. A help desk gives them that without the ITIL overhead.
CRM
Customer relationship management software is the sales team's record of every contact and deal. It isn't a queue, and using it as one gets painful fast: no owner per request, no SLA clock, no portal. What you want is a help desk connected to the CRM, so the ticket shows the account and the account shows the tickets.
Three more terms you'll meet
Ticketing system versus help desk. Vendors use these almost interchangeably, and the honest distinction is that a ticketing system is the queue alone while a help desk includes the knowledge base, portal and reports. If a product calls itself a ticketing system, check whether customers can search articles and track their own tickets. Here's how Cayzu's queue works.
ITSM. IT service management, the discipline behind service desks. If a vendor leads with ITSM, the product is built for IT departments with formal change and problem processes. Small IT teams often find a help desk with Windows sign-in does the job with far less to configure.
Contact centre. The phone-first end of customer service software: call routing, queues of calls, agent scheduling, often chat and chatbots built in. If most of your requests arrive by phone, this is your category. If they arrive by email and form, a help desk is enough. Cayzu puts email, web forms and the portal in one queue, and when a call does come in, an agent can attach a recording or a transcript of it to the ticket.
Which one do you need?
Answer three questions.
Who writes in? Customers, employees, or both. A help desk handles all three; a service desk is built for employees; customer service platforms are built for customers at volume.
How many agents? Two to a hundred is help desk territory. Beyond that, or with a phone floor, look at the contact centre products.
Who will run it? If the answer is "the person who also does their real job", pick something with no administrator role. If you have an IT team with change management, a service desk will feel natural. Our guide to choosing a small business help desk asks that question and six more.
For most small and mid-sized teams the answer is a help desk: the queue, the knowledge base, the portal and the reports, priced per agent, set up in an afternoon. That's what Cayzu is, and the first 15 days are free with every feature so you can test the answer with your own tickets.