Resolution Rate
Definition
Resolution Rate
Resolution rate is the share of cases, tickets, or contacts that are closed with the customer’s problem actually fixed. It is closure with the fix included, which is precisely what separates it from a plain count of tickets that were simply marked closed.
Closure is an administrative act — resolution is an outcome, and the two diverge more often than most reports admit.
Cases closed for inactivity are the clearest example. The ticket disappears from the queue — while the customer’s problem sits exactly where it was.
Any resolution rate worth publishing therefore needs a written rule about what closure reasons count. Without one, the figure drifts upward every quarter without anything improving.
Buyers should ask for that closure taxonomy before accepting any reported figure. A rate quoted without the list of excluded reasons is a claim rather than a measurement.
Key takeaways
- Resolution rate counts cases closed with the underlying problem genuinely fixed.
- Closure for inactivity, duplication, or reassignment should be excluded.
- Confirming resolution with the customer is what makes the figure defensible.
- A resolution rate always belongs beside a repeat contact measure.
How it works
Count the cases closed in a period, subtract those closed for administrative reasons, then divide the genuine resolutions by total cases handled. Publish the excluded categories alongside the rate so the basis stays visible.
Confirmation is the strongest control available. Asking the customer whether the issue is resolved converts an internal judgement into an observed fact.
| Closure reason | Counts as resolved | Why |
|---|---|---|
| Fixed and confirmed | Yes | Outcome verified with the customer |
| Fixed, unconfirmed | Usually | Verify by sampling rather than assuming |
| Closed for inactivity | No | Nothing was actually fixed |
| Duplicate or reassigned | No | The work moved rather than finished |
Categorising closures this way is more useful than any single percentage. It shows exactly where an inflated rate is coming from.
Public service measurement takes the same outcome-first line. The customer experience programme at Performance.gov evaluates services by whether people complete what they came to do, not by whether a case file was closed.
Satisfaction research supplies the commercial argument. The American Customer Satisfaction Index links satisfaction to retention and financial performance — and an unresolved issue behind a closed case damages both at once.
Examples
Resolution reporting varies by channel, by case complexity, and by how disciplined the closure rules happen to be. Four cases show where a reported figure drifts away from what customers actually experienced.
A telecoms support centre. The reported rate was 94% until inactivity closures were separated out, at which point it fell to 79%. Nothing about the service had changed.
A Manila back-office team. Customer confirmation was added by automated email. Two percent of confirmed cases were reopened, which turned out to be a reasonable accuracy check on the rest.
An enterprise IT desk. Cases reassigned to engineering counted as resolved by the first-line team. Reporting them as transfers gave a much clearer view of where capability was missing.
A utility complaints function. Regulatory rules define resolution precisely, so the closure taxonomy is externally set. The reported rate is auditable rather than negotiable.
Related terms
Resolution rate sits among the closure, timing, and escalation measures that describe how cases finish. The terms below cover the variants and the roles involved.
- First Call Resolution: resolution achieved on the first contact.
- Calls Resolved on First Call: the raw count behind that percentage.
- Resolution Time: how long resolution took, rather than how often it happened.
- Escalation: the route for cases the first team cannot resolve.
- Ticket Support Agent: the role closing most of the cases.
- Service Level: the standard resolution performance is judged against.
- Key Performance Indicator (KPI): the reporting family the rate belongs to.
FAQ
What is a good resolution rate?
Most support operations target 85% to 95% once administrative closures are excluded. Regulated complaint handling often works to a higher externally set bar.
How is resolution rate different from closure rate?
Closure rate counts every case removed from the queue. Resolution rate counts only those where the problem was genuinely fixed.
Should cases closed for inactivity count?
No. They represent an abandoned customer rather than a solved problem, and including them inflates the figure substantially.
How can resolution be confirmed?
Ask the customer, by email, survey, or a short follow-up. Sampling works when confirming every case is impractical.
Does reassignment count as resolution?
Not for the team that reassigned it. The case resolves wherever the work is actually completed, so record the transfer to keep capability gaps visible.
What should be reported alongside it?
A repeat contact measure, which shows whether resolutions held. The two together are far harder to misread than either alone.
Compare support providers and their resolution reporting across the Outsource Accelerator BPO hubs.
Independent
