First call resolution tells you how often customers get a complete answer the first time they reach your team. First call resolution and first contact resolution are two names for the same metric: “call” comes from phone support, “contact” includes chat, email and messaging.
How do you calculate first call resolution?
To calculate first call resolution, divide the issues resolved in the first contact by all eligible contacts and multiply by 100.
First call resolution rate
Dividing by eligible contacts gives net FCR; dividing by all contacts gives gross FCR, which is always lower.
Example: In one month your team handles 400 contacts. 25 are wrong numbers or dropped calls, so 375 are eligible. 260 of them are solved without the customer coming back about the same issue: 260 ÷ 375 × 100 = 69%.
Benchmark: 71% is the call center industry average; 70–79% counts as good and 80% or more as world class. Source: SQM Group, FCR benchmark, updated August 2026
There are two common ways to decide whether a contact was resolved:
- Ask the customer. A short question after the conversation, such as “Was your issue solved?”, gives the customer’s view, much like a customer satisfaction survey. SQM Group measures FCR this way.
- Look for repeat contacts. If the same customer comes back about the same issue within a set window, for example seven days, the first contact did not resolve it. There is no standard window: choose one and keep it, so the trend means something.
Leave out contacts nobody could resolve: wrong numbers, spam, calls that drop before anyone answers.
What is a good first call resolution rate?
A good first call resolution rate is 70–79%. SQM Group’s call center industry average is 71%, and 80% or more counts as world class, based on the more than 500 call centers SQM benchmarks each year. Averages by industry:
| Industry | Average FCR |
|---|---|
| Retail | 77% |
| Insurance | 75% |
| Technical support | 64% |
| Telecommunications | 56% |
Source: SQM Group, updated August 2026. IT service desks average 70.2% net FCR across channels and 62.3% for chat, according to MetricNet’s 2023 benchmarks (MetricNet, Summary of 2023 IT Service and Support Benchmarks). Compare your rate with teams that solve similar problems, and watch your own trend more than any single number.
Why does first call resolution matter?
First call resolution matters because every issue not solved in the first contact comes back as a second one: the customer loses time and your team handles the same problem twice. According to SQM Group, every 1% improvement in first call resolution improves customer satisfaction by 1% and reduces operating costs by 1%.
- Every repeat contact is the same work twice. The customer explains the problem again and an agent reads the history again, so a low rate fills your queue with issues you have already seen.
- Speed and resolution pull against each other. Pushing agents to keep calls short can lower first call resolution; watch it together with average handle time.
How do you measure FCR in a small support team?
A small team can measure first call resolution without special software: agree what counts as one issue, mark repeat contacts, review them weekly and fix the causes.
-
Decide what counts as one issue
Agree on the repeat window and on which contacts you leave out, and write it down so everyone counts the same way.
-
Mark repeat contacts
When a customer comes back about the same problem, link it to the earlier conversation or tag it, so repeats are easy to count at the end of the week.
-
Review the repeats every week
Read a handful of repeat contacts and note why the first answer did not solve the issue: missing information, a wrong department, an agent who was not allowed to fix it.
Fix the cause, not the agent
Add the missing answer to your knowledge base, change where those requests are routed, or let agents solve that kind of problem without approval.
What are common first call resolution mistakes?
The most common mistake is mixing gross and net FCR, which makes the rate look better or worse than it is.
- Mixing gross and net FCR. Gross FCR divides first-contact resolutions by all contacts; net FCR first removes contacts nobody could resolve, so it is always higher. Say which one you report.
- Counting closed as resolved. A ticket an agent closed is not resolved if the customer writes again about the same problem.
- Leaving transfers out. Contacts passed to another team are exactly the routing problems FCR should show.
- Trusting agents’ own counts. An agent may mark an issue solved that the customer still has; compare agent reports with survey answers or repeat contacts.
- Comparing channels. Email and complex tickets often need a second reply, so compare phone with phone and email with email.
- Changing the rules midway. A different repeat window or new exclusions make this month incomparable with the last.
How is first call resolution different from resolution rate?
Resolution rate counts every issue solved eventually, however many contacts it takes; first call resolution counts only the issues solved in the first contact, so it is always the lower number. The related metrics answer different questions:
- First call resolution: issues solved in the first contact.
- Resolution rate: issues solved eventually, however many contacts they take. It is always higher than first call resolution.
- Repeat contact rate: contacts about an issue the customer has raised before, the flip side of first call resolution.
- Customer satisfaction (CSAT): how satisfied customers say they are after the contact, whether or not the issue was solved the first time.
How can a small support team improve first call resolution?
A small team improves first call resolution mostly by sending each request to the right person and giving that person what they need to finish it:
- Route each request to the right person first. A customer sent to the wrong department has to explain everything again.
- Show agents the customer’s history. Earlier conversations explain what was already tried.
- Keep answers in one place. A knowledge base and saved replies help agents give the same complete answer every time.
- Let agents finish the job. Agents who may issue a small refund or reset an account do not need to pass the customer on.
- Call back instead of transferring. When a specialist is needed, a promised callback from the right person beats a cold transfer.
First call resolution in LiveAgent
