The SLA clock: targets, risk and breach
Every ticket runs on an SLA with two distinct targets: a first-response target (how quickly someone acknowledges and replies) and a resolution target (how quickly it is actually solved). These are separate on purpose — a fast first response buys trust even when the fix takes longer — and both are driven by the ticket's priority, so an urgent ticket has tighter targets than a routine one.
The clock is a live signal, not a report you run later. Timers show what is due soon and what is already at risk, so agents and leads can triage by urgency rather than by whoever shouts loudest. When a target is missed the ticket breaches, which escalates it and makes it visible to management — the point is that a slip surfaces on its own instead of being discovered by an unhappy customer.
Because targets follow priority, honest prioritisation at intake is what makes the whole system work. Marking everything "urgent" is self-defeating: it tightens every clock, floods the at-risk view, and hides the genuine emergencies. Set the real priority, and the SLA numbers become a trustworthy map of where attention is needed.
Key takeaways
- Two targets: first-response and resolution — tracked separately.
- Targets are driven by priority; higher priority means tighter targets.
- Timers surface due-soon and at-risk work live; a breach escalates and is visible to managers.
- Honest prioritisation is essential — inflating priority defeats the SLA.