ITIL incident management is the practice of restoring a disrupted IT service as fast as possible while limiting business impact. A typical process logs and categorises the incident, sets priority by impact and urgency, diagnoses and escalates, resolves, closes and reviews. ITIL 4 states the purpose as “to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.” This guide walks through each step, gives you a ready priority matrix, explains how to run a major incident, and lists the KPIs and tool features that make the process stick.

What is an incident in ITIL?

ITIL defines an incident as an unplanned interruption to a service, or a reduction in the quality of a service. A failed VPN, a slow ERP screen, a printer queue that will not clear and a monitoring alert that shows a link down are all incidents. A request for a new laptop or software access is not an incident; that is a service request, and it follows its own fulfilment workflow.

The goal of incident management is speed and containment, not root cause. If the payroll server is down, the incident team restores payroll, even with a workaround such as failing over to a standby server. Finding out why the server failed is the job of problem management.

ITIL v3 and ITIL 4. ITIL v3 described incident management as a process inside the Service Operation stage. ITIL 4 calls it a practice: a set of people, processes, tools and partners that work together inside the service value chain. The day to day steps barely change. What changes is the emphasis on collaboration, automation and continual improvement, rather than a fixed handoff from one support tier to the next.

Incident vs problem vs service request

Most service desks mix these up in their first year, and the result is messy reporting: request volumes inflate the incident count and root causes never get fixed. Use this table when you set up categories and train agents.

IncidentProblemService request
What it isUnplanned interruption or degradation of a serviceThe cause, or potential cause, of one or more incidentsA formal request for something standard, such as access or equipment
GoalRestore service quicklyFind and remove the root causeFulfil the request to an agreed standard
Typical triggerUser call, email, portal ticket, monitoring alertRepeat incidents, a major incident, trend analysisPortal or catalogue item
Measured byMTTR, SLA compliance, first contact resolutionRoot causes found, known errors, repeat incidents avoidedFulfilment time, request backlog
ExampleEmail is down for the finance teamEmail fails every month end because a disk fills upNew starter needs an email account

The ITIL incident management process, step by step

ITIL 4 does not prescribe a fixed number of steps; it leaves the workflow to you. The sequence below is the one most service desks use, and it maps cleanly to any ITSM tool.

  1. Detect and log. Incidents arrive from phone calls, emails, the self service portal, chat and monitoring alerts. Every incident gets a unique ID, a timestamp, the source channel, the affected user and the affected service or configuration item (CI). Converting email to tickets automatically removes the most common gap: incidents that live only in someone’s inbox.
  2. Categorise. Assign a category and subcategory (for example Network > VPN, or Application > ERP). Keep the category tree short, two or three levels at most, because agents pick the first option that looks close when the list is long. Good categories drive routing, reporting and problem trend analysis.
  3. Prioritise by impact and urgency. Impact is how many users or how much of the business is affected. Urgency is how fast the business needs a fix. Combine the two in a priority matrix (next section) so that priority is calculated, not argued over. Priority then sets the SLA clock.
  4. Diagnose and escalate. The first line agent checks the knowledge base and known errors, and tries a documented fix. If the incident is not resolved within the agreed time, it escalates. Functional escalation sends it to a specialist group (network, database, a vendor). Hierarchic escalation brings in managers when the SLA is at risk or the impact is high.
  5. Resolve and recover. Apply the fix or workaround, confirm the service is back to its agreed level, and record what was done. If the fix is a workaround, link the incident to a problem record so the root cause is still investigated.
  6. Close. Confirm with the user that the service works, set a closure category, and close the ticket. Many teams auto close after a set period if the user does not respond, and send a short satisfaction survey.
  7. Review. For major incidents, and for any incident that breached its SLA, hold a short review: what happened, how fast you detected it, what slowed resolution, and what will change. Feed knowledge articles and problem records from the review.

Incident priority matrix: impact x urgency

A priority matrix turns two simple questions into a consistent priority. The matrix below is a common three by three model with five priority levels. The response and resolution targets are examples only; set your own in your SLAs, and agree them with the business before you publish them.

Impact: High = a whole site, a business critical service or many users; Medium = a department or a group of users; Low = one user, with a workaround available.

Urgency: High = work has stopped or money, safety or compliance is at risk now; Medium = work is slowed; Low = it can wait.

Impact \ UrgencyHigh urgencyMedium urgencyLow urgency
High impactP1 Critical (example: respond 15 min, resolve 4 h)P2 High (respond 30 min, resolve 8 h)P3 Medium (respond 2 h, resolve 1 business day)
Medium impactP2 HighP3 MediumP4 Low (respond 4 h, resolve 3 business days)
Low impactP3 MediumP4 LowP5 Planning (respond 1 business day, resolve 5 business days)

