Resolution Economics | | 8 min read

Why First Call Resolution
Is a Misleading KPI

FCR measures whether a contact was resolved on the first attempt. It says nothing about cost. Here's why Cost Per Resolution is the metric that matters.


The FCR Illusion

First Call Resolution has been the gold standard of contact center performance for two decades. It shouldn’t be.

FCR measures whether a contact was resolved on the first attempt — but it says nothing about the cost of resolution, and it structurally obscures the most expensive failures in your operation.

When a contact center reports 70% FCR, leadership hears: “70% of our customer issues are handled efficiently.” That interpretation is wrong in two ways.

First, FCR is typically measured at the contact level, not the issue level. If a customer calls about a billing dispute, gets transferred to a specialist, and the specialist resolves it, that interaction may be coded as “resolved on first contact” because the specialist closed the ticket. The transfer, the duplicate handling, and the wait time vanish from the metric.

Second, FCR treats all resolutions as equal. A password reset that takes 90 seconds and a complex claims dispute that takes 38 minutes across two departments both count as one resolved contact. The operational cost difference between them is invisible.

What FCR Misses

The contacts that fail first-call resolution do not simply cost twice as much. They cost three to five times as much. Here is what happens downstream of an unresolved first contact:

Repeat contacts. According to SQM Group, the average contact center with 1,000 agents generates approximately 540,000 repeat calls per year, costing $4.8 million annually. Every 1% improvement in FCR saves approximately $286,000 per year. These are significant numbers — but FCR itself does not capture them. FCR tells you the rate. It does not tell you the cost.

Transfers and escalations. Each transfer adds labor cost from a second (or third) agent, increases handle time, and degrades customer experience. In many organizations, transferred contacts are still coded as “resolved” by the receiving agent — meaning FCR never registers the failure.

Rework. When a contact is improperly resolved — a claim processed incorrectly, a policy change entered wrong, an eligibility determination made with incomplete data — the rework cost is absorbed by back-office operations. It never touches the contact center dashboard. FCR cannot see it.

Channel switching. A customer who calls, then emails, then chats generates three contacts across three channels. Each channel may report its own FCR independently. The customer’s issue was resolved once. The cost was incurred three times.

Introducing Cost Per Resolution

If FCR measures the rate of first-contact success, Cost Per Resolution (CPR) measures the total economic cost of actually resolving a customer issue — regardless of how many contacts, transfers, channels, or rework cycles it required.

CPR = (Total Labor + Overhead + Technology) / Verified Resolved Outcomes

The denominator is critical. “Verified Resolved Outcomes” means unique customer issues confirmed as resolved — not contacts handled, not tickets closed, not calls answered. This is the number most organizations do not track, and it is the reason their cost reporting is structurally inaccurate.

The $42 Gap

Consider a mid-size contact center reporting a cost per contact of $12. That number is derived by dividing total operating cost by total contact volume. It is arithmetically correct and operationally useless.

When you adjust the denominator to count verified resolutions instead of raw contacts, the number changes. If 26% of contacts are repeats, and another 8-12% involve transfers or rework that generate downstream cost, the effective resolution count drops significantly. In a typical operation, that $12 cost per contact becomes $54 cost per resolution.

The $42 gap between those two numbers is not a rounding error. It is hidden margin waste.

What to Do About It

Operations leaders who suspect their FCR metric is masking resolution economics can take three concrete steps:

  1. Track issue-level resolution, not contact-level resolution. Assign a unique identifier to each customer issue and trace every contact, transfer, and rework event associated with it.
  2. Measure cost per resolution for your top five contact types. Calculate CPR for each and compare the results to your reported cost per contact. The gap will tell you where to focus.
  3. Separate AI-deflected contacts from human-handled contacts. If automation is absorbing low-complexity contacts, your human-handled cost per resolution is rising — even if blended averages look stable.

The Metric You Trust Most May Be the One Lying the Loudest

FCR is not a bad metric. It measures what it measures. The problem is that organizations use it as a proxy for cost efficiency, and it is not built to carry that weight. Cost Per Resolution closes the gap between what dashboards report and what operations actually cost.

Your CCaaS vendor reports your CPR. We verify it. They cannot do both.


Brandon Burdin is the founder of MarginSignal OS, a forensic margin diagnostic for contact center operations. 15 years in contact center operations. 50 to 2,000+ seats. Insurance, healthcare, BPO, ITSM, field service.

Ready to see what your operations are really costing?

MarginSignal OS runs a forensic diagnostic that reveals the gap between what you report and what you actually spend. Runtime governance meets operational intelligence.

Request a Diagnostic