First Call Resolution (FCR): a contact center metric that measures the percentage of customer issues resolved during the very first contact, with no follow-up call, email, chat, or escalation required to close the matter. It is one of the most commonly written SLA metrics in outsourcing contracts, and one of the most commonly gamed.
On paper FCR looks simple. In a vendor relationship it is a pressure point. Agents get coached to hit a FCR target, coached separately to hit an Average Handle Time (AHT) target, and those two goals pull in opposite directions. I would treat FCR less as a customer satisfaction proxy and more as a window into how disciplined a vendor’s floor management actually is.
What does FCR mean in a call center?
FCR in a call center means the customer’s issue was fully closed on the first interaction, with no need to call back, no ticket reopened, and no transfer to another queue or tier. It is tracked per agent, per team, and per campaign, and it usually feeds directly into vendor scorecards and, in many contracts, into pricing penalties or bonuses.
The tricky part is definition. “Resolved” sounds objective, but vendors and buyers do not always agree on what counts. Some contact centers define FCR using a callback window of 24 to 72 hours: if the customer does not call back about the same issue within that window, the ticket counts as first-call-resolved, even if the customer just gave up or escalated somewhere else. That window is a loophole I would ask about explicitly during vendor selection, because a generous window can make FCR numbers look better than the actual customer experience.
How is FCR calculated, and what’s a good FCR rate?
FCR is calculated as (issues resolved on first contact / total issues handled) x 100, tracked over a call, chat, or ticket volume for a set period, usually daily or monthly. A realistic benchmark range for most support operations is 70% to 75%, with strong operations pushing into the high 70s or low 80s depending on industry and issue complexity; treat any number above that as worth a closer audit, not an automatic win.
Here is the catch: a high FCR rate can mean excellent training, or it can mean agents are closing tickets prematurely to hit a number. I have seen both. The way to tell the difference is to look at repeat contact rate over 7 and 30 days, not just the headline FCR percentage. If FCR is reported at 82% but repeat contacts within a week sit at 25%, someone is closing tickets that were never actually solved.
| Reported FCR | 7-day repeat contact rate | Likely explanation |
|---|---|---|
| 78% | 6-8% | Genuine resolution, healthy process |
| 85% | 20%+ | Tickets closed early to hit target |
| 65% | 5% | Complex issue mix, not a red flag by itself |
| 90%+ | Not tracked | Ask why repeat contact isn’t measured at all |
I would never accept a FCR number from a vendor without also asking for the repeat contact rate in the same report. If a vendor cannot produce it, that is a reporting maturity gap, not a small omission.
Why does FCR conflict with AHT in outsourced contact centers?
FCR and AHT compete because resolving an issue fully often takes longer, while AHT targets reward agents for getting off the call fast. A vendor floor that is pushed hard on AHT will naturally see FCR erode, because agents rush closure, defer complex issues, or quietly transfer them instead of solving them, even when the transfer isn’t logged that way.
This is the operational reality that generic glossary definitions skip. Reddit threads from call center agents on this exact tension are common, and the complaint is consistent: agents are told to keep calls short and to resolve everything on the first contact, and those two instructions cannot both be optimized at once past a certain point. A vendor who claims strong performance on both metrics simultaneously, without tradeoffs, is usually reporting selectively.
As a buyer, I would ask for the AHT and FCR trend lines side by side, not as separate slides. If FCR climbed the same month AHT dropped sharply, that is not a coincidence worth ignoring. It is worth a call with the vendor’s ops manager, not the account manager, about how QA reviewed those closures.
How do you actually improve first call resolution with a vendor?
FCR improves through better agent knowledge access, tighter escalation paths, and QA that specifically audits closed tickets for premature closure, not through pressuring agents to close faster. The fix starts before the contract: document the resolution paths for your top 20 issue types clearly enough that a new agent can follow them, because you cannot outsource a process that isn’t written down yet.
Once live, the levers that actually move FCR are: agent access to the right knowledge base and account systems at first contact (not after escalation), a QA sample that specifically reviews closed-not-reopened tickets for false closures, and management structure where team leads can unblock an agent stuck on a hard case without forcing a transfer. A vendor with a mature QA program will typically review a meaningful percentage of resolved contacts specifically for this failure mode, not just for tone and compliance.
If you are comparing providers for Call Center & Customer Support, ask each one how they define FCR, what their callback window is, and how QA catches false closures. Compare vendors running call center outsourcing programs by process fit, not just their quoted FCR number. Location matters too: teams built for call center outsourcing united states delivery often run tighter QA on regulated issue types, while call center outsourcing manila operations are frequently optimized for high-volume support where FCR discipline varies more by account than by country.
What is the 80/20 rule in a call center?
The 80/20 rule in a call center most often refers to a service level target, meaning 80% of calls answered within 20 seconds, and it is a separate metric from FCR that measures speed of answer, not quality of resolution. Buyers sometimes conflate the two because both show up on the same SLA dashboard, but a vendor can hit 80/20 on speed while quietly under-delivering on FCR, or the reverse. Read both metrics on the same scorecard, not in isolation, before judging vendor performance.
If you are evaluating outsourced support or telemarketing services providers and want scorecards compared side by side before you commit, start at Get outsourcing quotes.