ITIL 4 Service Desk study materials
ITIL 4 Service Desk study resources

ITIL 4 Service Desk: Processes, Tools and Technology

ITIL 4 Service Desk · Work through your exam, one topic at a time.

All guide sections

Processes, Tools and Technology

The workflows the desk operates inside

The service desk works within other practices rather than owning end-to-end processes.

  • Incident management - identify and log, categorise, prioritise by impact × urgency, diagnose, escalate or swarm, resolve, close. Major incidents take a separate fast path with dedicated communication.
  • Service request management - requests come from a published catalogue and are fulfilled through request models with pre-agreed steps and approvals; a request is not a failure of a service.
  • Problem management - reactive and proactive; known errors and workarounds live in the known error database, and the desk is the main sensor for recurring incidents.
  • Knowledge management - capture at the point of contact, validate, publish, reuse, and retire stale articles.
  • Change enablement - standard, normal and emergency changes; the desk communicates impacts and outages.
  • Service level management - SLAs and OLAs set expectations that drive prioritisation and escalation rules.

Tooling

An omnichannel platform with a shared queue; an ITSM workflow engine for records and routing; a self-service portal and service catalogue; chatbot or virtual agent; AI-assisted classification, summarisation and suggested resolution; automation and orchestration for repeatable fulfilment; CMDB and asset data for impact assessment; a knowledge base; workforce management for forecasting and scheduling; dashboards; and CSAT surveying. Integration through APIs matters more than any single feature, because fragmented records produce fragmented service.

Worked example

Password resets are 25% of contacts. Instead of adding agents, the organisation publishes a self-service reset with identity verification, an automated fulfilment path, and escalation to an analyst when verification fails. Reasoning: high-volume, low-variability demand is the best candidate for shift-left automation, and the escalation route preserves safety.

Traps

Treating service requests as incidents; building a catalogue without request models or approvals; buying tooling before designing the workflow; deploying a chatbot with no clean hand-off path to a human.