Playbook · IT service management
SLA and Escalation Playbook
Design SLA clocks, warnings and escalation chains that reflect how your service desk really works. An SLA that ignores real waits, working hours and escalation is just a number on a dashboard. This playbook shows how to configure ITDesk SLA policies so breaches are predicted and handled, not discovered.
What you will learn
Inside the playbook
- How timer modes and calendars change what the clock counts
- When the clock should pause, and the defaults ITDesk uses
- How to match the right policy to the right ticket
- How warnings and four-level escalation chains work
- How to keep vendors inside the SLA process
Key takeaways
Three ideas to take away
Choose calendar or business-hours timing deliberately, and set the right calendar.
Pause only for waits you cannot control. Vendor waits pause by default.
Warn at a percentage of the target, then escalate in levels.
Contents
What each section covers
- Before you startWhat you need to decide.
- Choose how the clock countsTimer mode and calendars.
- Set targetsResponse and resolution.
- Decide when the clock pausesWaiting is not always your fault.
- Match policies to ticketsWho gets which SLA.
- Warnings and escalationAct before the deadline, not after.
- Bring vendors inside the processKeep third parties visible.
- Review every weekTune with evidence.
Get the full playbook
Register once and download the PDF. It is written for IT operations and security teams.