Reference · IT service management

IT Service Support: An Overview

IT service support is the set of ITIL-aligned functions that keep day-to-day IT operations running for end users. It centers on the service desk as the single point of contact, backed by four core disciplines: incident management (restoring normal service as quickly as possible after a disruption), problem management (finding and removing the underlying cause of recurring incidents), change management (controlling how modifications are introduced into the live environment), and request fulfillment (handling routine user requests that are not tied to a fault).

The distinction between an incident and a problem is one of the more commonly misunderstood parts of IT service support: an incident is a single disruptive event that needs to be resolved, while a problem is the root cause behind one or more incidents that needs to be diagnosed and eliminated so the incident does not recur. Mature service-support organizations track both separately, closing incidents quickly through workarounds while problem management runs in parallel to fix the underlying defect.

The service desk itself takes one of a few common shapes depending on the size and spread of the organization it supports. A local service desk sits close to the users it serves and understands site-specific quirks well, but does not scale past a single location. A centralized service desk consolidates staff into one location serving several sites, which lowers cost per ticket at the expense of that local context. A virtual service desk uses distributed staff who appear as a single point of contact through shared tooling and queues, and a follow-the-sun arrangement hands tickets between time zones so coverage runs around the clock without any one team working overnight shifts.

Most service-support metrics track how quickly and how well the desk restores normal service: first-call resolution rate, mean time to resolve by priority tier, and adherence to the response and resolution targets set in a service-level agreement. A self-service portal that lets end users log routine requests, reset passwords, or check ticket status without calling in is now standard practice, since it reduces the load on first-line staff for exactly the kind of low-complexity work that request fulfillment is meant to cover.

Frequently Asked Questions

What is the difference between IT service support and IT service delivery?

Service support handles the short-horizon, reactive side of ITSM — incidents, problems, changes, and routine requests as they come in day to day. Service delivery covers the longer-horizon planning work: setting performance targets, sizing capacity ahead of demand, and planning for recovery after a major outage.

What is the difference between an incident and a problem?

An incident is a single disruptive event that needs restoring to normal service as quickly as possible. A problem is the underlying cause behind one or more incidents — diagnosing and removing it is what stops the same incident from recurring.

What does a service desk actually do?

It is the single point of contact for end users, logging and triaging every incoming incident and request, then routing anything it cannot resolve on first contact to the right specialist team while tracking the ticket until it closes.

What is request fulfillment in ITIL?

The handling of routine user requests that are not tied to a fault in the service — a new-account setup, a software install, an access-permission change — as distinct from incident management, which exists to restore something that broke.