Summarise this article with:
On this page6 sections
To cut lead response time on WhatsApp, acknowledge every new lead automatically within seconds, ask two or three qualifying questions with buttons, and route the lead to a named rep with a first-response timer running. Then measure the time to the first human reply, not the bot's acknowledgement.
The answer on qualifying leads automatically covers scoring logic, and the real estate guide covers one industry's lead lifecycle. This playbook is the response-time system any sales team can run, whether it sells coaching batches in Kota, loans from an NBFC branch, B2B software in Bengaluru or cars from a Delhi showroom.
Know which door the lead came through
What you can send first depends on who spoke first. When a person messages you, Meta opens a 24-hour customer service window in which you can reply freely, per its documentation on service messages. When you message first, you need an approved template and the person's opt-in.
| Lead source | Who messages first | Your first message | Cost and limits |
|---|---|---|---|
| QR code, wa.me link or website chat button | The lead | Free-form reply inside the 24-hour window | A service message: Meta has charged these since 1 October 2026, after a free tier of 1,000 per business phone number each month |
| Click-to-WhatsApp ad, from the Android or iOS app | The lead | Free-form reply inside the window | Meta does not charge that reply, and it opens a free entry point window of up to 7 days |
| Web form, portal enquiry, missed call or IVR | You | An approved template, only if the lead opted in to WhatsApp messages from your business | Charged by template category, and counts towards your messaging limit |
The ad row comes from Meta's pricing documentation. For the form row, the category matters. Meta's template categorization guidelines include a utility use for continuing on WhatsApp an interaction that began in another channel, as long as the message is non-promotional and specific to or requested by the user. "We have received your enquiry about the NEET 2027 batch; Priya from admissions will message you by 4:00 pm IST" can fit, though Meta checks the category against the content. Add a fee discount and it becomes marketing, at ₹0.94 instead of ₹0.19 per delivered message on InfiQ's India card (ex-GST).
Template sends also count towards your messaging limit: the number of unique users you can deliver to outside a customer service window in a moving 24-hour period, set at business portfolio level and starting at 250 for new portfolios. A weekend lead campaign can hit that ceiling; the messaging limits guide explains how to climb.
The first minute: acknowledge, then ask
The automatic acknowledgement has three jobs, and it can do all three in one message:
- Confirm what they asked about, using the source: the ad, the QR reference or the form fields.
- Say what happens next and by when, in IST: "Arjun from our loans team will message you by 11:30 am."
- Ask the first qualifying question.
For a hypothetical Kota institute, the whole first message might read: "Hi Rohan, thanks for asking about the NEET 2027 batch at our Talwandi centre. Meera from admissions will message you by 6:30 pm IST. Which batch start suits you?" with three buttons: April 2027, June 2027 and Not sure yet.
Meta's message quality guidance advises against open-ended welcome or introductory messages. "Hi! How can we help you?" is exactly that, and it wastes the moment the lead is paying attention.
Keep qualification to two or three questions, and make them tappable. Meta's reply buttons allow up to 3 buttons with titles of up to 20 characters, and list messages allow up to 10 rows with row titles of up to 24 characters.
| Business (illustrative) | Question 1 | Question 2 | Question 3 |
|---|---|---|---|
| Coaching institute, Kota | Course, as a list: JEE, NEET, Foundation | Batch start, as buttons | Classroom or online, as buttons |
| NBFC loan desk | Loan type, as a list | Amount band, as a list | City, as a list |
| B2B software, Bengaluru | Team size, as buttons | Main use, as a list | Timeline: Within 30 days, 1–3 months, Later |
| Car dealership, Delhi | Model, as a list | New or used, as buttons | Test drive slot, as buttons |
Do not ask what you already know. If the ad was for the NEET batch, skip the course question. Save every answer to the lead record so the rep starts where the bot stopped.
Route to the right rep, not the next one
Fast assignment is not fast response. A lead assigned in one second to a rep on a site visit still waits hours. Route in this order:
- Match a pool by language, product or project, and city or territory.
- Rotate within the pool among reps who are on shift, using auto-assignment.
- Start an acceptance timer. If the assigned rep has not replied within your target, reassign the lead or escalate it to the team lead.
- Fall back to a queue when nobody in the pool is on shift, and apply your after-hours rules.
Set the timer from your own data, not from an ideal. If your median human first response in business hours is 40 minutes, a 10-minute timer will breach constantly and the team will learn to ignore the alerts. Start near your current median for hot leads, then tighten it month by month as staffing and routing improve.
Pass the context with the lead: source, reference, answers and any earlier chats. Give hot leads, the ones ready to decide soon, the tightest timer, and send cold leads to a nurture sequence instead of a rep's queue.
After hours and weekends
Leads arrive at 10 pm and on Sundays, and the 24-hour window keeps running. Suppose a lead messages at 9:40 pm IST on Saturday. Their window stays open until 9:40 pm on Sunday, unless they message again. If your first human reply is at 10 am on Monday, the window has closed and you can reach them only with an approved template, which requires their opt-in under the WhatsApp Business Messaging Policy.
Plan the night accordingly:
- Let the bot run the night shift. Acknowledge, qualify and set an honest expectation: "Our team replies from 10 am IST."
- Ask for follow-up permission inside the window. "Can we message you on WhatsApp about this enquiry after today?" with Yes and No buttons. Record the answer, so a Monday template stands on recorded consent.
- Cover the weekend for hot leads. One rep on Sunday, or a callback rota, if Saturday-night leads matter to your business.
- Sort the morning queue by window expiry. Leads whose window closes soonest come first, because a free-form reply is still possible for them.
Measure first response time honestly
First response time is the time from the lead's first message, or form submission, to the first reply. For a sales team, the reply that counts is the first human one; track the bot separately.
| Metric | Measured from and to | What it shows |
|---|---|---|
| Bot acknowledgement time | First inbound message to first automated reply | Broken automations |
| Human first response, median | First inbound message to first human message | The typical lead's experience |
| Human first response, 90th percentile | Same | Where leads are lost: nights, weekends, peaks |
| Window-expiry rate | Leads whose window closed before any human reply, as a share of all leads | Leads you can now reach only with a template |
| Qualified-to-contacted time | Qualification complete to first rep message | Routing performance |
Report each metric in calendar time and in business hours, separately, and split it by source, hour of day and rep. The averages hide the problem: one automated batch can make a mean look healthy while the weekend leads wait a day. When you compare conversion across response-time buckets in your own data, treat it as a signal rather than proof, because reps may answer the most promising leads first. The SLA rules tutorial shows how to turn your target into a timer.
Setting this up on InfiQ
InfiQ's shared team inbox assigns conversations by round-robin, skill-based or team-based routing, and out-of-office hours route to the bot or a queue. First-response and resolution timers with breach alerts track your SLA, and dashboards report response times per agent. In Flows, a lead qualifier is built from question, condition and hand-off blocks; the hand-off can carry an SLA with an escalation path, and a wait block can hold a follow-up until business hours.
