First Contact Resolution · Resolution on first contact
What is First Contact Resolution?
First Contact Resolution is the percentage of questions finished in one go. Of all customer service numbers, this is the one that predicts the most work.
In short
First Contact Resolution, abbreviated FCR, is the percentage of customer questions fully handled at first contact, without the customer having to come back to it. A question only counts as resolved on first contact when no new message, call or reopened ticket about the same topic follows.
Calculation
FCR = (questions without follow-up contact within 7 days / total questions) x 100
The seven-day window is a choice you have to fix. Take 24 hours and you miss follow-up contact on day three, scoring higher than is justified. Seven days catches most returners and stays practical to measure.
Why this number predicts your workload
Every question not finished in one go comes back. That second contact costs attention again, often from a different colleague who first has to read up. So an FCR ten points lower doesn't mean ten percent dissatisfied customers but a substantially higher workload at unchanged demand.
That makes FCR more useful than response time for planning capacity. Speed determines how long someone waits; resolution on first contact determines how many conversations you have at all.
Why a question isn't finished in one go
In practice, returning conversations usually come from one of three directions. The agent lacked information that lived in another system. The answer was correct but incomplete, so the customer had a follow-up question. Or the answer required an action nobody carried out afterwards.
Those three call for different measures: bringing data to the conversation, completing answer templates, and recording the action as a task rather than an intention.
Measure FCR or repeat contact?
| FCR | Repeat contact | |
|---|---|---|
| What you count | Conversations closed in one go | Customers who came back about the same thing |
| Gameable by closing | Yes, closing faster raises the number | No, the customer decides whether they return |
| Points at | How the conversation was handled | The cause behind the question |
Measure both and believe the second when they diverge. A rising FCR with rising repeat contact means conversations are being closed faster, not handled better.
Where it goes wrong
Only measuring within one channel
A customer who doesn't get an answer by email and then calls counts in many systems as two separate contacts, both resolved on first contact. Your FCR then looks excellent while the same question cost work twice. So link contacts to the customer, not to the channel.
Closing tickets quickly to hit the number
Close a ticket right after your answer and a customer reply arrives as a new ticket, not counting as a reopen. The number rises and nothing changes. So measure on customer and topic, not on ticket status.
What to do this week
Take last month's conversations where the same customer got back in touch within seven days about the same topic. Sort them by topic. The top two categories are where your answer template or your integration falls short, and that's more concrete than steering on the percentage.
What this looks like in a system
In Cuego conversations hang on the customer card rather than the channel, so an email followed by a call is visible as the same topic. When composing an answer the order, the delivery status and earlier conversations are already there, so the answer can be complete in one go. An action following from a conversation is recorded as a task with an owner and a date.
CRM & customer viewRelated terms
Deflection
Deflection is the share of questions that never reached an agent. It's the easiest number to overstate and the most useful to measure honestly.
Read onKnowledge base
A knowledge base is the recorded version of what your team knows. Without an owner and a rhythm it's partly wrong within six months.
Read onEscalation
Escalating is handing a conversation to someone who's allowed more or knows more. The rules for it are usually written nowhere, and you notice that only in the conversations that go wrong.
Read on