SLAs on an IT service desk: targets, timers and breach warnings

• A target per priority, for example a first response time and a resolution time for each of three or four priority levels.
• Business hours and holidays, so the timer pauses outside working time.
• Pause conditions, for example while the desk waits for the requester to reply.
• An escalation rule: who is told, or where the ticket moves, as the deadline approaches or passes.

ITIL 4 calls the wider practice service level management: agreeing targets that reflect what the business needs and checking delivery against them. The SLA timers in a service desk are the part of that practice the tool automates. See SLA and service level management in the glossary.

• Freshservice: SLA management from the Growth plan, $49 per agent per month [Freshservice pricing].
• Zendesk: SLAs from Suite Growth, alongside the service catalog, tasks and approvals [Zendesk Employee Service pricing].
• monday service: an SLA Monitoring Agent that 'flags at-risk tickets before SLA deadlines are missed' [monday IT page].
• Halo: AI suggestions for team routing and SLA-breach warnings [Halo AI].
• ServiceDesk Plus Cloud: SLA violation alerts through third-party notification channels, added in the 24 July 2026 release [ManageEngine release notes].
• Ivanti: service level management is among its 14 ITIL 4-certified practices [Ivanti].
• SysAid: service level management is listed on its home page [SysAid home page].

We did not record SLA details for Jira Service Management or ServiceNow ITSM on the pages we read, so ask both in a demo.

A report tells you last month's SLA performance. A warning gives an agent time to act on this ticket. When you test a tool, create a ticket with a short target, leave it untouched and note when and how the tool warns, who it tells, and whether it moves the ticket.

SLA timers usually start when a ticket is logged, depend on the priority set at categorisation, and drive escalation during routing. That is why a wrong category or priority at stage 02 can cause a breach later. The six stages lesson explains each stage.

1. Which plan includes SLA policies, and how many can we define?
2. Can timers pause for business hours, holidays and time spent waiting on the requester?
3. How are at-risk tickets flagged, and through which channels?
4. Can SLA targets differ for requesters outside IT, such as HR or facilities?