A breach found in the monthly report
Your managed contracts come in three tiers, with different response targets and hours of cover. A few older clients are on bespoke terms. The PSA's service level settings were configured years ago and some clients were never moved to the right one when they upgraded.
At month end, the service manager runs the report. A priority one ticket for a top-tier client sat for longer than its response target on a Tuesday afternoon, because it came in by phone, was logged late and was set to priority three. A bottom-tier client's ticket shows as breached overnight, even though their contract only covers office hours. The report is both too harsh and too lenient, and nobody trusts it.
Why target tracking goes wrong
Service levels depend on several things at once, and most PSAs make it easy to set them up once and hard to keep them right.
- Clients' tiers change at renewal but PSA settings do not.
- Hours of cover differ by tier, and bank holidays are handled inconsistently.
- Priority is set at logging and not always revisited.
- Waiting-on-client time should pause the clock under some contracts but not others.
- Breaches are discovered after the fact rather than prevented.
Channels matter too. Tickets from the portal and email get timestamps automatically, while phone calls are logged whenever the engineer finishes the call and gets to the keyboard. A response target measured from the logging time rather than the call time flatters the phone channel and hides real delays.
What unreliable tracking costs
| Problem | Effect |
|---|---|
| Targets missed without warning | Clients notice before you do |
| Wrong tier applied | Top clients treated like standard ones |
| Clock not paused | False breaches that make reports untrustworthy |
| Report not trusted | Service levels stop being managed at all |
| No per-client view | Renewal conversations without service evidence |
Your contracts define the targets and how they are measured. We apply those definitions, we do not add promises of our own.
Live target tracking we build
- A service level table per contract tier and for each bespoke contract: priorities, response and resolution targets, hours of cover, holiday calendar and pause rules, entered from your contracts.
- Each client linked to its tier, checked against the contract register so upgrades and downgrades are applied from the right date.
- Live calculation of each open ticket's time remaining against its targets, following hours of cover and pause rules.
- Warnings to the service desk board and Teams channel when a ticket approaches its target, ordered by time remaining.
- A priority check prompting the engineer when a ticket's description suggests a higher priority, such as 'nobody can log in'.
- Monthly reports per client showing performance against their own targets, with pauses and exclusions listed, so the report can be shared as it is.
The service desk, working to the right clock
The service desk board shows tickets ordered by time remaining against each client's actual targets, not by age. The top-tier priority one that came in by phone jumps to the top the moment it is logged, and the warning goes to the team channel before its target, not after. The bottom-tier ticket logged at six in the evening shows its clock starting at the next morning's opening time, as the contract says.
At month end, the report is one the service manager is happy to share with clients. Breaches are real, few, and each has a reason attached. The account manager takes a client's service record into the QBR and the renewal, and it stands up to questions.
Bespoke contracts stop being a special case that only one person understands. A client with extended hours on a Saturday morning, or a different priority definition written into their contract years ago, has its own row in the service level table, and every engineer's board applies it without anyone having to remember. When that client renews onto a standard tier, the change is made in one place from the renewal date.
Checklist: your service level tracking
- Your service level report is not trusted by your own team.
- Clients' tiers in the PSA do not match their contracts.
- Breaches are found at month end, not prevented.
- Tickets waiting on clients count against your targets when they should not.
- Tickets logged by phone often get the wrong priority.