Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Agent |
How often targets are met, and how to read the number without being reassured by an average.
Build it
- The SLA dataset.
- Metric: the percentage of targets achieved.
- Attribute: by month, and by target type.
- Filter: the last six months.
Achievement, not average time
A target is met or missed. An average response time can look excellent while a fifth of tickets breach, because the fast ones outnumber the slow ones.
The percentage achieved is what the commitment says and what a customer experiences.
Split by target
First reply, next reply, resolution. They fail for different reasons: first reply is staffing, resolution is complexity or a dependency on somebody else.
A single combined figure hides which one is the problem.
Look at the breaches themselves
Not just the count. Read ten breached tickets and the cause is usually obvious and usually the same: an out-of-hours arrival, a specific customer type, a group with no cover.
Split by priority
Meeting the target on low priority and missing it on urgent is much worse than the combined number suggests, and it is a common shape.
Check the policy before the performance
A target nobody agreed, or one set to a round number years ago, produces breaches that mean nothing. Confirm the target is real before treating the number as a problem.
Report it with volume
Ninety per cent achievement on forty tickets and on four thousand are different achievements. Both numbers, always.
Comments
0 comments
Article is closed for comments.