Here is how I improve first contact resolution. First contact resolution (FCR) is the share of customer issues fully solved in the first interaction, with no follow-up needed: FCR = issues resolved on first contact ÷ total issues resolved × 100. To improve first contact resolution, give the first person who touches a ticket what they need to finish it: the right details at intake, the right route, the right permissions and a knowledge base they trust.
The free FCR calculator works out your rate and shows how exclusions change it. This is Part 1 of The Support Operations Playbook, an eight-part series on running a B2B support team well, from first contact resolution to capacity planning. Below is what one point of FCR is worth, the seven levers I use and the 90-day plan I would run again.
How do you measure first contact resolution?
FCR (%) = Issues resolved on first contact ÷ Total issues resolved × 100
Resolved on first contact = solved in one interaction, and the customer does not
reopen it or open a related ticket within the window
Total issues resolved = all solved issues in the period, minus spam,
duplicates and "thanks!" replies
Reopen window = the days you wait before counting a ticket as solved
first time (I use 7)
The arithmetic is easy. The definitions are where teams disagree, so write them down before anyone sees a number. Report FCR by channel as well as overall. Chat and phone can solve an issue in one session, while email often needs one clarifying question.
How much is one point of FCR worth?
Every ticket not solved the first time creates at least one more contact. Say your team resolves 5,000 tickets a month.
| Today | Target | |
|---|---|---|
| Resolved on first contact | 3,400 | 3,750 |
| FCR | 68% | 75% |
| Tickets needing follow-up | 1,600 | 1,250 |
That is 350 fewer follow-ups a month. At about $18 per follow-up, it saves $6,300 a month, or $75,600 a year. Work out your own cost with the cost per ticket formula, then enter your counts in the FCR calculator to see your starting point.
What a 7-point FCR gain is worth
FCR rate = tickets resolved on first contact ÷ total resolved tickets × 100. Here 3,400 ÷ 5,000 = 68% today and 3,750 ÷ 5,000 = 75% at target, so 1,600 − 1,250 = 350 fewer follow-ups, and 350 × $18 = $6,300 a month.
The cost is only half of it. Customers hate writing twice. In the research behind "Stop Trying to Delight Your Customers" (Harvard Business Review, 2010), having to contact the company repeatedly was the single biggest driver of customer effort.
Free download
Get the First contact resolution spreadsheet
The First contact resolution calculator as an Excel file with the formulas set up, ready for your own numbers. Works in Google Sheets too.
The download button appears here right away; nothing is sent to your inbox. Your email also joins Clarivoxx Insights (a weekly article and a monthly newsletter). Unsubscribe in one click. Privacy
What FCR target should you set?
SQM Group, which benchmarks call centers, puts the average phone FCR at about 71%, with tech support lower at around 64% and 80% treated as world class. B2B SaaS tickets are often harder than consumer calls, so I do not chase those numbers directly. My rule: measure your own baseline by category, then aim for a few points a quarter. A jump of ten points in a month usually means someone changed the definition.
How do you improve first contact resolution?
Most gains come from removing what stops the first responder from finishing the job.
- Ask for the right details at intake. Make the form require account ID, product area and steps already tried.
- Route to the right skill. Billing to agents with billing rights, integration errors to technical agents. A misrouted ticket almost always comes back.
- Keep a short internal knowledge base. The exact fix, known workarounds and when to escalate. Review the most viewed articles every month.
- Widen permissions. If an agent needs a supervisor to approve a $40 credit, the customer waits and writes again. Set written limits and let agents act within them.
- Pull experts in instead of handing off. The first agent keeps the ticket and asks a specialist in a shared channel. Track your escalation rate next to FCR.
- Answer the next question too. The HBR authors call this anticipating the downstream issue. If a refund is approved, say when the money arrives and what the statement will show.
- Send root causes to product. Some tickets cannot be solved first time because the product is broken.
Which ticket categories drag FCR down?
Your overall number hides the story. Split 90 days of resolved tickets by category and a few weak spots usually stand out.
Two categories drag the average down
Integrations and bug reports produce 872 of 1,600 follow-ups from 30% of volume.
In this example, password questions are almost always solved first time. Integrations and bug reports create 872 of the 1,600 follow-ups from about 30% of the volume. That is where routing and product feedback pay off most.
What I've seen in practice
When I worked with hotel partners, refund requests were our worst category. The form did not ask for the booking reference, so the first reply was almost always "can you send the booking number?" We made that field required. Within two weeks that back-and-forth had mostly disappeared.
On another team, a third of our unresolved partner tickets were really one billing question that bounced between support and finance. Nobody owned it, so every partner wrote twice. Once finance gave us a short list of answers we could send ourselves, that category dropped out of the follow-up report.
The mistake I see most often is judging agents on FCR alone. Some will close tickets too early, and the number rises while customers get worse answers. Pair FCR with reopen rate and CSAT, measured the same way each month with the CSAT calculator.
What does a 90-day FCR plan look like?
- Days 1 to 30: agree the reopen window and exclusions, measure FCR by channel and category, fix the intake form for the two weakest categories.
- Days 31 to 60: set up skill-based routing, publish permission limits, refresh the 20 knowledge base articles linked to the most repeat contacts.
- Days 61 to 90: add "answered the next question" to QA, start a monthly root-cause review with product, set the next target a few points higher.
Who owns each FCR lever
The customer experience metrics guide shows how FCR fits with CSAT and effort.
The FCR dashboard I review every month
I keep FCR and its guardrail in one small table and update it on the first working day of each month. Here it is with the numbers from this example.
| Metric | Target | This month | Last month | Change |
|---|---|---|---|---|
| FCR, all channels | 75% | 68% | 66% | +2 pts |
| Follow-up contacts | 1,250 | 1,600 | 1,632 | −32 |
| Follow-up cost | $22,500 | $28,800 | $29,376 | −$576 |
| FCR, integrations and API | 55% | 45% | 42% | +3 pts |
| FCR, bug reports | 45% | 38% | 39% | −1 pt |
| Reopen rate (7 days) | 5% or less | 6% | 6% | 0 pts |
Read the category rows before the headline. Overall FCR went up, but bug reports slipped, so that is the first item for the monthly root-cause review with product.
What to do this week
Pull last month's resolved tickets, split FCR by category and read ten tickets from the weakest one. You will usually spot the missing field, the wrong route or the missing permission within an hour.
Frequently asked questions
How long does it take to improve FCR?
Intake and routing fixes usually show within a month. Knowledge base and permission changes take two to three months to move the overall number, because they work ticket by ticket.
Does improving FCR make tickets take longer?
Sometimes a little. Answering the next question adds a minute or two to a reply, but it removes a whole follow-up contact, so the total time per issue goes down.
Which FCR lever should I start with?
Intake. A required field on the contact form is cheap, quick and fixes the most common reason for a second reply: missing details.
Can FCR be too high?
Yes, if it comes from closing tickets early. When FCR rises and reopen rate rises with it, the gain is not real.
Who should own FCR?
The support manager owns the number. Product owns the root causes that make some tickets impossible to solve first time.
Sources
- First Call Resolution Benchmark, SQM Group
- Stop Trying to Delight Your Customers, Harvard Business Review
Run your own numbers
Free, no sign-up, with the formula and an Excel version.
Read next
How to Cut a Ticket Backlog Without Hiring
How to reduce ticket backlog without hiring: measure the excess, find where it sits and use six levers to make the queue shrink every day.
Read the article
Go further with the ebook
The Professional Customer Support Playbook
Better replies, fewer escalations, a clear path from agent to leader.
$19.99 · 103 pages · View the book