WhatsApp automation works when it handles the first reply, the routine questions and the follow-up reminders, and hands every real conversation to a person quickly. For most small businesses that means a WhatsApp Business App with quick replies at the start, then the WhatsApp Business Platform (API) connected to a CRM once volume, multiple agents or tracking needs outgrow the app. This guide covers how to choose, what the rules require, and a 30-day rollout. Rules and prices change often, so everything platform-related below is as of October 2026; check Meta's official pages before you commit.
WhatsApp Business App vs Business Platform (API): how to pick
The WhatsApp Business App is the free phone app. The WhatsApp Business Platform is the API that software connects to, usually through a Business Solution Provider (BSP). They are not two tiers of one product; they work differently.
| Question | Business App | Business Platform (API) |
|---|---|---|
| Who answers | One phone, plus a few linked devices | Many agents on a shared inbox or CRM |
| Automation | Greeting, away message, quick replies, labels | Flows, chatbots, triggers from your CRM or website |
| Bulk or triggered messages | Limited; broadcast lists reach only people who saved your number | Approved templates sent to opted-in contacts, within messaging limits |
| CRM integration | Manual, or by copy and paste | Native through webhooks and your provider |
| Source tracking | Basic | Full, if you capture it at entry |
| Cost | Free to use | Provider fees plus Meta's message charges; see my cost and setup guide |
| Best for | Under a few dozen enquiries a day, one or two people replying | Teams, ad-driven lead flow, follow-up at scale, reporting |
My rule of thumb: stay on the app while one person can reply to everything within minutes. Move to the API when any of these is true: more than two people need to answer from the same number, leads arrive from paid ads or forms and need an instant first message, you want every conversation tied to a CRM record, or you need to message people who enquired earlier. Do not move earlier just because the API sounds more serious. It adds cost and process, and a badly run API setup is slower than a well-run phone.
Opt-in and consent: the part that decides whether your number survives
Meta's WhatsApp Business Messaging Policy (page last updated 23 September 2026 when I read it) says you may contact people only if they have given you their number and opted in to receive your messages. You are responsible for your opt-in method and for following applicable law. Stop and block requests must be honoured whether they arrive on or off WhatsApp.
In practice, a clean opt-in looks like this:
- Say what they will get. "Get your quote and appointment reminders on WhatsApp" beats a pre-ticked box that says "updates".
- Keep it separate by purpose. Agreeing to service updates is not agreeing to promotions. Meta recommends separate opt-ins for message categories.
- Make opting out one word. Include "Reply STOP to unsubscribe" in marketing templates and actually suppress those contacts.
- Never import a bought or scraped list. This is the fastest route to blocks and reports.
A person who messages you first, for instance from a click-to-WhatsApp ad or a button on your site, has started a conversation, which lets you reply. It is still sensible to ask clearly before sending anything promotional later. I am not a lawyer; for India-specific consent and data rules, take advice on how your use of personal data should be documented.
Templates and the customer service window
This is the mechanic that shapes every automation, so it is worth understanding properly. According to Meta's developer documentation (as of October 2026):
- When a customer messages you, a 24-hour customer service window opens. Each new customer message resets the timer.
- Inside the window you can send free-form (non-template) messages: answers, images, documents, your own wording.
- Outside the window you can send only approved message templates, and only to people who have opted in.
- Templates fall into marketing, utility and authentication categories, and Meta charges per delivered message by category and country. There are also free-entry rules for conversations that start from click-to-WhatsApp ads.
The design consequence: your fastest, cheapest and most natural automation happens inside the window, when the customer has just written. Your follow-up after the window closes must be a template, and a template is a message you wrote and submitted in advance, so it has to make sense without knowing what the customer said. Write templates that are specific and useful ("Your site visit is booked for Saturday 11 am. Reply 1 to confirm or 2 to reschedule"), not generic nudges ("Hi, just checking in!"). Specific templates tend to get approved, get read and get fewer complaints.
Chatbots and flows: build for handover, not deflection
A chatbot is not a way to avoid talking to customers. It is a way to collect context and remove waiting. Meta's own policy page says automation can be used when responding within the 24-hour window, but you must offer a clear route to a human, such as a phone number, email or support channel. Treat that as a design requirement, not a footnote.
A flow that works for a service business usually has four steps:
- Greet and confirm. "Thanks for writing to us. Two quick questions so the right person can help."
- Ask at most three things. Need (button choices), city or location, and urgency. Names and phone numbers you usually already have.
- Route. Hot enquiry to a named salesperson with a notification, general question to the support queue, out-of-hours to a promise with a time ("We will reply by 10 am").
- Offer a human at every step. A visible "talk to a person" option, and a rule that any message the bot does not understand twice goes to an agent.
CRM integration and lead routing
Automation without a CRM leaves you with a faster inbox and no memory. The setup I recommend wiring up is simple:
- Create or match a contact by phone number the moment a conversation starts.
- Write the source (ad campaign, page, form, QR code) to the contact record.
- Assign an owner by rule: city, product line, round-robin, or "whoever handled them last".
- Log messages or at least key events (first reply time, qualified, quote sent) against the record.
- Move stages automatically when something concrete happens, such as a quote document sent or a visit confirmed.
If you are choosing or building the CRM side, see CRM and custom software. For connecting forms, ads, WhatsApp and the CRM into one flow, see analytics and automation. Routing rules should be written down in plain words first. If your team cannot say who owns a lead from Gurugram asking about a premium product at 9 pm, no tool will say it for them.
Speed-to-lead follow-up sequences
The first reply is where leads are won or lost, and it is the easiest thing to automate. I will not quote a statistic on response time because the effect varies by industry and what you sell, but the logic is plain: someone who enquired a minute ago is still holding the phone.
| Timing | Action | Human or automated |
|---|---|---|
| Within a minute | Acknowledge, confirm what they asked for, state when a person will reply | Automated |
| Within your stated time | Personal reply from the owner with a specific answer or question | Human |
| Same day, no response | One short, useful nudge: a brochure, price range or booking link | Template, automated |
| Day 2 or 3 | Call. Mention the WhatsApp thread | Human |
| About a week | One last helpful message with a clear opt-out; then stop | Template, automated |
What to automate and what to keep human
| Automate | Keep human |
|---|---|
| Acknowledgement and business hours | Price negotiation and custom quotes |
| Collecting basic details | Complaints and anything emotional |
| Appointment and delivery reminders | Medical, legal or financial advice |
| Sending brochures, location pins, forms | Closing the sale |
| Payment-due and order-status updates | Reactivating a lead who went cold on a bad experience |
A useful test: if a wrong or tone-deaf reply would cost you the customer, a person should send it.
Tracking: click-to-WhatsApp ads, UTMs and CRM stages
WhatsApp conversations are easy to lose in reporting because the click happens on one platform and the lead appears on another. Set up tracking before you scale spend:
- Click-to-WhatsApp ads: these let people start a chat directly from an ad. Use a unique pre-filled opening message per campaign (for example "Hi, I saw the 2BHK offer") so the source is visible in the first line, and map it to a campaign field in your CRM.
- Website buttons and QR codes: use a link with a distinct pre-filled message and UTM-tagged landing page where possible. My UTM builder and the naming conventions guide help keep these consistent.
- Stages, not vanity counts: chats started, replied within target time, qualified, quote sent, closed. Report conversion by source from stage to stage.
If you already get clicks but few enquiries, the problem may be on the site rather than WhatsApp; read why website traffic does not turn into leads first.
Mistakes that get numbers restricted or customers annoyed
- Messaging people who never opted in. Blocks and reports can reduce how many people you are allowed to message, and Meta's policy says large-scale unauthorised messaging can lead to restricted access.
- Vague templates sent to large lists. Low-quality templates affect your quality standing and messaging limits.
- No exit from the bot. People who cannot reach a human block you.
- Ignoring opt-outs. Honour stop requests in the same hour, across every tool.
A 30-day rollout plan
Week 1: decide
Count daily enquiries and reply times, choose app or API, and write your consent wording, routing rules and three reporting stages.
Week 2: set up
On the app, create the greeting, away message, labels and quick replies. On the API, complete business verification, register the number, submit three or four templates and connect CRM contact creation and source capture.
Week 3: build and test
Build the qualification flow with a human option, test with messy real messages, and run the follow-up sequence on a small share of new enquiries.
Week 4: launch and trim
Switch on for all new enquiries, review reply time, handover rate, opt-outs and stage conversion by source, and drop any message nobody responds to.
Timelines depend on verification, template approvals and how much CRM work is needed, so treat these four weeks as a sequence rather than a promise.
Frequently asked questions
Can I automate WhatsApp with the free Business App?
Yes, to a limited degree: greeting messages, away messages, quick replies and labels. For triggered follow-ups, shared team inboxes or CRM integration you need the Business Platform through a provider.
Is WhatsApp lead follow-up automation allowed?
It is allowed when the person has opted in and you use approved templates outside the 24-hour window. Cold messaging to people who never agreed to hear from you breaches Meta's policy and can get your number restricted.
What is the 24-hour customer service window?
It opens when a customer messages you and resets with each new message from them. Inside it you can reply freely; outside it you can send only approved templates. Check Meta's current documentation for any changes.
How do I know which WhatsApp leads came from ads?
Use a distinct pre-filled opening message and campaign field for each click-to-WhatsApp ad or link, capture it in the CRM at the first message, and report by source through to closed deals.
Next step
If you want a second opinion on whether your enquiries need the app or the API, and how to wire follow-up into your CRM and reporting, you can book a 30-minute strategy session (₹2,999 + GST). We will map your current lead flow and decide what to automate first.
