Revolutionize your call operation with Retell
First contact resolution (FCR) is the share of issues solved on the first contact. See the formula, a worked example, how to measure it, and what cuts it.
First contact resolution (FCR) is the percentage of customer issues resolved during the customer's first contact, so the customer never has to call, chat, or email again about the same problem. Many contact centers call it first call resolution, because most of the contacts they measure are phone calls. The two terms mean the same thing.
Divide the issues resolved on first contact by the unique issues customers raised, then multiply by 100.
FCR = (Issues resolved on first contact ÷ Unique issues raised) × 100
"Unique" means each issue counts once, not each call. "Resolved" needs a test, covered below.
| Input | Count |
|---|---|
| Inbound calls in March | 12,000 |
| Calls that were callbacks about an issue already raised | 2,000 |
| Unique issues raised | 10,000 |
| Issues that needed at least one more contact within 7 days | 1,600 |
| Issues resolved on first contact | 8,400 |
FCR = 8,400 ÷ 10,000 × 100 = 84%.
The 1,600 unresolved issues produced 2,000 callbacks because some customers called more than twice. Divide by total calls instead (8,400 ÷ 12,000) and you get 70%: a 14-point gap from the denominator alone. Write your definition down before comparing FCR across teams or vendors.
Teams use three methods, and careful ones combine two.
| Method | How it works | Strength | Trade-off |
|---|---|---|---|
| Post-contact survey | Ask the customer whether the issue was resolved and whether it took one contact | Captures the customer's view, which is what FCR is meant to reflect | Only covers people who answer, and results arrive late |
| Repeat-contact window | Check the CRM or call records for another contact from the same customer about the same issue within a set window, such as 7 days | Covers every contact and can be automated | Misses callers who switch numbers or channels; the window length and the "same issue" rule both move the result |
| Agent disposition | The agent marks the contact resolved or not at wrap-up | Instant and costs nothing | Agents grade their own work and cannot see a future callback, so it tends to read high |
Set the window per call reason (short for a status question, longer for an issue that needs investigation) and keep it fixed across periods.
SQM Group, which benchmarks more than 500 North American call centers using post-call surveys, rates 70% to 79% as good and 80% or higher as world-class. Those figures assume survey-based measurement, so a number from a repeat-contact window or agent dispositions is not directly comparable. Rates also vary by industry and call type. For the breakdown, see our first call resolution benchmarks.
Most unresolved contacts trace to causes the person on the call cannot fix in the moment:
Tag each unresolved contact with a reason and review by call type; call analytics makes this workable at volume.
A voice agent raises FCR when it can finish the job on the call. Three Retell capabilities map to the causes above.
issue_resolved and a selector for call reason, and you get a resolution flag per call that you can join with repeat contacts in your own records.Make two reporting decisions before launch. Decide whether a call the agent warm-transfers and a person resolves counts as FCR, and report AI-only resolution separately either way. And keep FCR apart from call containment, the share of calls finished without a person: a contained call that leads to a callback is not resolved.
If transfers, after-hours callbacks, or missing system access are holding your FCR back, see how Retell supports AI call centers and measure resolution on your own call reasons before you commit.