WhatsApp Response Time: What Indian Customers Expect and How to Measure It

WhatsApp is not email. A customer who messages your business at 8:40pm has the app open and is comparing you with two competitors they messaged in the same minute. Reply speed is not a service nicety on this channel; it is most of the conversion difference between businesses selling the same thing at the same price.

This guide sets out what to measure, what is realistic to target, and how to hit those targets without hiring a night shift.

Why speed matters more on WhatsApp than anywhere else

Three reasons, and the third is financial.

The customer is present. Unlike a contact form, a WhatsApp message is usually sent while the person is actively deciding. Reply in two minutes and you are talking to someone who is still thinking about it; reply in two hours and you are interrupting.

They messaged several businesses. Especially from click-to-WhatsApp ads and Google Business Profile. First substantive reply often wins, and the gap is rarely about price.

The 24-hour window. Once a customer messages you, you can reply freely for 24 hours at no per-message charge. Miss that window and you must use a paid template, and marketing templates additionally require opt-in. Slow replies therefore cost money as well as sales — the free lane closes.

The four metrics worth tracking

• First response time. Minutes from the customer's first message to a human or meaningful automated reply. Track the median, not the average — one four-hour outlier distorts an average, and the median tells you what a typical customer experienced.
• Unanswered rate. Conversations that received no reply at all. This is the number most businesses have never measured and the one that hurts most. Anything above 5% needs fixing before you optimise anything else.
• Resolution time. From first message to the customer's question actually being answered. A fast greeting followed by three hours of silence is worse than an honest four-minute wait.
• Within-window reply rate. Share of conversations answered inside the 24-hour service window. Directly tied to cost, because everything outside it needs a paid template.

Measure per agent and per branch, not only site-wide. Averages hide the one location losing every lead after 6pm.

Realistic benchmarks for Indian businesses

These are targets we see working in practice, not aspirational numbers.

• Sales enquiries in working hours: median first response under 5 minutes. Under 2 minutes for ad-driven leads, where competition is direct and simultaneous.
• Sales enquiries outside working hours: an automated acknowledgement within seconds that sets a clear expectation, and a human reply within the first hour of the next working day.
• Support queries: median first response under 15 minutes in working hours; resolution the same day for routine issues.
• Order and delivery questions: instant, because these should be automated lookups rather than human work.
• Unanswered rate: under 2%. Zero is the right target for sales conversations.

If your median first response is currently measured in hours, do not start with these numbers. Halve what you have, hold it for a month, then halve it again.

The auto-reply that helps, and the one that hurts

An instant acknowledgement is valuable only if it does work. "Thank you for contacting us, our team will get back to you shortly" does none — it tells the customer nothing and buys no patience.

A useful acknowledgement does three things: it states a specific expectation ("our team replies within 15 minutes, 9am to 8pm"), it offers something immediate (price list, catalogue, service areas, booking link), and it asks a qualifying question so your first human reply can be substantive. Handled well, the customer gets value in the first thirty seconds and your agent opens with an answer instead of "how may I help you".

Out of hours, be honest about the time. "We open at 10am and will reply first thing" holds a customer far better than "shortly" followed by silence until morning.

How to get fast without hiring a night shift

1. Automate the questions that are lookups

Order status, timings, service areas, price bands, document requirements. These are the bulk of inbound volume for most businesses and none of them need a person. Automating them does not merely speed those conversations up; it clears the queue so humans reach the real enquiries faster. See our guide on when a chatbot should hand over to a live agent.

2. Put every conversation in one inbox with clear ownership

Most slow replies are not laziness; they are ambiguity about who is answering. Assign conversations explicitly, show unassigned ones prominently, and alert when anything sits untouched past your target. Our shared inbox guide covers assignment rules.

3. Build quick replies for the twenty things you type daily

Saved replies for pricing bands, address and directions, warranty terms, payment details. A three-minute reply becomes twenty seconds, and quality becomes consistent across agents.

4. Staff to your actual traffic curve

Pull the hourly distribution of inbound messages for the last month. Indian consumer businesses usually see peaks around lunch and again between 8pm and 11pm — hours when most offices are shut. Shifting one person's hours later in the day typically does more for response time than adding a person at 10am.

5. Escalate on silence, not on complaint

Set an alert when a conversation has been waiting beyond your target. Catching it at fifteen minutes is cheap; hearing about it as a complaint is not.

Getting it wrong in the other direction

Speed is not the only variable. Three fast but wrong patterns to avoid: a bot that answers in one second and cannot solve anything, agents who send a holding message to stop the clock and then disappear, and replies so short they read as curt. Measure resolution time alongside first response so that gaming one number is visible in the other.

Where to start this week

Export the last thirty days of conversations and calculate two numbers: median first response time, and the count of conversations with no reply at all. Most businesses doing this for the first time are unpleasantly surprised by the second. Fix unanswered conversations first — they are pure lost revenue and usually the result of a routing gap rather than a staffing one. Then work on the median, then on the hours when nobody is watching.

Why the median matters more than the average

Almost every team that measures response time measures it wrongly, and the wrong number hides exactly the problem you are trying to find.

One message left overnight — twelve hours — inside fifty messages answered in two minutes produces an average of about sixteen minutes. That looks acceptable and it is not: one customer waited half a day. The median would have shown two minutes and the outlier would have shown up where it belongs, in a separate count of messages that waited more than an hour.

Three numbers, reported together, tell the truth:

• Median first response time — your normal experience.
• Count of conversations waiting over 60 minutes — your failures, named individually so somebody can look at them.
• Median during your busiest hour — your real capacity. A team that is fast at 11 am and slow at 7 pm has a rostering problem, not a speed problem.

Setting a commitment you can actually keep

A published response time is worth more than a fast one nobody promised, because it stops the customer messaging three competitors while they wait. To set it honestly:

1. Pull last month's hourly message distribution. Most Indian businesses see a lunchtime band and an evening band, with Sunday unlike any weekday.
2. Find the hour where your median is worst. That is the number you can promise, not your best hour.
3. State it in the away message and on the website. "We reply between 10 am and 7 pm, Monday to Saturday" beats "we will get back to you soon" by a wide margin.
4. Review it monthly. If the busy-hour median has drifted, either the roster or the automation needs to change before the promise does.

Then measure against the promise rather than against an industry figure. Your own trend, hour by hour, is the only benchmark that can actually be acted on.

Frequently Asked Questions

How fast should a business reply on WhatsApp in India?

Aim for a median first response under 5 minutes for sales enquiries in working hours, and under 2 minutes for leads from click-to-WhatsApp ads. Support queries can sit at 15 minutes, while order-status questions should be automated and instant.

Does a slow WhatsApp reply cost me money directly?

Yes. You can reply free for 24 hours after a customer messages you. Once that window closes you must send a paid template, and marketing templates also need opt-in, so slow replies raise costs as well as losing sales.

Should I use an auto-reply for messages received after hours?

Yes, but make it specific. State your actual opening time, offer something useful immediately such as a catalogue or price list, and ask one qualifying question. A vague promise to reply "shortly" holds nobody.

What is the most important WhatsApp metric to track?

The unanswered rate — conversations that never received any reply. Most businesses have never measured it, it is usually caused by a routing gap rather than staffing, and it is pure lost revenue.

How do I improve response time without hiring more staff?

Automate lookup questions such as order status and timings, assign every conversation to a named owner, build quick replies for your twenty most common answers, and shift staff hours to match your real evening traffic peak.