Help desk or service desk?
The terms are used interchangeably, but they describe different levels of ambition.
A help desk is reactive. Something breaks, someone reports it, and someone fixes it. The function works well as long as the volume is manageable and the requirements are low.
A service desk is the interface for the entire IT delivery. In addition to incidents, it handles requests from a service catalog, access rights, changes, and follow-ups against agreed-upon response times. It is therefore one of the core functions within ITSM.
Most organizations start with the former and grow into the latter. The problem arises when the volume grows but the way of working does not.
The shared inbox and why it stops working
Almost everyone starts there, and the breaking point rarely comes as a dramatic event, but rather as a slow decline.
No one knows what is currently being worked on. Two people answer the same question, and a third assumes someone else has already handled it.
Nothing can be measured. How many tickets are coming in? Which ones are recurring? Where does the time go? Without logging, prioritization becomes a matter of guesswork.
Quality varies from person to person. The same question gets different answers depending on who happens to respond. Users notice this long before it shows up in the statistics.
Knowledge is locked in people's heads. When someone leaves, that knowledge goes with them, and onboarding new employees takes a long time.
How to build a service desk
One entry point, multiple channels
Users should be able to reach out however they prefer—email, portal, phone, chat, or Microsoft Teams—but everything should land in the same queue. Multiple parallel entry points without a shared queue create the same problem as a shared inbox, just with more places to lose track of things.
Categorization from the start
A ticket registered without a category cannot be analyzed later. Keep the list short. A category structure with sixty options will be filled out carelessly and become useless anyway.
Prioritization based on impact and urgency
Priority should be determined by how many people are affected and how urgent the issue is, not by who is calling. This is one of the hardest principles to uphold and one of the most valuable.
A first line that actually solves problems
A first line that only forwards tickets is a bottleneck, not a relief. Give them the mandate, documented procedures, and access to the knowledge base.
Knowledge base integrated with the ticket workflow
Resolved tickets become articles, and articles mean fewer tickets. This only works if the article can be written the moment the ticket is solved. We go through what the structure should look like under IT documentation.
Self-service for repetitive tasks
Password resets, permissions, and standard requests rarely require human intervention. A portal with a service catalog and approval workflows eliminates the very tasks that are the least rewarding to work on. The next step is automation of the execution itself.
SLAs that are monitored continuously
Response and resolution times linked to ticket type and priority, with automatic escalation before time runs out. Retrospective follow-ups only tell you what has already gone wrong.
Service desk for internal use or for customers?
The function looks the same, but the system requirements differ, and this is where the wrong choices are made.
For your own organization, the focus is on ITIL processes, service catalogs, assets, and internal monitoring.
For external customers who pay invoices, you also need agreements, time tracking, price lists, and billing. A pure ticketing system cannot handle that part – you need a PSA system, and what is missing is otherwise managed in a separate spreadsheet.
For customers in a customer service role, i.e., support for a product rather than IT, the focus is instead on response times, customer satisfaction, and multiple channels.
We deliver platforms for all three. Does the person contacting you send you an invoice, or do they receive one from you? That is usually the question that decides it.
