First Contact Resolution: What It Is, How to Measure It and How to Raise It
Ask customers what good support feels like and you'll hear the same thing in different words: "they sorted it straight away." First contact resolution (FCR) measures exactly that, the share of problems solved in a single conversation, with no follow-up needed. It's one of the few support metrics that customers feel directly, and it tends to lift satisfaction and lower workload at the same time.
This guide explains what FCR is, how to measure it, how to judge your own number, and practical ways to raise it.
What is first contact resolution?
First contact resolution is the percentage of customer issues resolved in the first interaction, without the customer having to contact you again about the same problem.
In call centres it's often called first call resolution. For teams working across chat, email and messaging apps, "contact" means the first conversation, whichever channel it happens on.
The TNT Chat ticket list with status, priority, SLA and assignee for every ticket.
Why it matters
- Customers are happier. Every extra contact adds waiting, repeating and doubt.
- Your team does less work. A problem solved once costs less than a problem handled three times.
- It reveals what's really broken. Low FCR points to missing knowledge, missing access or confusing products.
It also balances speed metrics. A team can hit a great first response time with quick replies that don't solve anything. FCR catches that.
How to calculate FCR
The basic formula:
FCR = (issues resolved in the first contact ÷ total issues) × 100
For example, if 400 conversations were closed this month and 300 needed no follow-up, your FCR is 75%.
The hard part is deciding what "resolved in the first contact" means. Pick one definition and stick to it:
- Ticket-based: the ticket was solved with one agent reply and wasn't reopened within a set period, such as seven days.
- Customer-based: the same customer didn't contact you about the same topic within seven days, on any channel.
- Survey-based: ask the customer, "Was your problem solved?" at the end of the conversation.
Ticket-based is the easiest to measure in a help desk. Survey-based is the closest to how customers feel. Many teams use one as their main number and glance at the other.
What to leave out
Exclude conversations that can't be resolved in one contact by nature, such as a return that requires the customer to send something back, and spam or messages that need no answer. Count them separately so they don't distort the number.
What's a good FCR?
It depends on what you support. A shop answering delivery questions can solve most in one go. A software company handling technical problems will have more back-and-forth. Rather than chasing someone else's benchmark, measure your own baseline for a month and work on raising it. Watch the trend, and compare by channel and by topic.
Why problems aren't solved first time
When you look at conversations that needed a second contact, the causes are usually one of these:
- The agent didn't have the answer and had to check with someone.
- The agent didn't have access to do what was needed.
- The question was misunderstood, so the answer missed.
- Information was missing from the customer: an order number, a screenshot, an account email.
- The fix depended on another team or a bug fix.
- The answer was right but unclear, so the customer came back to ask what it meant.
Tag a sample of repeat contacts by cause for a few weeks. One or two causes usually dominate, and that's where to start.
8 ways to raise first contact resolution
1. Collect the right details up front
Ask for order numbers or account emails in your pre-chat form or contact form, so agents don't have to ask before they can start. Keep it to one or two fields; long forms put people off.
2. Give agents the full picture
The customer's past conversations, orders and recent activity should be visible next to the chat. Being able to see what they did on the website before writing in helps too; session replay shows the visit that led to the question.
3. Build a knowledge base for agents, not just customers
If agents keep asking colleagues the same question, that answer belongs in an article. See how to build a knowledge base.
4. Give frontline agents more authority
If a refund under a certain amount always gets approved, let agents approve it. Every unnecessary escalation is a second contact.
5. Confirm you've understood before answering
A one-line summary ("Just to check: you were charged twice for the same order on Monday?") prevents a wrong answer and the follow-up that comes with it.
6. Answer the next question too
If someone asks how to change their delivery address, they'll probably want to know when the change takes effect. Answer both. Saved replies for common topics can include the usual follow-ups.
7. Switch to a call when chat is going in circles
Some problems are faster to talk through, especially when you can see their screen. Voice and video calls with screen sharing, started straight from the chat, often solve in five minutes what takes an hour by text.
8. Close the loop with a quick check
Before ending a chat, ask, "Does that solve it for you?" If not, you're still in the first contact and can fix it now.
Don't game the number
FCR can be gamed: closing tickets too early, discouraging customers from writing back, splitting one problem into several tickets. Prevent this by measuring reopens and repeat contacts, and by pairing FCR with satisfaction. If FCR rises but CSAT falls, something is off.
Measure it alongside your other numbers
FCR works best as part of a small set: first response time, resolution time, satisfaction and FCR together give a balanced view. Our guide to customer support KPIs shows how to build a simple dashboard.
Common questions
Is FCR the same as one-touch resolution? Close. One-touch usually means a single agent reply; FCR allows several messages in the same conversation, as long as the customer doesn't need to come back.
Does an AI answer count? If the AI solved the problem and the customer didn't come back, yes. Track AI-resolved conversations separately, so you can see both numbers.
How often should I check FCR? Monthly is enough for most teams. Look at it by topic to find where to improve.
Solve it the first time
Customer history next to every chat, saved replies, internal notes, calls with screen sharing and reports on resolution and satisfaction are all included in our help desk and live chat, in every package including the free one. Start free and measure your baseline this month.