ITSM is not the same thing as a helpdesk
A helpdesk receives tickets. ITSM covers the whole delivery: how services are defined, how changes are approved, how assets are documented and how the work improves over time.
The difference shows most clearly the day something goes wrong. A helpdesk can tell you who reported the fault. An ITSM organization can tell you what caused it, which services were affected and what has been done to stop it happening again. We cover how the function is built under service desk and helpdesk.
Why ITSM matters
Most IT departments start out in a shared inbox. It works – until it doesn't.
You don't know what you're doing. Without structured registration there is no way to see how many tickets come in, which ones recur, or where the time goes. Prioritizing becomes a matter of instinct.
Quality varies with the person. The same question gets different answers depending on who happens to reply. Users notice long before the statistics do.
Knowledge sits in people's heads. When someone leaves, it goes with them. Onboarding new staff becomes slow and dependent on someone having time.
Changes happen without traceability. Nobody knows for certain what changed, by whom or why – a problem both when troubleshooting and when facing an audit.
IT can't demonstrate its value. Without follow-up, IT becomes a line in the budget rather than a function delivering measurable benefit.
The processes in brief
ITSM is built from a number of processes drawn from ITIL. You rarely need all of them – each process has its own page where we go into depth.
Incident management restores normal service when something breaks, with priority set by impact and urgency. Largest volume and clearest benefit – start here.
Service requests and service catalog handle orders with predefined workflows and approvals. Repetitive, and therefore the best place to start automating.
Problem management looks for the root cause behind recurring incidents. The process most often skipped and the one that gives the most back over time.
Change management introduces changes with controlled risk and full traceability. For organizations facing audits, this is where ITSM becomes hard to opt out of.
Knowledge management turns resolved tickets into articles, and articles into fewer tickets.
CMDB and asset management keeps track of components and dependencies – the basis for being able to risk-assess a change.
Service level management ties response and resolution times to ticket type, priority and service, with automatic escalation before time runs out.
Automation removes the steps that repeat: assignment, escalation, approval flows and account handling during on- and offboarding.
Follow-up is what separates a system from a process
Ticket volume over time, first-line resolution rate, SLA adherence, recurring problem types and the share of changes that caused an incident.
That last figure is the most honest measure of whether change management works. The data is used to prioritize improvements – and to show management what IT delivers.
How to choose an ITSM system
Seven questions that matter more than the feature list.
How complex is your delivery, really? Do you need full ITIL coverage or is structured ticket handling enough? Buying too much costs both money and implementation time.
Who will administer the system? Some platforms are configured by your own administrators, others require a consultant for every change. That determines what administration costs over five years.
What's included in the price? Module-based pricing looks cheap at signing and gets expensive as you mature. Ask specifically what costs extra.
Where may the data be stored? Public sector, healthcare and regulated industries often require EU data residency or on-premise hosting.
What does it need to integrate with? Microsoft 365, Entra ID, monitoring, finance systems. Check that ready-made integrations exist, not just an API.
What does migration look like? Ticket history, assets and knowledge articles need to come along. Ask who does the work – see migrating to HaloITSM.
Who answers when something goes wrong? Time zone, language and escalation path. It matters little until the first time it matters.
We distribute several ITSM platforms deliberately
A distributor with only one brand can only recommend that brand. We can start from how your organization actually works – and advise against what you don't need.
Within ITSM we are the Nordics' most experienced and largest distributor and implementation partner for HaloITSM. How an implementation is structured is described under ITSM implementation.
If you instead deliver IT to external clients who pay invoices, a PSA system is what you should be looking at.
