What is Resolution Time?
The total time taken to fully resolve a customer's issue
What is Resolution Time?
Resolution time (also called time to resolution or TTR) measures the elapsed time from when a customer first contacts you to when their issue is fully resolved and the conversation is closed. Unlike average handle time (which measures agent work time), resolution time includes all waiting periods—time between replies, internal escalations, and any back-and-forth needed to reach a solution.
Resolution time is measured differently across channels. For live chat, it might be 10-20 minutes. For email, a few hours to a few days. For complex technical issues requiring engineering involvement, it could be weeks. Most teams track median resolution time rather than average, since a few outlier cases can skew the average significantly.
Why Resolution Time Matters
Zendesk research found that 72% of customers who gave negative satisfaction ratings cited slow resolution as the primary reason. Customers can tolerate a fast first response followed by a reasonable resolution timeline, but extended back-and-forth without progress erodes satisfaction rapidly.
Tracking resolution time by issue type reveals which problems need better documentation, tooling, or training. If "billing questions" resolve in 5 minutes but "integration issues" take 3 days, that tells you where to invest in better self-service resources or agent training.
Resolution Time in Practice
A team tracked their resolution times and found that conversations requiring escalation to engineering took an average of 4.2 days. The bottleneck was context transfer—engineers had to ask customers to re-explain the problem. By adding structured internal notes (steps to reproduce, error messages, customer environment details) to the escalation workflow, they cut engineering resolution time to 1.8 days. Customer satisfaction for escalated issues improved from 58% to 79%.