Major incident management in ITIL

A major incident is an incident with significant impact on the business, serious enough that it needs a separate, faster procedure. Most organisations treat every P1 as a candidate major incident and let the incident manager or service desk lead declare it.

What changes when an incident becomes major:

  • One owner. A named major incident manager runs the response. Their job is coordination and communication, not fixing.
  • A dedicated team. Specialists from network, applications, database and vendors join one call or channel instead of passing the ticket between queues. ITIL 4 calls this kind of collaborative working swarming.
  • Fixed communication rhythm. Status updates to users and leadership at set intervals, for example every 30 minutes, even when the update is “still investigating.” Silence generates more calls than the outage.
  • Parent and child tickets. One parent major incident, with duplicate user tickets linked to it, so the service desk can close them all together.
  • Shorter escalation timers. Escalation to senior management happens in minutes, not hours.
  • Mandatory review. Every major incident gets a post incident review within a few working days, and usually a problem record.

A simple major incident runbook covers: the criteria for declaring a major incident, the contact list and bridge details, the update template and schedule, the decision points for failover or vendor escalation, and the review template. The priority matrix above gives you the impact and urgency definitions to start from.

ITIL incident management best practices

These are the practices that separate a service desk that keeps up from one that drowns in backlog.

  • Calculate priority, do not negotiate it. Use the impact and urgency matrix and let the tool set priority. It ends the “everything is urgent” problem and makes SLA reports honest.
  • Keep categories short and stable. Review the category tree quarterly and merge categories that are rarely used. Clean categories are what make problem trends visible.
  • Route by rules, then by skill. Auto assign tickets to the right group based on category, service, location or customer. Manual triage at scale is where hours disappear.
  • Tie escalation to the SLA clock. Escalate automatically when a response or resolution threshold is near, not when someone remembers. Reassign on breach so a ticket never sits with an absent technician.
  • Put knowledge at the point of work. Suggest relevant articles when an agent logs an incident, and turn good resolutions into articles. A knowledge base that agents never see does nothing for MTTR.
  • Link incidents to CIs. When an incident is logged against the affected server, application or link, agents can see related changes and past incidents, and problem management can spot weak components.
  • Communicate before users ask. Publish known outages on the portal and notify affected users by email, SMS or chat. It cuts duplicate tickets during a major incident.
  • Hand off to problem management. Any repeat incident or major incident should create or link to a problem record. Otherwise the same outage comes back next month.
  • Review the numbers monthly. Look at SLA breaches by category and group, reopened tickets and the top ten incident types. Pick one improvement each month and track it.

Incident management KPIs to track

Pick a small set of measures that reflect both speed and quality, and report them by priority, category and support group. Averages across all tickets hide the P1s that matter. To see what faster recovery is worth in money, try the free MTTR impact analyzer or the incident response calculator.

KPIWhat it measuresHow to use it
Mean time to acknowledge (MTTA)Time from logging to first responseShows whether tickets are picked up within the SLA
Mean time to resolve (MTTR)Average time to restore serviceTrack by priority; rising P1 MTTR is an early warning
SLA complianceShare of tickets responded to and resolved within targetReport by group and category to find bottlenecks
First contact resolutionShare of incidents fixed by the first line without escalationImproves with better knowledge articles and scripts
Reopen rateShare of closed incidents reopenedA high rate means fixes are incomplete or closure is rushed
Backlog and ageingOpen incidents and how long they have been openSpot queues that are growing week on week
Repeat incidentsIncidents with the same cause or CIFeeds problem management priorities
User satisfaction (CSAT)Survey score after closureRead the comments, not just the score

What to look for in an ITIL incident management tool

Any ITSM tool can log a ticket. The difference shows in how much of the process above it runs for you. Use this checklist when you shortlist tools, and ask each vendor to show it in a live demo rather than on a slide.

CapabilityWhy it mattersQuestion to ask the vendor
Multichannel intakeIncidents arrive by email, portal, chat, phone and alertsDoes email convert to tickets and thread replies automatically?
Priority matrix and SLA timersPriority and targets set consistentlyCan SLA targets differ by priority, service and business hours?
Rule based assignment and escalationRemoves manual triageCan it reassign automatically when an SLA is breached?
Knowledge suggestionsFaster first line fixesDoes it suggest articles while the incident is being logged?
CMDB and CI linkingContext for diagnosis and change impactCan incidents, problems and changes all link to the same CI?
Problem and change on the same platformCloses the loop from incident to root cause to fixAre these modules in the same product and plan?
Reports and dashboardsKPI tracking without spreadsheetsCan reports be scheduled and exported by group and priority?
Deployment and data locationCompliance and data residencyIs it available as SaaS and on premise, and in which countries?

