The service desk: what kind of ticket is this?
▶ Start the interactive lesson
Your first day on Burrow's service desk. The phone rings four times in ten minutes. A laptop won't start. Someone wants a second monitor. The Wi-Fi in the warehouse has dropped for the third time this week. And a manager wants Teams installed on everyone's laptop on Friday. Priya, the desk lead,…
Why the desk sorts every call
A service desk can get hundreds of calls a day. If everything goes into one pile, urgent outages wait behind people asking for a new mouse.
Four kinds of work
Something broke that used to work: "my laptop won't boot", "the printer is offline". Goal: get the person working again, fast.
A ticket's life
Every ticket moves through the same stages: logged (who, what, when), categorised and prioritised, worked on (maybe passed to another team), resolved, and closed once the user confirms it works.
First contact, first fix
The desk tries to fix things on the first call when it can: password resets, simple how-to questions, a stuck print queue. This is called first-contact resolution and it's one of the main numbers desks are measured on.
Key points
- Every contact becomes a ticket, sorted by type: incident (broken), service request (wants something), problem (the cause behind repeats), change (a planned modification).
- Lifecycle: logged → categorised and prioritised → in progress → resolved → closed. On hold pauses the clock while you wait on the user.
- Aim for first-contact resolution. When you pass a ticket on, write what you've already checked.
Words you'll learn
Incident · Service request · Problem · Change · Ticket · First-contact resolution (FCR) · On hold / pending · ITSM