What is first contact resolution (FCR)?
First contact resolution (FCR) is the percentage of customer issues that are fully resolved in the first conversation, without the customer needing to come back, be called back, or have the ticket reopened. It started in call centres as first call resolution and applies just as well to WhatsApp, email and chat support.
The basic formula is issues resolved on first contact ÷ total issues handled × 100. What makes FCR tricky is deciding when a conversation was the first and only one. Most teams use a recontact window: if the same customer contacts you again about the same issue within, say, 7 days, on any channel, the first conversation did not count as resolved. Others ask the customer directly ("Did we solve your issue today?") and blend the two.
WhatsApp needs one more definition. Because it is asynchronous, a single issue can stretch over a morning of messages with pauses while the customer finds a receipt. Counting each burst of messages as a new contact would make FCR look terrible. Define a contact as one issue from first message to resolved, regardless of gaps, and treat a reopen of the same issue as a second contact.
FCR is distinct from resolution time, which measures how long resolution took, and from first response time, which measures the wait for the first reply. It sits close to deflection rate and Customer Effort Score: repeat contacts are among the clearest signs of customer effort.
Key takeaways
- First contact resolution (FCR) is the percentage of issues fully resolved in the first conversation, with no repeat contact about the same issue.
- Formula: issues resolved on first contact ÷ total issues × 100, using a reopen or recontact window such as 7 days.
- On WhatsApp, one "contact" must be defined by issue, not by message, because chats pause and resume over hours.
- FCR measures completeness; resolution time measures speed. A fast answer that brings the customer back is not first contact resolution.
First contact resolution (FCR): key facts and limits
- Formula
- Issues resolved without recontact ÷ total issues × 100
- Common recontact window
- 7 days (some teams use 24–72 hours)
- Unit of measure
- One issue, not one message or one session
- Measures
- Completeness, not speed
- Common data sources
- Ticket reopens, cross-channel recontacts, customer survey
Common mix-ups
Common mistakes with first contact resolution (FCR)
Counting message bursts as contacts
Splitting one WhatsApp issue into several "contacts" whenever the customer pauses makes FCR meaningless. Define contacts by issue, from first message to resolved.
Only looking at one channel
A customer who chats on WhatsApp and then phones about the same problem was not resolved first time. Match recontacts across channels.
Closing chats to protect the metric
Agents may mark issues resolved too early or open new tickets instead of reopening. Audit a sample and use customer confirmation alongside system data.
Including issues that cannot be solved in one contact
A replacement that needs a technician visit will always need follow-up. Exclude planned multi-step journeys, or report them separately.
How does first contact resolution (FCR) work?
- Step 1
Define one issue
A contact is one issue from the customer's first message to resolution, even if the chat pauses for hours. Tag the issue so recontacts can be matched to it.
- Step 2
Set a recontact window
Choose how long after resolution a return about the same issue counts against FCR — 7 days is common — and apply it across WhatsApp, phone and email.
- Step 3
Match recontacts
Link returning customers by wa_id, BSUID, phone or email, and compare the primary tag. A reopened ticket or a new chat on the same tag inside the window is a repeat.
- Step 4
Calculate and segment
FCR = issues resolved without recontact ÷ total issues × 100. Report it per tag, team and agent, excluding issues that were never resolvable on first contact by design.
- Step 5
Fix the causes of repeats
Read repeat cases: missing permissions, wrong answers, transfers that lost context, promised call-backs. Each fix moves FCR more than coaching speed.
Example: Address changes at a Delhi courier company
A Delhi courier company handles 5,000 WhatsApp issues in a month. 3,350 are resolved with no recontact within 7 days, so FCR is 67%. The address-change tag is far lower at 41%: agents can note a new address but cannot update the delivery system, so customers return when the parcel goes to the old address. Giving L1 agents direct access to update the address, with a confirmation message in the chat, lifts that tag above 80% and cuts total volume by several hundred issues the next month.
Why the difference matters
Why does first contact resolution (FCR) matter?
Every repeat contact costs twice: agent time on a problem that should already be closed, and customer patience. Teams with high FCR typically also see better CSAT and lower volume, because unsolved issues generate more conversations. On WhatsApp, each extra agent reply is a service message, charged per message in India since 1 October 2026, so repeat contacts also add directly to messaging cost.
FCR FAQs
How do you calculate first contact resolution?+
What is the difference between FCR and resolution time?+
How do you measure FCR on WhatsApp chat?+
What is a good first contact resolution rate?+
Rules of thumb
Best practices for first contact resolution (FCR)
- Give L1 agents the permissions to finish common fixes themselves; it is the biggest FCR lever.
- Use warm transfers with notes, so a transfer does not turn into a repeat contact.
- Ask "Is there anything else?" before closing — many recontacts are a second question, not a failed first one.
- Publish FCR per tag beside average handle time so speed never wins over completeness.