Loading
Because it is usually manual and reactive. Somebody notices a breach the morning after, and the escalation is really an apology with a different name.
An escalation moves a ticket to more senior or specialist attention when a defined condition is met.
Rules fire on the clock reaching a threshold, on a reopen, on a customer request, or on a state persisting. Each escalation names a person or rota and records why it fired.
A ticket hits eighty per cent of its resolution target with no owner activity for two hours. It escalates to the team lead while there is still time to act, rather than at the breach.
It will not create capacity. Escalating to a lead who is already at capacity moves the problem; the report will show that pattern if it is happening.
It notifies the named person, can reassign or raise priority, and appears in breach reporting whether or not the ticket later breached.
Yes, including on-call, read from Nest.
Yes, in stages, at thresholds you set.
Yes, and it is recorded as customer-requested.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.