A gold-tier client raises a priority-two ticket at 17:42 on a Friday. The support group that owns their queue works a split shift, mornings and late afternoons, and Monday is a public holiday. The client is two time zones east of the desk. On Tuesday morning the service manager opens the SLA report and finds the ticket marked breached by fifty-odd hours, alongside a dozen others from the same weekend. None of them was late by any standard a client would recognise. The report says otherwise, so the monthly review starts with an argument about the report instead of the service.
Because the SLA clock kept running through hours nobody was contracted to work. A naive clock counts elapsed time. A slightly better one knows about weekends. Very few know about a split shift, a public holiday in one country but not another, or a client whose business day starts before the desk’s does. The gap between the clock and the calendar is where the false breaches come from, and it is also where real breaches hide, because a team that has learned to ignore the report stops seeing the ticket that genuinely slipped.
In Guardian PSA, response and resolution targets are set per priority and measured against a calendar that belongs to the support group. That calendar carries the shifts the group actually keeps, including split shifts, the public holidays that apply to it, and its time zone. A group that works 24/7 is configured as one. The clock pauses when the group is off and resumes when it is on, so the target reflects working hours rather than wall time.
The numbers in that ticket are an example, not a default; the calendar is yours to set. The point is the shape: the clock ran only during the shift, the warning fired while there was still time to act, and Monday’s holiday did not count against anyone.
Through per-customer tiers. The priority-to-target mapping is written once; a tier tightens it for the clients who pay for that. A gold client’s priority two carries a one-hour response target while a standard client’s carries a longer one, and the desk maintains one policy set rather than one per client. When you change the standard policy, the tiers move with it. This is the difference between a policy and a spreadsheet of exceptions.
Someone is paged before the breach, not after it. A configurable threshold on each target pages a person while the ticket can still be met. If the ticket is still unclaimed when the target arrives, escalation acts rather than reports: it can reassign the ticket, raise its priority or move it to another group, automatically. In the example above the on-shift lead was paged at 18:30 and claimed the ticket eleven minutes later. Had nobody claimed it, the escalation would have moved it to the second-line group before the shift ended, and the record would show that it did.
Escalation only works if the ticket is where it should be in the first place. That is why routing matters to the SLA: a ticket that lands in the right queue on the check that failed starts its clock in front of the right people. We covered that in Route the ticket on the check that failed.
Because the alternative is a report you correct by hand. When the desk and the monitor are one system, the ticket opened by a failing check inherits the client, the client’s tier and the group’s calendar at the moment it is created. There is no export to a reporting tool that applies its own idea of business hours, and no monthly job of explaining to a client why the report says breached when the technician answered in twenty minutes. The history of the ticket is append-only, enforced by the database, so the timestamps in the SLA record are the ones the client can rely on.
One reconciliation per month, per client whose SLA you report on, in which someone takes the breaches the tool reported and strikes out the ones that were weekends, holidays or a time zone. Then the harder cost: the ticket that was genuinely late, hidden in a list of false ones, that the client noticed before you did.
The one with the weekend breaches. We will walk a ticket through your calendar and show you the clock.