Why Time to Resolution matters
A decrease can mean issues are being solved faster. An increase may reflect complexity, backlog, staffing, or a change in case mix rather than weaker agent performance alone.
- Business question
- How long does a customer issue typically remain unresolved?
- Teams that use it
- Customer support, service operations, customer success, product, and quality teams.
- Decisions it supports
- Staffing, routing, escalation, self-service content, process changes, and recurring issue prioritisation.
Time to Resolution formula
Total Resolution Time ÷ Total Cases
Formula components
- Resolution time
- Elapsed or business time from the defined case start to final resolution.
- Total cases
- Resolved cases included in the same period and queue scope.
- Pause rules
- Whether time waiting for the customer or another team is excluded.
- Reopened cases
- Cases that close and reopen, handled under an explicit final-resolution rule.
How to calculate Time to Resolution
- Define when the clock starts and stops and whether it uses elapsed or business hours.
- Select cases finally resolved in the reporting period.
- Calculate resolution time for each included case under the same pause rules.
- Sum resolution time and divide by resolved cases; review the median and distribution too.
Time to Resolution example
A support team resolves 240 cases in a week. Under its business-hour clock, those cases accumulate 1,920 hours of resolution time.
- Total resolution time = 1,920 business hours.
- Total resolved cases = 240.
- Average Time to Resolution = 1,920 ÷ 240 = 8 hours.
Average Time to Resolution is 8 business hours.
A resolved case took eight business hours on average, but the team should inspect percentiles to see whether a few long cases inflated the mean.
How to interpret the result
Segment by issue type, severity, channel, product, and escalation path. Pair speed with satisfaction and reopen rate so fast closures do not replace durable solutions.
Expected resolution time varies by complexity, service hours, support tier, channel, and customer dependencies. A universal benchmark is rarely meaningful.
Common mistakes and limitations
- Open cases excluded from the story
- A resolved-only average can improve while a difficult backlog grows.
- Mixed clock definitions
- Elapsed hours and business hours are not comparable.
- Misleading averages
- A small number of extreme cases can dominate the mean.
- Premature closure
- Closing cases quickly can lower the metric while increasing reopens.