How fast should you reply on WhatsApp?

The honest answer is that nobody can tell you, because almost nobody has measured it. The lead-response statistics that get quoted at you, such as reply within minutes or the lead goes cold and most customers buy from whoever answers first, were measured on phone calls and web forms, years ago, and then repeated by every article since. They describe a real shape: speed wins. They do not describe WhatsApp, and they were never a target, only an observation.

So treat any WhatsApp benchmark that arrives without a method the way you would treat a reference the candidate wrote themselves. The useful question is not “what is the industry number?” It is “what is my number, and what should it be?”, and you can answer both this month.

Start with the number you already have

Before you set a target, measure the team you actually run, over a normal fortnight, not the week after you announce you are measuring. You want the median first reply: the wait a typical customer experienced, counted from their message to the first answer from anyone on your side, not from when a rep opened the app.

The median, not the average. One conversation abandoned over a weekend drags an average somewhere useless, and every team has one. An average also flatters you in the other direction: a rep who fires back “noted” in 30 seconds and then goes quiet for a day looks excellent in it.

You can get this number by hand, exporting a sample of chats and timestamping the first replies yourself, and for a 2-rep team that is a reasonable Saturday. Past that it stops being one, which is what an archive on the company numbers is for: the same measurement, on every conversation, without anyone doing the timestamping.

Then set the target you would say out loud

The right target is not a percentile of somebody else’s data. It is the wait you would be comfortable defending to the customer who experienced it. “We aim to answer within 15 minutes in business hours” is a sentence you can say to a customer and to your team. “We aim to beat the industry median” is not, because there isn’t one worth the name.

Two rules make the target honest:

1. Count business hours, not the clock. A message at 21:40 answered at 08:15 is not an 11-hour failure, and a target that says it is will be ignored by February. Response tracking measures against the business hours you set for exactly this reason.
2. Set it per conversation, not per rep. The customer does not care which rep was slow. First reply from anyone on your side is the number the customer felt.

The worst case matters more than the median

A team can hold a fine median while one customer in 10 has a very different experience of your company. The median describes a normal day; the longest wait describes the customer having the worst one. When you measure, look at both ends: the typical wait, and the oldest unanswered conversation right now, by name.

The pattern we see when a team measures for the first time is consistent enough to predict. The median is usually better than the manager feared. The spread between the fastest and slowest rep is wider than anyone guessed. And there are almost always a few conversations that nobody ever answered at all: not slowly, not badly, just never. Those are the ones worth finding first, because no reply target fixes a conversation that isn’t on anyone’s list.

Where the published numbers are

We are building the WhatsApp-specific dataset this question deserves, and we are doing it in the only order that keeps it trustworthy: the benchmarks report publishes the method first, covering what counts as a first reply, how business hours and group chats are handled and what gets excluded, and the aggregate numbers follow once the cohort is large enough to anonymise properly. We would rather show you an empty table with an honest method than a full one with neither.

Until then, the standard that matters is yours: your median, measured on a normal fortnight; a business-hours target you would say to a customer; and a worst case you check by name, not by average. If you set those 3 this month, you will be measuring your team more honestly than any benchmark article would have let you.