How Infraon ITSM supports ITIL incident management

Infraon ITSM is built around ITIL practices and is PinkVERIFY verified for 12 ITIL processes. Here is how it maps to the process above, with the plan each capability sits in.

  • Intake and logging (Essential, $19 per user per month). Incidents from the portal, email, phone and mobile app, each with a unique ID, timestamps, source and the caller’s previous incident history. Email to ticket conversion and email threading keep conversations on the ticket. Incident templates let users raise common issues from the self service portal.
  • Priority, SLA and escalation (Essential and up). SLA templates set response and resolution targets per priority level in your priority matrix, with business hour templates and multiple escalation points. The Standard plan ($47) adds multiple SLA profiles. Escalation matrices per business service, and automatic reassignment when an SLA is breached, keep tickets moving.
  • Assignment. Rule based auto assignment to groups, subgroups and technicians, plus vendor routing for third party support.
  • GenAI ticket prioritisation (Professional, $57). The Professional plan adds GenAI ticket routing and prioritisation to help the desk set priority and send tickets to the right group.
  • Knowledge at the point of work. Relevant articles are suggested when an agent adds an incident, and resolutions can be saved as knowledge articles automatically.
  • Problem and change (Professional). Create a problem record from an incident, run root cause analysis on a visual timeline, and raise changes with CAB approval, all linked to the same CIs in the CMDB.
  • Communication and reporting. Notifications by email, SMS and WhatsApp at every status change, configurable dashboards with drill down, and KPI and SLA reports exported or scheduled to mailboxes.

Infraon ITSM runs as SaaS, or as the Enterprise edition on premise or hybrid, deployed in the country you need, with Arabic language support. Security and service credentials include ISO/IEC 27001:2022, ISO 20000-1:2018 and SOC 2 Type 2.

See how Infraon ITSM handles logging, SLA based escalation and problem handoff on the incident management page, or read how QLM improved customer satisfaction by up to 75%.

Customer results

Published Infraon ITSM case studies show what a structured incident process looks like in practice. Figures are as printed in each case study.

  • QLM Life and Medical Insurance Company, a life and medical insurer in the Middle East, moved its service desk, asset management and self service portal onto Infraon ITSM. The case study reports customer satisfaction improvement of up to 75%, IT spend reduced by up to 50% and compliance improved by up to 50%, with the platform up and running in a matter of months.
  • Tata Electronics, a semiconductor and precision component manufacturer in India, uses Infraon ITSM to manage access permissions for more than 18,000 users and reports reduced time and effort for ticket creation and tracking.
  • Udaan, a B2B ecommerce platform in India, runs a dedicated Infraon ITSM instance for 130 technicians and helpdesk agents serving 10,000+ users, handling 500+ tickets a day; knowledge base integration reduced the request load.

Read the full stories on the case studies page.

Frequently Asked Questions

What is ITIL incident management?

It is the ITIL practice of restoring a disrupted IT service as quickly as possible while limiting the impact on the business. It covers logging, categorising, prioritising, diagnosing, escalating, resolving, closing and reviewing incidents.

What are the steps in the ITIL incident management process?

ITIL 4 does not fix a number of steps, but a typical process is: detect and log, categorise, prioritise by impact and urgency, diagnose and escalate, resolve and recover, close, and review.

What is the difference between an incident and a problem?

An incident is a single interruption or degradation of service, and the aim is to restore service fast. A problem is the underlying cause of one or more incidents, and the aim is to find and remove that cause so the incidents stop recurring.

What is major incident management in ITIL?

It is a separate, faster procedure for incidents with significant business impact. A named major incident manager coordinates a dedicated team, sends updates on a fixed schedule, links duplicate tickets to one parent incident and runs a review afterwards.

How is incident priority calculated?

Priority is usually calculated from impact (how much of the business is affected) and urgency (how quickly a fix is needed) using a priority matrix. The resulting priority sets the response and resolution targets in your SLA.

What is the difference between ITIL v3 and ITIL 4 incident management?

ITIL v3 treated incident management as a process within Service Operation. ITIL 4 treats it as a practice within the service value chain, with more weight on collaboration such as swarming, automation and continual improvement. The core steps are much the same.

Which KPIs matter most for incident management?

Start with MTTR, MTTA, SLA compliance, first contact resolution, reopen rate and user satisfaction, reported by priority and support group rather than as one overall average.

Run your incident process in Infraon ITSM. Plans start at $19 per user per month, with GenAI ticket prioritisation in Professional. Start a 14 day free trial or book a demo.

Do you like Sudhakar Aruchamy's articles? Follow on social!
Start Free Trial