GoldenrozBook a call

What is ITSM? Tools, ITIL and where to start

IT service management (ITSM) is the way an IT team designs, delivers and supports the services the business uses, from a password reset to a server change. It replaces ad hoc requests with defined processes: incidents, service requests, changes and assets. ITIL is the best-known framework of guidance for doing ITSM, and an ITSM tool is the software that records and routes the work.

A gold sphere under a clear glass dome on a navy base.

ITSM in plain terms

Every IT team already does service management. Someone asks for a laptop, someone reports that the VPN is down, someone wants a firewall rule changed. The question is whether that work arrives through hallway conversations and personal inboxes, or through a process that records it, assigns it and measures it.

ITSM treats IT as a set of services with users, owners and agreed levels. Email is a service. Remote access is a service. Onboarding a new employee is a service that crosses several teams. Once you name the services, you can say who is responsible for each, how to ask for it and how fast a response should be.

From an engineer’s seat, the value is practical. A recorded incident history shows which system fails most. A change log shows what was touched before an outage. Without those records, every investigation starts from memory.

ITSM vs ITIL

The two terms are often used as if they meant the same thing. They do not.

ITSM ITIL
What it is A discipline: managing IT as services A framework: published guidance on how to do ITSM
Who owns it Nobody. It is a practice PeopleCert
Mandatory No No. It is guidance, not a standard to certify a company against
What you get Working processes in your organization Vocabulary, practices and certifications for people

ITIL 4 describes 34 management practices, according to PeopleCert. PeopleCert released ITIL (Version 5) in early 2026, and its certification listings show ITIL 4 still offered alongside the new version. Other frameworks and standards exist in the same space, including ISO/IEC 20000, which is an international standard for service management, and COBIT, which focuses on governance.

The mistake to avoid is treating ITIL as a checklist to implement in full. A team of five supporting 300 users does not need 34 practices. It needs four or five done properly.

The core processes

These are the processes nearly every organization starts with. The definitions follow common ITIL usage.

Incident management

An incident is an unplanned interruption to a service or a reduction in its quality. The printer is offline, the ERP is slow, a user is locked out. The goal of incident management is to restore service quickly. Finding the root cause is a separate activity.

What it needs: one place to report, categories, priorities based on impact and urgency, and clear escalation.

Service request management

A request is something a user asks for that is a normal part of service: a new account, access to a folder, a software install, a replacement mouse. Nothing is broken.

Separating requests from incidents is the first improvement most teams make. Requests can be standardized, pre-approved and often automated. Mixing them with incidents hides real outages inside a queue of routine tasks.

Change enablement

A change is the addition, modification or removal of anything that could affect a service. Change enablement, which older ITIL versions called change management, makes sure changes are assessed, authorized and scheduled.

Three types cover most cases:

  • Standard changes. Low risk, done often, pre-approved. Example: adding a user to a group.
  • Normal changes. Assessed and approved before work begins.
  • Emergency changes. Done fast to fix or prevent a serious incident, reviewed afterward.

The engineer’s version of this is simple: every production change has a record, a rollback step and a named approver.

Asset and configuration management

Asset management tracks what you own and pay for: laptops, servers, licenses, contracts. Configuration management tracks how components relate, for example which application runs on which server and depends on which database. The store of that information is called a configuration management database, or CMDB.

Start with an accurate asset list. A full CMDB is a later step, and an inaccurate one is worse than none because people trust it.

Problem management

A problem is the cause, or potential cause, of one or more incidents. Problem management looks for root causes and tracks known errors and workarounds. It is the process that reduces ticket volume over time, and it depends on good incident data.

Help desk vs service desk

A help desk is reactive. Users report faults and technicians fix them.

A service desk is the single point of contact between users and IT. It handles incidents and requests, publishes a catalog of what users can ask for, communicates about outages and planned changes, and feeds data to the other processes.

The label on the door matters less than the behavior. If your team logs every contact, separates incidents from requests and offers self-service, it is working as a service desk whatever it is called. The staffing side of this, including first-line coverage and escalation to engineers, is what our IT help desk services page describes.

ITSM tools, by category

An ITSM tool does not create a process. It enforces and records one. Choose the process first and the tool second.

