How long you take to answer a WhatsApp, and what that delay costs you

The number almost nobody measures

WhatsApp response time is how long passes between a message arriving and your first one going out. It is the easiest metric to get in your whole business and the one fewest people look at.

Harvard Business Review audited 2,241 companies to measure it. Among those that replied at all, the average was 42 hours, and 23% never replied. In that gap sits almost everything that decides whether that person buys from you or from whoever answered first.

What happens to a buyer while they wait

Conversion data for WhatsApp draws a fairly cruel curve:

How long they waited	What happens
Under 1 minute	8 times more likely to qualify than if they waited over 5
Each extra minute	Probability of closing drops 3% to 5%
30 minutes	70% have gone cold
4 hours	90% are lost

Data from Harvard Business Review, across 2,241 audited companies.

What matters in that table is not the exact number, which varies by industry. It is the shape: the drop is steepest at the start. The first five minutes are worth more than the following four hours combined.

And there is something the table does not show. The person who wrote to you also wrote to three others. They are not waiting. They are comparing.

Measure yours before fixing it

It takes twenty minutes by hand and needs no tooling.

Take the last 30 messages that came in. For each one, note the time it arrived and the time of your first reply. Take the median, not the average: one message you answered the next day skews the mean and makes you think you are worse than you are.

Then split those 30 into three groups, because each one is fixed differently:

• The ones that arrived during business hours and still took long.
• The ones that arrived after hours.
• The ones that arrived as voice notes.

The three delays and how to remove them

The overnight delay. Everything that arrives after you close waits until morning. That is 12 to 16 hours on the clock, and it is the easiest to eliminate: an automatic reply that resolves the frequent questions already leaves the customer with what they came for.

The audio delay. A three-minute voice note needs three minutes of somebody, which is why it gets postponed. When it arrives transcribed in the chat, it reads in ten seconds and stops being a message people skip.

The "not mine" delay. The message arrived, three people saw it, each assumed someone else would take it. This is fixed by assigning conversations, not by asking for more attention.

None of the three is solved by hiring. They are solved by taking the message out of the queue.

Lowering the number is not answering just anything

One warning, because it is easy to optimise the metric and damage the business.

A 5-second response time with an answer that resolves nothing is worse than 10 minutes with a useful one. If you are going to measure time, also measure how many conversations end without anyone on your team having to step in. Together they tell you something. Alone, the first one lies.

That is why sensitive queries are better handed off to a person with the reason written down, rather than resolved fast and badly.

Key takeaways

• Measure the median of your last 30 messages. Twenty minutes of work, and it is your baseline.
• The loss curve is steepest at the start: the first 5 minutes are worth more than the 4 hours that follow.
• Split the delay in three, because each is attacked differently: the night, the audios and the ownerless messages.
• The overnight delay is the biggest and the cheapest to eliminate.
• Look at response time together with resolution. On its own, speed can be faked.