What is resolution rate?

Resolution rate, explained

Resolution rate asks the question every support team cares about: did the customer get what they needed? For human support, it is typically the share of tickets closed as solved. For AI support, it is often the share of bot conversations that ended without escalation, sometimes with an extra condition such as a positive rating or no follow-up within a set period.

That variation is the main thing to understand. One tool may count any conversation the customer did not escalate. Another may require explicit confirmation. A third may count billable “resolutions” that include some handoffs. Comparing percentages across tools without checking definitions is comparing different units.

Resolution rate is most useful as a trend within one tool and one definition, broken down by topic. A high overall rate can hide a weak area such as returns if easy questions dominate the sample.

Validate it the same way as deflection: check whether customers come back about the same issue, what they rated the conversation, and whether a reviewer agrees the answer was correct.

How to measure it

Write down what counts as resolved (no escalation, customer confirmation, no repeat contact within N days) and keep it fixed when comparing periods.

Common mistake

How SuperBot relates

SuperBot's analytics track resolution rate alongside CSAT, sentiment and knowledge gaps, so you can read the rate next to how customers felt and what the bot could not answer.

• AI chatbot evaluation checklist
• Compare support platforms
• Support cost calculator

Frequently asked questions

Related terms

• First contact resolution (FCR)First contact resolution (FCR) is the percentage of customer issues fully resolved in the first interaction, with no follow-up, transfer or repeat contact needed. It is one of the most customer-centred support metrics because having to contact a business again about the same problem is a common source of frustration.
• Deflection rateDeflection rate is the percentage of customer questions answered by self-service, such as a chatbot, help centre or FAQ, without creating a ticket or reaching a human agent. It estimates how much work automation keeps away from the support team, but it does not by itself prove the customer's problem was solved.
• Ticket deflection vs resolutionTicket deflection means a customer question was handled without reaching a human agent. Resolution means the customer's problem was actually solved. Every resolved self-service conversation is deflected, but not every deflected conversation is resolved: customers who give up or come back later also count as deflected, which is why deflection alone overstates success.
• Customer satisfaction score (CSAT)Customer satisfaction score (CSAT) measures how satisfied customers are with a specific interaction, usually from a one-question survey such as “How satisfied were you with this conversation?” on a 1–5 scale. CSAT is the percentage of respondents who choose the top ratings, typically 4 or 5, out of everyone who responded.
• Fallback rateFallback rate is the percentage of chatbot messages or conversations where the bot could not produce a confident answer and fell back to a default response, such as “I'm not sure” or an offer to contact a person. It measures how often customers ask things the bot's knowledge or rules do not cover.