Category What it does When you need it
Ticketing Records, assigns and tracks incidents and requests From day one
Self-service portal Lets users submit and follow tickets without email or phone From day one
Knowledge base Stores answers for users and technicians First 90 days
Service catalog Lists what can be requested, with forms and approvals First 90 days
Change management Records, approves and schedules changes Once more than one person changes production
Asset management and CMDB Tracks hardware, software, licenses and relationships When you cannot answer what you own
Automation and integrations Connects to identity, monitoring, chat and endpoint tools After the basic processes are stable
Reporting Shows volume, response times and trends From day one, kept simple

Products in this market range from large enterprise platforms to tools aimed at small and mid-size teams. Commonly evaluated examples include ServiceNow, Jira Service Management, Freshservice and ManageEngine ServiceDesk Plus. We name them as examples, not as recommendations, and Goldenroz does not resell any of them.

Questions that separate tools in practice:

  • Can non-IT teams such as HR and facilities use it for their own requests
  • How are licenses counted: per technician, per user or per asset
  • Which integrations exist for your identity provider, endpoint management and monitoring
  • Can you export all your data if you leave
  • How much configuration can your own team do without a consultant

ITSM best practices for a first rollout

  • Start with the processes that produce the most tickets, not the most interesting ones.
  • Keep categories few. Twenty categories nobody uses correctly are worse than six that everyone does.
  • Define priority by impact and urgency, in writing, so that priority is not set by whoever shouts loudest.
  • Close the side doors. If tickets are also accepted by direct message, the data is incomplete.
  • Measure a small set of numbers: volume by category, time to first response, time to resolution, reopen rate.
  • Write knowledge articles from real tickets. The ten most frequent requests are the first ten articles.
  • Review the setup every quarter and remove fields and steps nobody uses.

Where to start: the first 90 days

This is a planning outline, to be adjusted to your team’s size.

Days 1 to 30: see what you have

  • List the services IT provides and name an owner for each
  • Count requests and incidents for two weeks, from every channel
  • Agree on categories, priorities and target response times
  • Select a tool against a written list of requirements

Days 31 to 60: build the basics

  • Configure incident and request workflows
  • Launch the portal and one intake email address
  • Publish a first service catalog with the most common requests
  • Write the first knowledge articles
  • Train technicians and announce the new channel to users

Days 61 to 90: tighten and extend

  • Introduce a simple change record with approval and rollback fields
  • Import an asset list and link assets to users
  • Review the first month of data and fix the categories that were misused
  • Decide what phase two covers: problem management, automation or integrations

What to do next

Count your tickets by channel for two weeks. If more than a small share arrives outside the official channel, fix intake before buying or replacing a tool.

Our ITSM implementation service covers process design, tool selection, configuration and rollout as a project, starting at $25,000 at a fixed price per phase. If you would prefer that the day-to-day service desk and the systems behind it are run for you, managed IT services is a monthly retainer quoted after an assessment. Automating the request workflows themselves is covered in what is Power Automate.

Questions buyers ask

What is the difference between ITSM and ITIL?

ITSM is the discipline: how an organization manages its IT services. ITIL is a published framework of guidance on how to do that, owned by PeopleCert. You can practice ITSM without ITIL, and many teams adopt only the ITIL practices that fit their size.

What is the difference between a help desk and a service desk?

A help desk fixes problems users report. A service desk is the single point of contact between users and IT for everything: incidents, requests for access or equipment, questions and communication about changes. In practice the terms overlap, and what matters is whether requests and incidents are handled as separate, defined processes.

What are ITSM tools?

ITSM tools are software that records tickets and routes them through defined workflows. Typical modules are a ticketing system, a self-service portal, a knowledge base, a service catalog, change management, and an asset database or CMDB. Examples include ServiceNow, Jira Service Management, Freshservice and ManageEngine ServiceDesk Plus.

Which version of ITIL is current?

PeopleCert released ITIL (Version 5) in early 2026, and ITIL 4 certifications remain available alongside it, according to PeopleCert's certification listings. ITIL 4 describes 34 management practices. For a team starting out, the differences between versions matter less than getting incident, request and change handling working.

How long does an ITSM implementation take?

It depends on the number of processes, integrations and teams involved. A first phase that covers incident and request management, a portal and a small service catalog can be planned as a 90-day effort. Change management, asset management and integrations usually follow in later phases.

Written by

CTO and technology partner

Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.

Keep reading

Talk to the person who will do the work

One hour, no sales team. You talk to Daniel or Shai, we look at your account or your product, and you leave with a clear next step.

Or send the details

Book a 1-hour consultationWhatsApp us