ronutz

The Roles · Who runs it

Service desk analyst

Written from published sources

The single point of contact between an organisation and the people who use its technology. The framework defines the service desk as the practice that captures demand for incident resolution and service requests, and the phrase that matters in that definition is single point of contact: a user reports a problem to one place, and the desk works out who owns it.

What the day looks like

  • Logging, categorising and prioritising whatever arrives, across every channel the organisation offers.
  • Investigating and diagnosing far enough to resolve at first contact, which is where the value concentrates.
  • Routing what remains to whichever specialist team owns it, which requires knowing the whole organisation.
  • Keeping ownership of the ticket through the routing, so the user has one thread rather than several.
  • Communicating status, which is most of what a waiting user actually wants.

What it answers for

  • Every contact being recorded, categorised and visible.
  • Ownership through to resolution, including while somebody else does the work.
  • The user knowing where their request stands.

What it is measured on

  • First-contact resolution rate.
  • Time to respond and time to resolve against the service level.
  • User satisfaction, and the volume handled per analyst.

Who it receives from

Users
The problem as they experience it, described in their own vocabulary.
Specialist teams
Resolutions, workarounds and the knowledge that raises first-contact resolution.
Change and release management
What is about to happen, which explains tomorrow's call volume.

Who it serves

Everyone in the organisation
One door, so that nobody needs to know which team owns their problem.
Specialist teams
A filtered queue, with the routine handled before it reaches them.
IT management
The clearest available picture of what the organisation is struggling with.

Who else has a stake

  • Department heads whose people are waiting.
  • The teams downstream, whose day is shaped by what the desk routes to them.
  • Vendors and managed providers, where a ticket eventually crosses out of the organisation.

What it takes

  • Breadth across everything the organisation runs, at the depth first contact requires.
  • Questioning that gets from a described symptom to a usable description.
  • Written clarity, since the ticket is what every later person reads.
  • Steadiness with people who are frustrated and whose day this has interrupted.

What the job turns on

The desk exists so that the routing knowledge lives in one place rather than in every head in the organisation. That makes first-contact resolution the honest measure and volume a misleading one: an analyst who resolves fewer tickets while raising what the team can handle alone has improved the service, and the numbers show it slowly. It also explains the ceiling — a desk kept purely at intake stays a switchboard, and one given time to learn becomes the reason specialists are left alone.

The published sources

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice