Comwil

Service Desk

What is an IT service desk? Tiers, SLAs and KPIs

A clear guide to the IT service desk: what it does, how support tiers work, what to put in an SLA and which KPIs show whether it performs.

Published 7 November 20266 min readService Desk

Key takeaways

  • A service desk owns the whole process for incidents and requests, not just answering calls.
  • Three support tiers keep simple issues quick and complex ones with specialists.
  • Measure first-contact resolution, resolution time and satisfaction, not only ticket volume.
  • Write response and resolution targets per priority into the SLA.

What a service desk does

An IT service desk is the single point of contact between your employees and IT. It logs every incident (something is broken) and service request (someone needs something), resolves what it can at first contact and routes the rest to the right specialist.

It is often confused with a help desk. A help desk typically reacts to technical problems. A service desk is broader: it owns the process around incidents and requests and connects to wider IT service management such as problem and change management.

How support tiers work

Most service desks organise work in tiers so that simple issues stay cheap and quick, and complex ones reach people with the right skills.

  • Tier 1 (first line): logs tickets, resolves common issues such as password resets and standard how-to questions, and escalates what it cannot solve.
  • Tier 2 (second line): technicians who handle deeper problems with devices, applications, accounts and networks.
  • Tier 3 (third line): specialists and vendors for infrastructure, software defects and security incidents.

Clear escalation rules matter more than the number of tiers: who owns the ticket, when it moves and how the user is kept informed.

What belongs in the SLA

A service level agreement turns expectations into numbers both sides can check.

  • Priority definitions, for example what counts as critical, high, medium or low.
  • Response and resolution targets for each priority.
  • Coverage hours, including out-of-hours handling for critical issues.
  • How and how often performance is reported and reviewed.
  • What is excluded, so that nobody is surprised later.

The KPIs that matter

Ticket volume alone says little. These measures show whether the desk helps people.

  • First-contact resolution: the share of tickets solved without escalation.
  • Resolution time per priority against the SLA target.
  • Backlog and ticket age: how many tickets wait and for how long.
  • User satisfaction collected after closure.
  • Reopen rate: tickets that came back because the fix did not hold.
  • Volume by category, to spot problems worth fixing at the root.

Common mistakes

These show up again and again:

  • No knowledge base, so every ticket is solved from scratch.
  • Measuring only speed, which rewards closing tickets rather than fixing problems.
  • Unclear priorities, so everything is urgent.
  • No problem management, so the same incident returns every week.

Let’s talk about your IT

Tell us what you need. We will come back with a clear proposal and a named contact.