First contact resolution (FCR) is one of the oldest metrics in support operations, and still one of the most useful, because it directly captures customer effort rather than just agent throughput. A ticket resolved in one exchange is a meaningfully better experience than one requiring three back-and-forths, even if both eventually reach the same outcome.
The metric is simple to define; the interesting part is what actually moves it.
Direct answer
First contact resolution (FCR) is the percentage of customer support interactions resolved in a single contact, with no follow-up needed from the customer or a second touch from another agent. It's typically calculated as resolved-on-first-contact tickets divided by total tickets over a period. FCR is heavily influenced by whether agents have quick access to accurate, current reference material, an agent who has to guess or escalate to find the right answer directly lowers this number.
How it's calculated and why it's tracked
FCR is usually measured as: (tickets resolved without a follow-up contact or escalation) / (total tickets), over a given period. It's tracked because it correlates strongly with customer satisfaction, a resolved-in-one-touch experience consistently outperforms a multi-touch one in satisfaction surveys, even when the final outcome is identical.
What actually moves FCR
- Agent access to accurate, current internal and customer-facing documentation, guessing or escalating to check both cost the first-contact resolution.
- Clear escalation paths so an agent who genuinely needs another team doesn't stall the ticket unnecessarily.
- Consistent product knowledge across agents, inconsistent answers between agents often mean a follow-up contact to clarify.
- A help center the agent can confidently point the customer to for anything requiring more detail than the response allows.
Frequently asked questions
What's a good first contact resolution rate?
Benchmarks vary by industry and support complexity, so there's no single universal target. What matters more is the trend: an FCR rate that's declining, or that lags well behind comparable teams in your space, is worth investigating.
How is first contact resolution different from average resolution time?
Resolution time measures how long a ticket takes to close, even across multiple contacts. FCR measures whether it was solved in one contact at all, capturing a different (and often more customer-experience-relevant) dimension than speed alone.
Does documentation quality affect first contact resolution?
Yes, directly. An agent checking outdated internal notes or an out-of-date help center article is more likely to give an incomplete or incorrect answer, requiring a follow-up contact to correct it.
Conclusion
- First contact resolution measures whether an issue was solved in a single interaction.
- It correlates strongly with customer satisfaction, independent of final resolution time.
- Accurate, current reference material for agents is one of the strongest levers on FCR.
- DocsKoala keeps that reference material current automatically as the product changes.