Resolution Time
Definition
Resolution time (also called time to resolution or TTR) measures the full duration of a support issue lifecycle — from the customer's first contact to complete resolution. Unlike response time (which measures only the first reply) or handle time (active agent time), resolution time captures the total customer-perceived wait. An issue may have a fast first response but a long resolution time if it requires multiple back-and-forths, specialist escalation, or engineering involvement. Resolution time is a key SLA metric for most support tiers and correlates strongly with customer satisfaction — the faster an issue is fully resolved, the higher the satisfaction.
Why It Matters
Resolution time is the metric that most directly captures the customer's actual experience of a support interaction. Customers do not care primarily about how quickly they received a first response — they care about how quickly their problem was solved. An issue that receives a fast first response but takes 5 days to resolve is experienced as a poor support interaction regardless of the excellent initial response time. For AI chatbot deployments, containment rate and resolution time work together: issues contained by the AI have near-instant resolution time, dramatically improving the average compared to human-handled issues.
How It Works
Resolution time is tracked from ticket creation to resolution status in the ticketing system. Most help desks calculate this automatically and provide reports segmented by issue type, channel, customer tier, and agent. Resolution time improvement involves: identifying issue types with disproportionately long resolution times, investigating root causes (lack of agent authority, missing information, slow engineering response, unclear escalation paths), and addressing those root causes. Targets for resolution time vary by issue priority and customer tier — critical P1 issues may have a 2-4 hour resolution target while low-priority requests may have 5 business day targets.
Resolution Time — Distribution & SLA Compliance
Tickets resolved by time bucket
Median resolution time
3h 20m
SLA compliance
87% within SLA
Same-day resolution
55%
Factors affecting resolution time
Issue complexity
Technical bugs take longer
Support tier
Enterprise gets priority queue
Channel
Chat resolves faster than email
Real-World Example
A 99helpers customer tracks resolution time by issue category and finds that technical integration questions have an average resolution time of 8.3 days — far higher than their 3-day target. Investigation reveals that integration questions require engineering input, and engineers respond to support requests only once per week during a designated support rotation. They establish a daily engineering support rotation and create self-service documentation for the 15 most common integration questions. Average resolution time for integration issues drops to 2.1 days.
Common Mistakes
- ✕Confusing resolution time with handle time — resolution time includes waiting periods on both sides; handle time is only active agent involvement
- ✕Not segmenting resolution time by issue type — averaging resolution time across simple password resets and complex multi-team engineering issues produces meaningless aggregates
- ✕Setting uniform resolution time targets regardless of priority — critical issues need resolution time targets of hours, not days
Related Terms
Service Level Agreement
A Service Level Agreement (SLA) is a commitment between a support team and its customers (or internal stakeholders) that defines expected response times, resolution times, and other measurable service standards.
First Contact Resolution
First contact resolution (FCR) is the percentage of customer support interactions resolved completely during the first contact, without requiring the customer to follow up or the issue to be escalated.
Response Time
Response time is the elapsed time between a customer submitting a support request and receiving the first substantive reply from a support agent or automated system, a key metric for customer experience and SLA compliance.
Average Handle Time
Average Handle Time (AHT) is the mean total time an agent spends on a customer interaction, including talk time, hold time, and after-interaction wrap-up work, used to measure support efficiency.
Support Analytics
Support analytics is the collection and analysis of operational data from customer support activities — ticket volume, resolution times, satisfaction scores, and agent performance — to drive data-informed decisions and continuous improvement.
Ready to build your AI chatbot?
Put these concepts into practice with 99helpers — no code required.
Start free trial →