# WhatsApp Lead Follow-Up That Actually Converts | Napnix > Most "we need more leads" problems are follow-up problems. A first-week sequence, what WhatsApp conversation pricing costs, and the three numbers to measure. Source: https://napnix.in/blog/whatsapp-lead-follow-up --- ## WhatsApp Lead Follow-Up That Actually Converts How fast do you have to reply to a lead? Within five minutes, or the enquiry has usually gone cold. The practical target for a small team is the same business hour, with an automated acknowledgement inside one minute so the enquirer knows a human is coming. What loses deals is not a slow answer — it is silence. Almost every “we need more leads” conversation we have turns out to be a follow-up problem. The enquiries are arriving. They are being read. Someone means to reply after this one job, and then the day ends. Two days later the customer has booked someone else, and the business concludes it needs more marketing. This is the cheapest problem in a service business to fix, because it needs no new spend on acquisition. It needs an owner per enquiry and a system that notices silence. ### Why WhatsApp, not email For Indian service businesses the follow-up channel question is largely settled. Email open rates for a cold quote are poor and the reply lands in a promotions tab; a WhatsApp message gets read. More importantly, it gets_replied to_, which is the only metric that matters when you are trying to book a site visit. That has a cost implication worth planning for. The WhatsApp Business Platform bills per conversation rather than per message, and business- initiated conversations cost more than user-initiated ones. So a follow-up sequence is a usage cost that grows with your pipeline rather than a fixed line item. Model it at your expected enquiry volume before you build it — this is the single most common surprise in WhatsApp automation projects. The other constraint is that business-initiated messages must use a pre-approved template. You cannot free-type a follow-up to someone who has not messaged you in the last 24 hours. Design the sequence around approved templates from the start rather than discovering that limit after build. ### What a follow-up sequence should actually do The instinct is to send more messages. The thing that works is to assign an owner and escalate on silence. A sequence that covers the first week: | When | What happens | Who does it | |---|---|---| | Within 1 minute | Automated acknowledgement naming what was asked about and when a human will reply | System | | Within the hour | Real reply with a specific next step — a time for a call or a visit, not "we will get back to you" | Assigned owner | | Day 1, no reply | One short nudge on the same thread | System | | Day 3, no reply | Different angle: a price range, a comparable job, or a direct question | Assigned owner | | Day 5, no reply | Escalation to a manager, or reassignment | System → manager | | Day 7, no reply | Marked dormant with a reason, and a 60-day re-contact scheduled | System | Two details do most of the work. The first is that every enquiry has exactly one named owner, because an enquiry owned by “the team” is owned by nobody. The second is the day-5 escalation: the system has to tell someone when an enquiry has gone quiet, because the person who dropped it is by definition not going to notice. ### What the automation costs to run What does WhatsApp follow-up automation cost per month? The software is the small part. Budget for WhatsApp conversation charges, which scale with your enquiry volume: a business handling 300 enquiries a month with a three-message sequence is paying for roughly 900 business-initiated conversations, not 300. Model it at your real volume before building. The mistake is to price the CRM and forget the messaging. Three things make up the running cost, and only one of them is fixed: - **The CRM itself** — fixed and predictable. A configured tier, or the amortised cost of a build. - **WhatsApp conversations** — variable, and the one that surprises people. Meta bills per 24-hour conversation window, with business-initiated windows costing more than ones the customer opens. Every automated nudge in your sequence is a separate business-initiated conversation if the customer has not replied in between, which is exactly the case you built the nudge for. - **Template maintenance** — small but real. Templates need approval, and a rejected or paused template silently breaks the sequence until someone notices. Put that on a person, not a wiki page. A useful way to size it: take your monthly enquiry count, multiply by the number of automated touches in the sequence, and treat that as your conversation volume ceiling. It will be lower in practice, because customers who reply convert the window to user-initiated, but sizing on the ceiling means the bill never surprises you. Then sanity-check it against the value of one additional booked job — for most service businesses the whole monthly messaging cost is less than a single conversion, which is what makes this worth doing at all. One more constraint worth designing around early: sequences that fire outside working hours annoy people and burn conversations for nothing. Gate the automated touches to business hours in the customer’s timezone, and keep the one-minute acknowledgement as the only message that can go out at any time. ### What to measure Three numbers tell you whether follow-up is working, and none of them is “leads received”: - **Median time to first human reply.** Not average — one forgotten enquiry at four days drags an average into uselessness. - **Share of enquiries with no reply after 24 hours.** This should be near zero. In most businesses that have never measured it, it is between a fifth and a third. - **Share reaching a defined outcome** — quoted, booked, or explicitly marked lost with a reason. Enquiries with no outcome are the ones quietly costing you money. If you do not know those three numbers today, that is the finding. Our [Revenue-Leak Audit](https://napnix.in/audit) is a free 20-minute pass over exactly this: where enquiries enter, who owns them, and where they stop. ### Build it or configure it None of the above needs custom software. A configured CRM with WhatsApp integration, assignment rules and escalation timers covers it, and that is what [Napnix CRM](https://napnix.in/napcrm) does from the Growth tier up — see [pricing](https://napnix.in/napcrm/pricing) for the tier limits. A custom build earns its cost when the routing logic is genuinely unusual — multi-branch assignment, field-team dispatch, or follow-up that depends on inventory or scheduling state. That is a [CRM development](https://napnix.in/services/crm-development) project, and the [cost guide](https://napnix.in/blog/cost-of-custom-crm-2026) works through when building beats configuring. ### The bottom line Follow-up is an ownership problem wearing a software costume. Automation is worth having because it removes the chance of silence going unnoticed, not because it replaces the reply. Assign every enquiry to a person, acknowledge inside a minute, escalate on day five, and measure the median time to a human reply. The leads you already have will convert better than the ones you were about to go and buy. ### Sources 1. [WhatsApp Business Platform — conversation-based pricing](https://developers.facebook.com/docs/whatsapp/pricing/) — Meta 2. [WhatsApp Business Platform — message template guidelines](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/) — Meta 3. [Napnix CRM pricing — the follow-up automation referenced below](https://napnix.in/napcrm/pricing) — Napnix ### About the author Aman Kumar— Founder & Engineering Lead Aman co-founded Napnix and leads its engineering work, building Napnix CRM and the custom CRM and automation systems Napnix delivers for agencies and service businesses. Writes about custom crm development, enterprise software architecture, microservices migration. First published Oct 5, 2026 ### Related Services #### More Services ##### Custom Web Development Scalable web apps tailored to your needs. ##### Mobile App Development Native & cross-platform mobile solutions. ##### AI & Machine Learning Intelligent automation & insights.