First Contact Resolution (FCR) is the percentage of customer support inquiries that are fully resolved during the initial interaction without requiring any follow-up contacts, transfers, or escalations, serving as a key indicator of support efficiency and customer satisfaction.
First Contact Resolution is widely regarded as one of the most impactful metrics in customer support. When a customer reaches out with a question or issue and gets it completely resolved in a single interaction — no callbacks, no follow-up emails, no transfers — both the customer and the support team benefit. The customer gets what they need immediately, and the team avoids the cost and complexity of multiple touchpoints.
FCR matters because repeat contacts are expensive and frustrating. Every unresolved interaction generates at least one additional contact, doubling the cost. If that follow-up also fails, the cost triples. Research from the Service Quality Measurement Group found that for every 1% improvement in FCR, there is a 1% improvement in customer satisfaction. It is one of the few metrics with such a direct, linear relationship to satisfaction.
Several factors influence FCR rates. Agent knowledge and training are foundational — agents need to know the product deeply enough to resolve diverse issues. Access to information is equally critical — if agents must navigate multiple systems to find answers, resolution slows and accuracy drops. Empowerment matters too — agents who must seek approval for common actions (refunds, account changes) cannot resolve issues on first contact.
AI chatbots have a nuanced relationship with FCR. For routine questions with documented answers, AI achieves very high FCR rates because it can instantly retrieve and present the correct information. For complex issues that exceed the AI's capabilities, the initial AI interaction may not count as resolution, and the customer must be connected to an agent. The key is ensuring the handoff to an agent is seamless so the agent can resolve the issue on that second contact without requiring yet another follow-up.
Improving FCR requires a systematic approach: analyze the reasons for repeat contacts, expand the knowledge base to cover gaps, train agents on common multi-step resolutions, empower agents to take action without approval, and ensure AI escalations include complete context so agents can resolve immediately.
Calculate FCR as: (Issues resolved on first contact / Total issues) x 100. A good FCR rate for B2B SaaS support is 70-75%, with best-in-class teams achieving 80%+. Measure FCR by tracking whether a customer contacts support again about the same issue within 3-7 days. Alternatively, ask customers directly: "Was your issue resolved?" after the interaction. Segment FCR by channel, issue type, and agent to identify patterns. Track repeat contact rate (the inverse of FCR) to understand which topics most frequently require multiple interactions.
Corebee drives high first contact resolution rates through two mechanisms. First, the AI chatbot resolves routine questions completely on the first interaction by drawing accurate answers from your knowledge base. Second, when issues escalate to human agents, the shared inbox provides the full conversation history, customer context, and relevant knowledge base articles — equipping agents with everything they need to resolve the issue without further follow-up.
Learn MoreFirst response time (FRT) is the amount of time between when a customer submits a support request and when they receive the first meaningful reply from a support agent or AI system, excluding automated acknowledgment messages.
Customer Effort Score (CES) is a customer experience metric that measures how much effort a customer had to exert to resolve their issue, complete a transaction, or get their question answered, typically measured on a 1-7 scale from "very low effort" to "very high effort."
Average Handle Time (AHT) is a customer support metric that measures the average total duration of a customer interaction, including the time spent actively communicating with the customer, any hold time, and post-interaction work such as note-taking and ticket documentation.
CSAT (Customer Satisfaction) score is a metric that measures how satisfied customers are with a specific interaction, product, or service, typically collected through a post-interaction survey asking customers to rate their experience on a scale of 1-5 or 1-10.
A good FCR rate for B2B SaaS support is 70-75%, with best-in-class teams achieving 80% or higher. The benchmark varies by channel — chat and phone tend to have higher FCR than email because of real-time back-and-forth. AI chatbots can achieve 85%+ FCR for routine questions within their knowledge domain. Track FCR trends over time rather than comparing to external benchmarks.
FCR has one of the strongest correlations with customer satisfaction of any support metric. Research shows that for every 1% improvement in FCR, CSAT improves by approximately 1%. Customers who resolve their issue on the first contact are 2-3 times more likely to rate the experience positively. The relationship is intuitive — nobody enjoys having to contact support multiple times for the same issue.
Common causes of low FCR include knowledge gaps (agents lack information to resolve issues), insufficient agent empowerment (agents must seek approval for common actions), poor documentation (knowledge base does not cover frequent questions), complex product issues that genuinely require investigation, and inadequate tooling (agents must switch between multiple systems). Analyze your repeat contacts to identify the specific causes in your organization.
See how Corebee uses AI to deliver instant, accurate support at a flat $99/month.