First contact resolution rate on WhatsApp: how to calculate and interpret it
What is first contact resolution rate (FCR) on WhatsApp
First contact resolution rate (FCR) measures the percentage of inquiries that are resolved in the first interaction, without the customer having to write again about the same issue. On WhatsApp, where the conversation is asynchronous and can stretch over hours, defining "first contact" is not as straightforward as in a phone call. This page gives the specific formula, which messages go into each part of the calculation, and a table to interpret the result by industry.
FCR matters because it is correlated with service cost: every time a customer writes again about the same problem, the conversation consumes another 24-hour window, another agent or more AI time. It is not an abstract quality metric: it is an operational efficiency metric.
The formula: what goes in the numerator and what goes in the denominator
The general formula is the same one used in call centers, but you have to adapt what counts as "first contact" and what counts as "resolution" when the conversation is over text messages.
| Component | What it includes | What it excludes |
|---|---|---|
| Numerator: inquiries resolved on first contact | Conversations where the customer did not write again about the same issue after the first response that resolved their inquiry. | Conversations where the customer asked something new and different (that is a new inquiry, not a follow-up). |
| Denominator: total inquiries received | All conversations that a customer started with a specific question or request. | Automatic welcome messages, order confirmations, campaign notifications or messages that do not require a response. |
| Measurement period | One week or one calendar month, in the business's local time. | Individual days: daily FCR is very volatile due to seasonality. |
| Channel | WhatsApp only (or Instagram only, if measured separately). | Mixing channels in the same rate: response times and customer behavior are different. |
The formula is as follows: FCR = (inquiries resolved on first contact / total inquiries) × 100. The result is a percentage: if out of 200 inquiries, 140 were resolved without the customer writing again about the same issue, the FCR is 70%.
How to identify an inquiry resolved on first contact with real data
The practical problem is that no platform gives you FCR solved: you have to define it with the data you do have. With the WhatsApp API (the one Wando uses), you can reconstruct each conversation and classify it with three rules.
- The customer wrote a message with an inquiry (not a greeting or a "thank you").
- The business replied and the customer did not write again about the same matter in the following 24 hours (the conversation window period).
- If the customer wrote again, you have to look at whether it is the same topic or a new one. This is the hardest part to automate: a message like "hi, I'm still waiting" is clearly the same topic; "hi, can you send me the price of the other product?" is not.
If you use Wando, the inbox stores the complete history of each conversation and you can export conversations by tag or by agent. To measure FCR without programming, the simplest option is to tag as "resolved on first contact" every conversation that the agent closes without the customer having reopened the topic. It is not perfect, but it is consistent if all agents use the same rule.
Interpretation table: what each FCR range means
There is no universal "good" number. In telephone call centers, 70-75% is often cited as a reference, but WhatsApp has particularities: the customer can write at any time and the business's response time depends on whether there is someone on the other side. The table below is an operational guide to interpret the result, not a standard certified by any association.
| FCR range | What it indicates | What to review first |
|---|---|---|
| 85% to 100% | Support resolves almost everything on the first reply. Risk: it may be avoiding complex inquiries or under-referring. | That there are no inquiries being closed without resolving them (the customer does not come back because they got tired, not because they were satisfied). |
| 70% to 84% | Healthy range: most inquiries are resolved on first contact and the rest are cases that require research or referral. | Maintain the current process and monitor whether the percentage drops when volume increases. |
| 50% to 69% | There is a significant portion of inquiries that require more than one back-and-forth. Review whether the replies are complete or whether data is missing in the first reply. | The agents' replies: do they include all the information the customer asked for? Are templates being used that answer only part of the inquiry? |
| Less than 50% | Most inquiries require multiple exchanges. The cost per conversation skyrockets and the customer is probably frustrated. | The support process: are there hours without coverage? Do agents have access to the information they need (order status, prices, stock)? Is the inquiry being referred internally without notifying the customer? |
Common mistakes when calculating FCR on WhatsApp
FCR seems simple until you calculate it with real data. These are the mistakes that distort the number the most.
- Counting individual messages instead of conversations: FCR is calculated per inquiry, not per message. A customer who sends 5 messages in a row before the business responds is one inquiry, not 5.
- Not separating new inquiries from follow-ups: if the customer asked about the price, you answered, and then they asked about the schedule, that is not a failed FCR: it is a new inquiry. Mixing them artificially lowers the rate.
- Measuring on individual days: Monday might show 80% and Tuesday 40% simply because Tuesday had a spike in complex inquiries. Measure by week or by month.
- Not considering business hours: if the business closes at 18:00 and the customer writes at 23:00, it cannot be resolved until the next day. That is not a first-contact failure, it is a business-hours limitation. Measure FCR only on inquiries that came in during business hours, or split it into two rates: within hours and outside hours.
- Using the message creation date instead of the event date: if you imported the history from another platform, the timestamp of when the record was inserted into your database is not when the conversation happened. Always use the WhatsApp event date.
What to do when FCR is low: a diagnosis guide by cause
A low FCR is not fixed by "answering better." You have to identify the root cause, which is usually in the process, not in the agent. This table organizes the diagnosis by symptom.
| Symptom | Probable cause | Concrete action |
|---|---|---|
| The customer always writes back with the same question | The first response did not answer everything the inquiry required. | Review the template responses: do they include price, availability, timeline, and payment method when the inquiry calls for it? |
| The customer writes back several hours later | The response arrived late and the customer no longer trusts that it is complete. | Measure first response time separately. If it is high, the problem is speed, not content. |
| Inquiries are forwarded internally and the customer does not receive a response until the next day | There is no clear handoff process between agents or areas. | Define one owner per conversation: if it is forwarded, the original agent tells the customer they will respond within X timeframe. |
| The customer writes at 23:00 and only receives a response at 10:00 the next day | There is no after-hours coverage and no automatic response that manages expectations. | Set up an after-hours auto-reply that states when they will receive a response. It does not resolve the inquiry, but it prevents the customer from writing again 10 minutes later. |
How to calculate FCR with the information you already have in Wando
If you use Wando, you do not need to program anything to get an approximation of FCR. The method is as follows:
- 1At the end of each week, export the conversations from the last 7 days from the contacts or statistics section.
- 2Filter the conversations that a customer started with an inquiry (exclude those that are only responses to campaigns or automated messages).
- 3For each conversation, check whether the customer wrote again after the business's first response. If they did not write again, count it as resolved on first contact.
- 4If they did write again, check whether the second message is about the same topic or a new one. If it is the same topic, it does not count as resolved on first contact.
- 5Apply the formula: (resolved on first contact / total inquiries) × 100.
This manual method is consistent if all agents use the same criteria to decide whether a second message is the same topic or a new one. If you want more precision, the alternative is to tag each conversation as "resolved on first contact" or "required follow-up" at the moment it is closed. The tag is more reliable than after-the-fact analysis, because the agent who handled it has the full context.
FCR limitations on WhatsApp you need to know about
FCR has limits that are worth keeping in mind before using it as your only quality metric.
- It does not measure satisfaction: a customer may not write back because they got tired or because they found the answer elsewhere, not because they were satisfied.
- It depends on the definition of "same topic": two agents can classify the same conversation differently. That is why the rule has to be written down and be the same for the whole team.
- It does not distinguish simple queries from complex ones: an FCR of 80% can hide the fact that all simple queries are resolved well and all complex ones require follow-up. Look at FCR broken down by query type if the volume justifies it.
- WhatsApp's 24-hour window shapes what counts as "writing back": if the customer writes two days later, it is probably a new topic or a different query. If they write an hour later, it is the same topic.
Frequently asked questions
Short answers to the most common questions about this metric are in the frequently asked questions section at the end of this page.
Frequently asked questions
What is a good first contact resolution rate on WhatsApp?+
There is no universal standard. In phone support, 70-75% is often cited as a reference, but on WhatsApp it depends on the industry: simple inquiries like hours or prices tend to exceed 80%, while industries with complaints or technical inquiries usually fall between 50% and 70%. The most useful approach is to measure your own history and compare against yourself month over month, not against a generic number.
How do I know if a customer who writes again is on the same topic or a new inquiry?+
The practical rule is: if the second message asks for information that was already in the first reply or that is a direct consequence of that reply (e.g. 'did my order arrive?' and then 'did it arrive?'), it is the same topic. If it asks for something different (e.g. 'do you have this product in another color?'), it is a new inquiry. The rule has to be written down and the same for the whole team, because two agents can classify the same conversation differently.
Is FCR calculated per message or per conversation?+
Per conversation, or more precisely per inquiry. A customer who sends 5 messages in a row before the business replies is a single inquiry. FCR measures whether that inquiry was resolved with the business's first reply, not how many messages the customer sent.
What should I do if my FCR is very low (under 50%)?+
First check whether the problem is in the process, not the agents: are there hours without coverage? Do agents have access to order status, prices and stock? Are inquiries forwarded internally without notifying the customer? Then check whether the replies include all the information the inquiry asks for (price, availability, timeline, payment method). A low FCR is almost always a symptom of missing information in the first reply or of delayed responses.
Does Wando calculate FCR automatically?+
Wando does not show an automatic FCR indicator: it stores the full conversation history and lets you tag each one. To measure FCR without coding, the option is to tag each conversation as 'resolved on first contact' or 'required follow-up' when closing it, and then calculate the percentage over the total. The tag applied by the agent who handled it is more reliable than analyzing the conversation after the fact.
Answer WhatsApp with AI
Try Wando free. No credit card required.