First-call resolution (FCR) is the share of customer issues that are solved during the first call, with no callback, transfer chain or follow-up email. Customers love it because their problem is simply gone. Teams love it because every repeat call is work they don’t have to do twice.
Why first-call resolution matters
- Customers remember effort. Calling twice about the same problem is one of the most frustrating support experiences.
- Repeat calls fill your queue. Every unresolved call comes back, making wait times longer for everyone else.
- It shows where to improve. Calls that need a second contact point to gaps in routing, knowledge or authority.
How to measure it
There is no single perfect formula. Pick one definition and use it consistently:
- Agent-reported: the agent marks whether the issue was solved on the call. Simple, but optimistic.
- Repeat-contact based: a call counts as resolved if the same customer doesn’t call again about it within a set window, for example seven days.
- Customer-reported: a short question after the call, “Was your issue solved today?”.
Whatever you choose, track the trend over time rather than chasing one number.
1. Route calls to the right person the first time
Many unresolved calls start in the wrong place. A caller with a billing question who reaches a technical agent will need a transfer or a callback.
- Separate the most common reasons for calling with a short menu or different numbers.
- Send complex topics to the people who can actually solve them.
- Review where calls are transferred most often and fix the route. Our call routing guide explains the options.
2. Give agents the full picture
An agent who can see the caller’s history solves problems faster.
- Keep contacts with notes so the next agent knows what was promised last time.
- Check the call history before calling a customer back.
- Use call recordings and transcripts to review complex cases, and to train new people.
3. Let agents actually fix things
Many second calls happen because the first agent wasn’t allowed to solve the problem. Give your team clear authority for the common cases, such as small refunds, rescheduling or replacing an order, and a fast path to a supervisor for the rest.
4. Build and use a knowledge base
Write down the answers to your most common questions, and keep them current. A shared help center helps agents answer consistently, and lets customers solve simple issues without calling at all.
5. Close the call properly
- Summarise what was done and what happens next.
- Ask: “Is there anything else I can help you with today?”
- If something must happen later, say who will do it and when, and write it in the contact’s notes.
Post-call time, a short buffer after each call, gives agents a moment to finish notes before the next call rings.
6. Learn from the calls that weren’t resolved
Once a month, take a sample of repeat calls and ask why the first call didn’t solve the problem. The answers usually fall into a few groups: wrong routing, missing information, missing authority or a product issue. Fix the biggest group first.
A quick checklist
- Pick one FCR definition and track it monthly.
- Route the top reasons for calling to the right people.
- Keep contact notes and check call history before calling back.
- Give agents clear authority for common fixes.
- Close every call with a summary and next steps.
- Review a sample of repeat calls every month.
Shorter queues help too: see how to reduce customer wait times on the phone.
