ITIL 4 Service Desk key terms

The single point of contact between a service provider and its users, handling incidents, service requests, and communication, and coordinating activity with other practices to keep services running and users informed.

An arrangement where users reach one entry channel for all their service needs, so they do not have to identify the right team or person before getting help or information.

An unplanned interruption to a service or reduction in service quality. A service desk logs it, captures symptoms, restores service as quickly as possible, and keeps users updated until closure.

A user's request for something that is part of normal service delivery, such as access, information, a standard change, or a routine item, handled through an agreed request fulfilment route rather than incident management.

An incident with significant business impact that needs a separate, prioritized response, often with a dedicated coordinator, senior escalation, and frequent stakeholder communication until service is restored.

A problem that has been analysed and has a documented root cause and, usually, a workaround. The service desk uses known error records to resolve matching incidents faster and consistently.

A temporary way to restore or continue service when the underlying cause is not yet fixed. The service desk offers it to users and records it so others can reuse it.

A cause, or potential cause, of one or more incidents. Service desk staff contribute evidence and patterns from recurring tickets that help problem management identify and remove the underlying cause.

The practice of managing user requests end to end, from logging and approval through to delivery and closure, using agreed procedures and published service levels for each request type.

A structured description of services and offerings available to users, including what each includes, who may request it, expected delivery time, and any cost or approval conditions.

A user-facing interface for logging tickets, tracking status, searching knowledge, and requesting catalogue items without contacting an agent, freeing desk capacity for complex work.

Delivering consistent service across multiple contact channels such as phone, email, chat, portal, and messaging, with one shared history so users do not repeat themselves when switching channels.

Automated conversational tooling that answers common questions, guides users through simple requests, and hands complex or sensitive cases to a human agent with the context already captured.

A curated, searchable store of articles, known errors, workarounds, and procedures that agents and users rely on to resolve issues consistently and reduce repeat diagnosis effort.

An approach in which knowledge is created, shared, and reused as a routine part of every interaction, so solutions are captured during tickets rather than recreated from scratch each time.

A documented agreement between a provider and a customer that states expected service levels, such as response and restore times, and the responsibilities of each party.

A measurable commitment within an agreement, such as answering 80 percent of calls within 30 seconds or restoring priority-one service within four hours, used to judge desk performance.

The elapsed time between a user's contact or ticket submission and the first meaningful human response, a common service desk measure that reflects accessibility and queue performance.

The proportion of contacts resolved during the first interaction without escalation, callback, or reopen. It indicates desk competence, knowledge quality, and empowerment of agents.

The share of incidents or requests resolved correctly on the first attempt, with no repeat contact for the same issue. It highlights quality rather than speed of handling.

The percentage of closed tickets that users ask to have reopened, usually because the fix failed or the request was incomplete. It is a useful signal of premature or poor-quality closure.

The proportion of users who leave a queue, such as hanging up before an agent answers, before being served. High values point to understaffing or poor queue design.

The measured perception of users about the service they received, usually collected through short post-ticket surveys and tracked over time to guide improvements in desk behaviour and speed.

A loyalty measure based on how likely users are to recommend the service, calculated from promoter and detractor responses. It complements satisfaction and effort scores in desk reporting.

A structured way of collecting and using user feedback, complaints, and survey results so that improvement priorities reflect what users actually experience rather than internal assumptions.

A defined, repeatable measurement, such as resolution time or backlog size, with an agreed formula and data source, used to judge performance and support decisions about the service desk.

A metric chosen because it reflects progress toward an important objective, reported regularly to managers. Good indicators are few, balanced, and tied to user or business outcomes.

A visual display of selected live or near-live metrics, such as open tickets by priority and service level compliance, giving teams and managers a shared view of current performance.

The recurring practice of identifying, prioritizing, and implementing improvements to products, services, and practices, using evidence such as metrics, feedback, and audit findings.

A log of suggested improvements with their owner, expected benefit, priority, and status, ensuring ideas from agents, users, and reviews are tracked rather than forgotten.

A four-stage improvement loop: plan the change, do it on a small scale, check results against expectations, and act to adopt, adjust, or abandon it. Useful for piloting desk changes safely.

Moving an issue to another level or team because it needs more skill, authority, or urgency than the current handler has. Functional escalation adds expertise; hierarchical escalation adds management attention.

An arrangement where first-line staff resolve common issues, second-line specialists handle deeper technical work, and third-line or supplier teams address the hardest cases, with clear handoff rules.

Front-line staff who log, classify, diagnose, and resolve contacts, keep users informed, and escalate what they cannot fix, acting as the human face of the service provider.

The role accountable for desk performance, staffing, processes, tooling, and service level achievement, and for developing the team and driving improvements with other practice owners.

Giving agents the authority, guidance, and access needed to resolve issues and make reasonable decisions without seeking approval, which raises first contact resolution and user trust.

A staffing design in which desks in different time zones pass open work to each other at shift end, providing continuous coverage without forcing one site to work overnight.

A structured transfer of open tickets, known issues, and pending commitments between shifts, so incoming staff know what needs attention and users are not left waiting for a forgotten promise.

A record of a contact that captures the user, affected service, description, priority, actions taken, and status, providing an auditable history for resolution, reporting, and improvement.

Deciding the order in which tickets are handled, typically from impact and urgency, so that the most damaging issues get attention first while routine requests wait predictably.

Actively monitoring incoming contact volumes and waiting work, adjusting staffing, routing, and self-service prompts so that response targets are met and users are not left queuing.

A staffing formula that estimates how many agents are needed to answer a given call volume within a target wait time, balancing service level against cost of overstaffing.

The final step of handling a ticket, confirming with the user that the issue is resolved, recording the resolution, and closing the record so it can be reported and reused.

The accumulated set of open tickets or improvement items not yet completed. Ageing backlogs signal capacity or prioritization problems and are a standard input to desk improvement planning.

The regular production and distribution of performance information, such as volumes, service level achievement, and trends, so stakeholders can make informed decisions about the desk.

A person who uses services and contacts the service desk for help, information, or requests. Understanding their roles, locations, and needs shapes desk channels and communication.