Resolution Rate
Definition
Resolution rate measures the proportion of support interactions that are closed with a successful resolution — the customer's issue is fully addressed — as opposed to tickets that are abandoned, unresolved, or pending indefinitely. It can be calculated for a specific period (e.g., percentage of tickets opened this week that were resolved this week) or for the total ticket lifecycle (percentage of all tickets ever opened that were eventually resolved). Resolution rate is a broader measure than FCR (which measures first-contact resolution); a ticket may be resolved on the third contact but still count toward resolution rate. Low resolution rates indicate systemic problems: issues the team cannot solve, process failures, or ticket abandonment.
Why It Matters
Resolution rate is a fundamental measure of support effectiveness. A support team that opens many tickets but resolves few is failing its customers and creating a backlog that erodes morale and response time. For AI chatbot deployments, resolution rate distinguishes between deflection (preventing contact) and resolution (actually solving the problem) — two related but distinct metrics. A chatbot that deflects contacts without resolving the underlying issue has poor resolution rate; one that deflects and resolves has high resolution rate. The distinction matters because unresolved issues lead to re-contact and churn.
How It Works
Resolution rate is tracked in the ticketing system as the ratio of tickets moved to 'Resolved' or 'Closed' status within defined time windows. Quality is validated through customer confirmation (customer marks issue resolved) or inactivity (ticket auto-closes after N days of no customer activity). Resolution rate can be segmented by issue type, channel, agent, customer tier, and time period to identify patterns. Unusually low resolution rates for specific issue types signal gaps in agent capability, product documentation, or product functionality that need addressing.
Resolution Rate — Weekly Dashboard
Total tickets
420
this week
Resolved
374
of 420
Resolution Rate
89%
Last month
86%
baseline
Resolution by channel
Resolution by ticket age
Real-World Example
A 99helpers customer finds their overall resolution rate is 87% — meaning 13% of tickets are never formally resolved. Investigating the unresolved backlog, they find two categories: tickets abandoned by customers (the customer likely resolved the issue independently or gave up), and tickets stuck awaiting a response from engineering. They implement an auto-close workflow for tickets inactive for 7 days after agent response, and create a dedicated escalation path that ensures engineering response within 5 days. Resolution rate improves to 96%.
Common Mistakes
- ✕Using ticket closure as a proxy for resolution — tickets can be closed without resolving the customer's issue; validate resolution through customer confirmation where possible
- ✕Not distinguishing between customer-abandoned tickets and truly unresolved tickets — abandoned tickets require different action than stuck tickets
- ✕Measuring resolution rate in isolation from CSAT — a 98% resolution rate with 2.5/5 CSAT indicates issues are being closed but not satisfactorily resolved
Related Terms
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.
Support Ticket
A support ticket is a record created in a help desk system that documents a customer's issue or request, tracks its status through resolution, and maintains the complete communication history between the customer and support team.
Customer Satisfaction Score
Customer Satisfaction Score (CSAT) is a metric that measures how satisfied customers are with a specific interaction, product, or experience, typically collected through a simple post-interaction survey asking customers to rate their satisfaction on a numeric scale.
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.
Deflection Rate
Deflection rate is the percentage of potential support contacts that are resolved through self-service, AI chatbots, or automated tools without requiring a human agent, measuring the effectiveness of automated and self-service support.
Ready to build your AI chatbot?
Put these concepts into practice with 99helpers — no code required.
Start free trial →