First Call Resolution (FCR) is the percentage of customer contacts resolved completely on the first interaction, with no repeat contact needed within a defined window (typically 7 days). Industry average is 70–75%. Top-quartile contact centers achieve 80–85% FCR.
Definition
First Call Resolution measures whether the customer’s issue was fully handled on the first contact, without the need to call back, email again, or reopen the issue later. It is one of the strongest indicators of whether a contact center is truly solving problems instead of only closing interactions.
Customers care about FCR because repeat contact feels like failure. Leaders care because every repeat contact adds queue load, labor cost, and frustration. That is why FCR sits near the center of many contact center scorecards, even though the underlying measurement is more contested than most dashboards admit.
Formula
The usual formula divides contacts resolved on the first interaction by total contacts. The hard part is not the math. It is defining “resolved.” Most teams use a repeat-contact window, often 7 days, and ask whether the customer came back about the same issue during that time.
Example: if 1,000 customers contacted support and 760 did not recontact within the defined same-issue window, operational FCR would be 76%. Change the window to 3 days or 14 days and the number can move meaningfully, which is why the definition must stay fixed once reporting begins.
Benchmarks
| Vertical | Top quartile | Good | Average | Below average |
|---|---|---|---|---|
| B2B SaaS support | >85% | 75–85% | 65–75% | <65% |
| Collections | >82% | 72–82% | 62–72% | <62% |
| Insurance enrollment | >85% | 75–85% | 65–75% | <65% |
| Technical support | >80% | 70–80% | 60–70% | <60% |
Why FCR measurement is contested
There are two big debates. The first is the repeat-contact window. Some teams use 24 hours, some use 3 days, and many use 7 days. Longer windows catch more unresolved issues but can also pull in unrelated follow-up. The second debate is same-issue identification. If a customer calls back about billing after first calling about login trouble, that should not count as failed FCR. If the follow-up is about the same payment plan that was not explained clearly, it probably should.
Those choices matter enough that FCR can become unreliable across teams unless everyone uses the same rules. One reason leaders struggle with FCR is that the number looks simple while the operational logic behind it is anything but simple.
Customer-reported vs. operational FCR
Customer-reported FCR comes from survey questions like, “Was your issue resolved today?” It captures the customer’s view, which is valuable because a case can look closed in the CRM and still feel unresolved to the person who called. Operational FCR uses system data to check whether the customer returned about the same issue.
Neither method is perfect alone. Surveys can be sparse and mood-driven. Operational logic can miss frustration that did not lead to another contact. The strongest programs compare both. When customer-reported FCR is much lower than operational FCR, that usually means the team is closing cases too optimistically.
FCR's relationship to CSAT and AHT
FCR often has a direct relationship with CSAT. Customers usually rate an interaction more positively when it ends the problem. FCR can also have a tension with AHT. Calls that fully solve the issue may take a bit longer because the agent verifies the outcome, checks understanding, and gives better next steps.
That is why a falling AHT can sometimes mask a worsening FCR trend. If leaders push for faster calls without checking repeat contacts, they may cut visible labor today and create more labor tomorrow.
Collections FCR: promise kept vs. promise broken
Collections teams need a more nuanced view of FCR because a call can sound resolved at the end and still fail later. If the customer agrees to a payment but does not keep it, should the original call count as first-contact resolution? Many teams say no, because the underlying account problem was not actually resolved.
That makes collections FCR partly a promise-quality metric. Strong agents set clear payment commitments, confirm dates and amounts, and explain consequences and next steps. Weak agents may end the call faster but create more broken promises, repeat outreach, and rework.
How call scoring predicts repeat-contact risk
Conversation analytics can flag the patterns that often create failed FCR: vague close language, missing summary, low customer confirmation, long unresolved holds, and escalations that never reach the right owner. Those signals matter because they show risk before the repeat contact happens.
That is especially useful in low-survey environments. Instead of waiting a week to discover FCR drift, managers can use call-level patterns to see where resolution quality is getting weaker now.
FAQ
What is a good FCR score?
Many teams land around 70% to 75%. Good performance is usually 75% to 85%, and top-tier programs often exceed 85% in steady-state queues.
Why is FCR hard to measure?
Because the score depends heavily on the repeat-contact window and on how the team identifies whether a second contact was about the same issue.
Should FCR be measured by customers or operations?
Both. Customer-reported FCR captures perception, while operational FCR captures behavior. Together they give a more honest picture.
How does FCR relate to AHT and CSAT?
Higher FCR usually supports higher satisfaction and may require slightly longer calls. Very aggressive AHT targets often work against FCR.
What does FCR mean in collections?
It often comes down to whether the customer left with a clear, kept payment plan rather than an easy verbal agreement that breaks later.
Benchmark Your FCR
Measure repeat-contact risk, compare your resolution rate against peers, and see which conversations are closing without actually solving the issue.
Email: amanda@altorlab.xyz
Related metrics: CSAT Score, Deflection Rate, Escalation Path, Agent Occupancy Rate, Average Handle Time