Service Desk Guide
ITSM Fundamentals: Tickets, SLAs & Escalation
By Mithun K. Singh, Founder, Svasamm Research · 16 July 2026
A service desk succeeds or fails on a few fundamentals: getting tickets to the right person, holding to SLAs, and escalating before things break. This guide covers the core concepts and how to set them up so they actually work.
The building blocks
- Tickets & queues — structured intake routed to the right team.
- Categories & priority that drive routing and SLA.
- Incident vs problem — fix the outage, then the root cause.
- Knowledge base to deflect repeat questions.
SLAs that mean something
Set response and resolution targets by priority, measure against them per ticket, and make the clock visible to agents. An SLA nobody can see is an SLA nobody meets.
Define escalation before you need it: who gets notified, and when, as a ticket approaches its SLA — automatic, not a manual chase.
Escalation & self-service
- Automatic escalation when an SLA is at risk.
- Self-service portal so users raise and track their own requests.
- Knowledge articles that cut ticket volume.
- Reporting on SLA attainment and backlog.
Stand up a service desk that holds its SLAs
Bring your ticket categories and SLA targets, and we'll configure a working queue with you.