First call resolution predicts satisfaction and cost better than almost any other measure, which is exactly why it gets gamed. Here is how to define it so the number means something.
Why FCR is worth the argument
First call resolution is the share of contacts fully resolved without the customer having to come back. It correlates with satisfaction more reliably than speed does, and it is the only major contact center metric where improving it reduces cost and improves experience at the same time. Every repeat contact is a second interaction you paid for and a customer who is now more annoyed than they were.
Which is precisely why the definition matters. FCR is the easiest metric on the board to inflate, and an inflated FCR actively hides the problem it exists to reveal.
The three ways the number gets gamed
- Counting the call, not the issue. If a customer calls three times about one problem and each call is logged as resolved, FCR looks excellent and the customer has called three times.
- Ignoring channel switching. A caller who is told to email, or a chat that ends "please call us", is a resolved contact by most systems and an unresolved issue by any honest reading.
- A too-short window. Measured over twenty-four hours, FCR misses every customer who discovers on Thursday that Monday's fix did not hold.
A definition that survives contact with reality
Resolve at the level of the issue, across all channels, over a window long enough to catch a failed fix — seven days is the common choice and fourteen is defensible for technical products. Under that definition FCR usually drops sharply the first time it is measured properly, and that drop is the most useful thing the metric will ever tell you.
Pair it with repeat contact rate, which is the same information stated as a problem rather than an achievement, and is harder to argue with in a management meeting.
What actually moves it
Agent authority is usually the largest single lever and the least often pulled. An agent who has to transfer or seek approval for a routine remedy cannot resolve on first contact no matter how well trained they are. Widening the band of decisions an agent can make without asking moves FCR faster than any amount of coaching.
After that: knowledge that is findable during a live call rather than comprehensive and buried; routing that gets the contact to someone equipped the first time; and closing the loop on root causes, because a large share of repeat contacts are the same handful of upstream problems generating avoidable calls forever.
The trade-off to watch
FCR and average handle time pull against each other, and a center targeting both aggressively will get neither. Resolving properly takes longer on the call and costs less overall. If you are going to prioritize one, prioritize resolution and let handle time land where it lands — then watch total contacts per customer, which is the number that actually reflects cost.
See how quality and resolution are monitored, or read about the reporting layer behind these metrics.
Frequently asked questions
What is a good FCR rate?
Benchmarks float around the seventy to seventy-five per cent mark for many voice programs, but the number is close to meaningless without knowing the definition behind it — a center measuring per-call over twenty-four hours will beat a center measuring per-issue over seven days while delivering a worse experience. Treat published benchmarks as unreliable for comparison and use your own trend under a fixed definition instead. The direction matters more than the level.
How do we measure it without asking the customer?
Repeat contact analysis on your own data, which most teams can do without new tooling. Match contacts by customer identifier over your chosen window and count how many had more than one contact about the same issue. It requires reasonable disposition coding to attribute contacts to issues, and improving that coding is usually worthwhile in its own right. Customer-confirmed FCR from a post-contact survey is more accurate and much lower volume, so most centers run both.
Does FCR apply to chat and email?
The concept does, though the name stops making sense — most centers rename it first contact resolution for that reason. It matters most across channels rather than within them: the failure mode worth catching is the contact that appears resolved in chat and reappears as a phone call the next day. If your channels are measured in separate systems that never reconcile, your FCR is measuring each channel's ability to end conversations rather than to solve problems.
Should agents be paid on FCR?
Be careful. FCR is heavily influenced by things an individual agent does not control — routing quality, system access, the authority they have been granted, and the upstream defects generating the calls. Incentivising it individually reliably produces gaming: contacts marked resolved that were not, and customers discouraged from calling back. It works better as a team-level diagnostic that drives changes to authority and knowledge than as a personal target.
Running the operation
Keep reading
The rest of this cluster, for the question you are actually working through.
- CSAT, NPS, CES and the Metrics Worth Putting on a Dashboard
- How to Reduce Call Abandonment Without Just Adding Agents
- Call Center Attrition: What It Really Costs and What Reduces It
- Seasonal Support Staffing: Covering a Peak Without Carrying It All Year
- Writing a Call Center SLA That Means Something
- PCI Compliance in a Call Center: Where Card Data Actually Leaks