Service Desk
The service desk is the single point of contact between users and the IT organisation. It logs incidents and service requests, classifies and prioritises them, resolves at first level or escalates, and keeps requesters informed. Distinction: a help desk reactively handles faults, while a service desk additionally owns service requests, communication and the link to the service catalogue. ITIL 4 lists the service desk as a practice in its own right among its 34 management practices.
Service Desk in practice
The usual arrangement is tiered: first level receives, qualifies and resolves standard cases from documented solutions; second level contributes systems depth; third level covers specialists or vendors. The decisive metric is first-contact resolution, because every handover adds waiting time, context loss and follow-up questions. That is precisely what shift-left targets: recurring requests move from second level into documented first-level solutions, from there into self-service and finally into automation — self-service password reset, or software delivery through a portal catalogue.
A service desk without a maintained knowledge base and a binding service catalogue falls back on ad-hoc requests and is consumed by its own repeat work. Keeping the two intake types apart matters: an incident interrupts a committed service and runs against the agreed restoration time, while a service request — a new device, an additional permission, a software install — is planned work with its own approval and its own lead time.
ITIL 4 separates them accordingly into the incident management and service request management practices. Counted in one pot, the metrics lose meaning, because a rise in ticket volume could equally indicate a quality problem or growth of the organisation.