First Contact Resolution (FCR)
First Contact Resolution (FCR) is a customer support metric that measures the percentage of customer issues fully resolved during the first interaction, without requiring follow-up contacts, callbacks, escalations, or additional tickets. Also called first-call resolution or one-touch resolution.
How it works
FCR is calculated as:
FCR = (Issues resolved on first contact / Total issues) x 100
Measuring FCR accurately requires defining "resolved", typically a combination of: - No follow-up ticket from the same customer on the same issue within 72 hours - Customer confirmation of resolution (positive feedback) - Agent marks issue as resolved (less reliable as a standalone signal)
FCR is considered the most important support metric because it directly measures whether customers actually got their problem solved. A team with fast response times but low FCR is responding quickly without actually helping.
Operational Review
In practice, first contact resolution (fcr) should be evaluated by what it changes in the support workflow. Ask whether it improves answer accuracy, reduces repeated agent work, clarifies handoff decisions, or makes reporting easier. If the answer is only "it sounds modern," the concept is not yet operational.
A concrete example is ai chatbot achieving high fcr: A SaaS company measures FCR for AI chatbot interactions by tracking whether customers return with the same issue within 72 hours. The AI achieves 85% FCR on supported topics, matching human agent performance, because RAG retrieves comprehensive answers rather than partial information.
The simplest takeaway is: FCR measures the percentage of issues fully resolved on the first interaction without follow-ups
Why it matters
How Chatsy uses first contact resolution (fcr)
Real-world examples
Key takeaways
Frequently asked questions
What is a good first contact resolution rate?
Industry benchmarks: 70-75% is average, 80%+ is good, 90%+ is excellent. FCR varies significantly by industry and issue complexity. Technical support typically has lower FCR (60-70%) than billing support (80-90%) because technical issues are more complex.
How do you measure FCR accurately?
The most reliable method is the "72-hour re-open" rule: if the same customer contacts you about the same issue within 72 hours, the original contact is counted as not resolved on first contact. Supplement with customer confirmation ("Was your issue resolved?") for additional accuracy.
Does fast response time guarantee good FCR?
No. A team can respond in 5 seconds with an inaccurate or incomplete answer, resulting in fast response time but low FCR. The best support teams optimize for both: fast AND complete first responses. AI chatbots with RAG achieve both by responding instantly with comprehensive, grounded answers.
How can I improve FCR for my support team?
Improve knowledge base coverage for top topics, train agents on complete resolution (not just first response), implement AI chatbots with RAG for accurate first answers, analyze repeat contacts to identify gaps, and ensure agents have the tools and permissions to resolve issues without escalation.