Resolution Rate
Resolution rate is the percentage of customer support issues that are fully resolved within a defined scope, whether that is a single interaction, a specific channel, or a set time period. An issue is "resolved" when the customer's problem is completely addressed and no further action is required from either party. It is the most basic measure of whether your support function is actually solving problems or just processing tickets.
The metric seems straightforward, but defining "resolved" is where most companies struggle. A ticket marked as closed is not necessarily resolved. A customer who stops replying might have given up, not gotten their answer. A workaround that addresses the symptom but not the root cause is a deferral, not a resolution. Measuring resolution rate honestly requires understanding whether the customer's underlying problem was genuinely fixed, which is harder than counting closed tickets.
Resolution rate matters because it sits at the intersection of customer experience and operational efficiency. A high resolution rate means customers are getting their problems solved and your team is not wasting effort on repeat contacts and reopened tickets. A low resolution rate means problems are bouncing around, customers are getting frustrated, and your support costs are inflated by redundant work on the same issues.
Why it matters for SaaS
In SaaS, every unresolved issue is a small withdrawal from the customer's willingness to renew. Individual unresolved issues rarely cause churn directly, but they accumulate. A customer who experiences three unresolved or poorly resolved issues in a quarter is measurably more likely to churn than one whose issues are consistently handled well. Zendesk research shows that customers who have a single bad support experience are 50% more likely to switch to a competitor. Customers who have two bad experiences are over 80% more likely to leave.
The economics of resolution rate are also notable. An unresolved issue does not just disappear. It becomes a reopened ticket, a follow-up email, a second call, sometimes an escalation to engineering or management. Each additional touch multiplies the cost. Industry benchmarks suggest that the average cost to resolve a ticket on first contact is $7-12, while a ticket that requires three or more interactions costs $25-45. For a support organization handling 10,000 tickets per month, improving resolution rate by 10 percentage points can save hundreds of thousands of dollars annually.
For PLG companies, resolution rate has an outsized impact because many customers are self-serve and paying relatively low amounts. If it costs more to support a customer than they pay, the unit economics do not work. High resolution rates make support sustainable at PLG price points because each issue is handled once, efficiently, without the overhead of escalations and re-contacts.
How it works in practice
A B2B SaaS company tracks resolution rate across three dimensions: first-contact resolution (resolved in a single interaction), channel resolution rate (resolved within the channel where the issue was raised, without needing to transfer), and time-based resolution (resolved within the SLA target, typically 24 hours for standard issues). Each dimension tells a different story about support quality.
Their analysis reveals that first-contact resolution is 72% for their chat channel but only 55% for email. Investigation shows that chat agents can ask clarifying questions in real time and resolve ambiguity immediately, while email agents often guess at the problem, provide a solution that does not match, and then wait for the customer to reply that it did not work. The company shifts resources toward chat, builds better email templates that ask for diagnostic information upfront, and watches the email resolution rate climb to 65% over the next quarter.
Another company discovers that their overall resolution rate is high at 85%, but resolution rate for issues related to their API integration module is only 40%. Most API issues require engineering involvement, which means tickets sit in a queue, get passed between teams, and take days to resolve. Rather than accepting this as inevitable, they invest in better API error messages, a troubleshooting guide specific to common integration failures, and an in-product diagnostic tool that helps users self-diagnose configuration problems. Within three months, the API integration resolution rate improves to 70%, and the volume of API-related tickets drops by 30%.
The most impactful use of resolution rate data is identifying systemic product problems. When resolution rate is persistently low for a specific feature area, it signals that the product itself needs attention, not just the support process. A feature that generates 200 tickets per month with a 50% resolution rate is not a support problem. It is a product problem that happens to manifest in the support queue.
Resolution Rate vs First-Contact Resolution
First-contact resolution, or FCR, is a specific type of resolution rate: it measures the percentage of issues resolved in a single interaction, without any follow-up needed. Resolution rate is the broader metric that measures whether issues are eventually resolved, regardless of how many interactions it takes.
FCR is a more demanding standard and a better indicator of customer experience. A customer whose issue is resolved in one interaction has a completely different experience than one whose issue takes three interactions over a week. Both count as "resolved" in the general resolution rate, but only the first counts toward FCR. For this reason, many support teams track both: overall resolution rate to ensure issues are being closed, and FCR to ensure they are being closed efficiently.
The tradeoff is that optimizing exclusively for FCR can lead to premature closure. Agents under pressure to resolve on first contact might mark complex issues as resolved before fully confirming the fix, or provide quick workarounds that do not address root causes. Healthy support organizations track FCR alongside reopen rate to ensure that first-contact resolutions are actually sticking.
How Floe approaches this
Floe improves resolution rates by resolving common issues before they become support tickets. When a user encounters friction in the product, Floe's AI agent can provide immediate, contextual assistance: answering questions about the current screen, walking the user through a confusing workflow, or explaining an error message in plain language. Issues that would have generated a ticket are resolved in the moment, within the product, on the first interaction.
For SaaS companies, this means the issues that do reach the human support team are the genuinely complex ones that require human judgment, not the routine questions that could have been answered with better in-product guidance. The human team sees a higher resolution rate because they are handling a filtered set of issues that are actually appropriate for human resolution, and users get a better experience with immediate answers instead of waiting for a ticket response.
FAQ
What is a good resolution rate benchmark? Industry benchmarks for overall resolution rate in B2B SaaS range from 70-85%, with top performers above 90%. First-contact resolution benchmarks range from 65-75%. These vary widely by product complexity, customer segment, and support channel. More important than hitting a specific number is understanding your resolution rate by issue category and identifying the areas where unresolved issues are concentrated. A company with 80% overall resolution but 30% resolution on billing issues has a very specific, fixable problem.
How do you accurately measure whether an issue is truly resolved? The most reliable method is customer confirmation: after closing a ticket, send a brief follow-up asking whether the issue was fully resolved. Track the percentage of customers who confirm resolution versus those who reopen or indicate the problem persists. Automated methods include monitoring whether the user repeats the same action or visits the same help article within a set window after the ticket is closed. A combination of explicit confirmation and behavioral monitoring gives the most accurate picture.
Does automating support hurt resolution rates? It depends entirely on what you automate. Automating routine, well-understood issues with clear solutions typically improves resolution rates because the response is instant and consistent. Automating complex, ambiguous issues with canned responses typically hurts resolution rates because the response does not match the problem. The key is knowing which issues are genuinely routine and automating only those, while routing complex issues to humans who can handle the nuance.