WhatsApp automation for business: what actually works in India

WhatsApp automation for business means letting software send and answer WhatsApp messages for you - order updates, appointment reminders, lead replies, payment follow-ups - instead of a person typing each one. In India you do this through the WhatsApp Business Platform (Cloud API), you pay Meta per message, and Meta's rules decide what you may send and when.

WhatsApp Business app vs WhatsApp Business Platform

These are two different products with the same green icon, and most confusion about WhatsApp automation for business starts here.

The WhatsApp Business app is the free download. One phone, one person, manual work. It gives you a business profile, a catalogue, quick replies, labels, a greeting message and an away message. That is the whole automation story. Broadcast lists are capped at 256 contacts per list, and - this is the part people miss - a broadcast only reaches contacts who have saved your number in their phone. You cannot connect it to your CRM, your website, your billing software or a workflow tool.

The WhatsApp Business Platform, which most people call the Cloud API, is the programmable version. Meta hosts it. Your number lives on Meta's servers instead of a handset, several people can handle the same inbox, and any software you own can send or receive messages through it. This is the only version that can be wired into a real system. Meta does not charge a platform fee for the Cloud API itself - you pay per message, plus whatever your provider or tooling costs.

One hard constraint: a phone number can be on the app or on the Platform, not both. If you move your existing business number to the API, the app stops working on that number. Most businesses keep the old number on the app for walk-in chat and register a second number for automation, at least for the first few months.

What you can and cannot automate under Meta's rules

WhatsApp is not email. You do not get to decide what lands in someone's inbox. Meta's Business Messaging Policy is explicit: you may contact someone only if they gave you their number and gave you opt-in permission to message them. Buying a list and blasting it is the single fastest way to lose a number.

You can automate: replies to anyone who messages you first, order and delivery updates, booking confirmations and reminders, OTPs and login codes, payment links and receipts, feedback requests, lead qualification questions, handing a live chat to a human, and pushing everything into your CRM or a sheet.

You cannot automate: unsolicited promotions to people who never opted in, messages to numbers you scraped, anything about prohibited categories (Meta's policy names firearms, drugs, real-money gambling in most markets, adult services, multi-level marketing and payday loans among others), impersonating another business, or forwarding one customer's chat content to another customer.

Opt-in, in practice

• Put a clear checkbox on your website form: "Send me updates on WhatsApp."
• Log where and when each opt-in happened. If Meta or a customer questions it, that record is your defence.
• Take separate consent for marketing and for transactional updates. People tolerate the second far more than the first.
• Honour STOP. Build the opt-out into the flow on day one, not after the first complaint.

Template messages and how approval works

Any message you send to someone who has not messaged you in the last 24 hours must be a template - fixed wording, submitted to Meta in advance, with variables for things like name, order number and date. Meta reviews it and sorts it into one of three categories.

• Utility - follows something the customer did. Order shipped, booking confirmed, payment received, feedback request. Non-promotional.
• Authentication - one-time codes only, using Meta's predefined formats.
• Marketing - offers, launches, re-engagement, anything selling. The catch-all.

Meta checks the category you picked against its own guidelines. Since 9 April 2025, if you submit something as utility and Meta decides it is really marketing, it is approved as marketing rather than rejected - so it goes out at the marketing rate. Meta also re-categorises already-approved templates, usually with notice. Repeated miscategorisation escalates to warnings, rate limits and template suspension.

Approval is usually fast - often minutes, sometimes a day. The usual rejection causes are avoidable: promotional wording hiding in a "utility" template, a variable at the very start or end with nothing around it, placeholder text you forgot to replace, an unclear link, or writing that reads like a mass blast.

Marketing templates carry a second limit worth planning around. Meta applies per-user marketing limits, throttling how many marketing templates a given person receives when they seem unlikely to be receptive - based on their recent read rate and how full their inbox already is. Hit it and you get error 131049. Note also that marketing templates are not currently delivered to US phone numbers at all, which matters if you sell abroad.

New numbers also start small. A fresh business number begins at 250 unique recipients in a rolling 24 hours, scales to 2,000 after verification, and from there Meta raises the limit automatically when you use at least half your current limit inside seven days while keeping quality high. Plan your first campaign around that, not around your full list size.

The 24-hour window and the pricing model

The customer service window opens the moment a customer messages you and stays open 24 hours. Inside it you can send normal, free-form messages - no template, no fixed script. Once it closes, you are back to templates until they write again.

There is also a free entry point window of 72 hours, triggered when someone reaches you through a Click-to-WhatsApp ad or a Facebook Page call-to-action button and you reply. Every message in that window is free. If you run Meta ads at all, routing them to WhatsApp is the cheapest conversation you will ever have.

On 1 July 2025 Meta replaced conversation-based pricing with per-message pricing. You are charged when a template message is delivered, at a rate set by category and country. Utility and authentication get volume discounts as your monthly numbers grow; marketing does not.

Two changes are landing right now, and anyone budgeting in late 2026 needs them on the whiteboard. From 1 August 2026 Meta began charging for Meta Business Agent messages, metered per token. From 1 October 2026, per Meta's notice on non-template messages, service messages - the free-form replies from your human agents or your own AI inside the 24-hour window - start being charged per message, and utility messages inside the window lose their free status too. The rates match the utility and authentication rates for your market, and there are no volume tiers for service messages.

Practically: the era of unlimited free conversation once a customer writes to you is ending in a fortnight. Build for it now. Keep replies useful and few rather than chatty and many.

Five workflows worth building first

1. Lead capture to CRM

A lead fills your website form or clicks a WhatsApp ad. Within seconds they get a message confirming you have their enquiry and asking two qualifying questions - budget range, timeline, city, whatever actually sorts your pipeline. Their answers write straight into your CRM with a tag, and your salesperson gets a notification only for the leads that qualify. The gain is response time: replying in under a minute instead of four hours changes conversion more than any script rewrite.

2. Order and delivery updates

Order confirmed, packed, shipped with tracking link, out for delivery, delivered. Five utility templates fired from your order system. This is the workflow that kills the most "where is my order" calls, and it is the easiest to get approved.

3. Appointment reminders

A reminder 24 hours before with a confirm or reschedule button, and a short nudge two hours before. Clinics, salons, coaching centres and service businesses usually see no-shows fall noticeably. The reschedule button matters more than the reminder - it turns a lost slot into a moved one.

4. Payment follow-ups

Invoice raised, then a polite reminder three days before due date, on due date, and at seven days overdue, each carrying the payment link and amount. Stop the sequence the moment payment lands. Done well this is the workflow with the clearest rupee return, because collections that used to depend on someone remembering now happen on their own.

5. Feedback and reviews

Two days after delivery or service, ask one question with quick-reply buttons. Route anything below four stars to a human immediately; send the happy ones a Google review link. You get complaints before they become public reviews.

If you want more ideas beyond WhatsApp, our list of n8n automation ideas for business covers the same logic applied to email, sheets and invoicing. And before you build anything, it is worth running the task through this simple test for whether a task is worth automating.

What WhatsApp automation for business costs to run in India

Three separate costs, and only one of them is Meta's.

Meta message charges. India has its own rate card, billed in INR since Meta localised India billing on 1 January 2026. As of September 2026 the widely reported India rates are roughly ₹0.86 per marketing message (raised about 10% on 1 January 2026) and roughly ₹0.12 per utility or authentication message, with 18% GST on top. Rates change and vary by account - check the official pricing page and your provider's current rate card before you budget.

What that means in practice: 3,000 utility messages a month is under ₹400 in Meta charges. 3,000 marketing messages is around ₹2,600. Utility is cheap, marketing is not, and the gap is the whole reason to design flows around things customers actually asked for.

Provider or platform fee. Most Indian businesses go through a partner rather than wiring to Meta directly. Monthly fees vary widely by vendor and features, and many add a per-message markup on Meta's rate. Ask for both numbers in writing - platform fee and effective per-message rate including GST - before signing. We do not quote other companies' prices here because they move; get them from the vendor's own page.

Build cost. Somebody has to design the flows, write and get templates approved, connect your CRM or order system, and set up alerts for when something fails. This is the largest line item in year one and the one that decides whether the rest works. Our AI automation and AI agents service covers exactly this, with fixed scope and price agreed in writing within 48 hours and first automations usually live in about 10 working days.

Mistakes to avoid

• Migrating your only number on day one. Use a second number until the flows are proven. Migration is not casually reversible.
• Treating WhatsApp like an SMS blast. Marketing volume without opt-in quality drags your quality rating down and your limits with it.
• Dressing marketing up as utility. Meta reclassifies it, you pay the marketing rate anyway, and repeat offences cost you templates.
• Automating with no human exit. Every flow needs "talk to a person" as a visible option. Customers who get stuck in a bot loop do not come back.
• No failure alerts. A silent automation that stopped last Tuesday is worse than no automation. Alerts on failure are non-negotiable.
• Budgeting on the old free-service-window assumption. From 1 October 2026 those replies are billable.
• Not owning your assets. The WhatsApp Business Account, the number and the templates should sit in accounts you control, not your agency's.

How to start, in order

1. Pick one workflow. Order updates or appointment reminders - something you already send by hand every day.
2. Count it. Messages per month, minutes per message, who sends them. That number is your business case.
3. Choose your number - ideally a new one - and a provider. Get the full cost in writing, GST included.
4. Verify your business on Meta and register the number on the Cloud API.
5. Write three or four templates in plain language and submit them. Expect one rejection; it is normal.
6. Connect the trigger - your order system, calendar, CRM or a form - to the send.
7. Test on your own team's numbers until the flow is boring.
8. Go live small, watch your quality rating and delivery errors for two weeks, then add the next workflow.

If part of the flow needs judgement rather than a fixed script - reading a messy enquiry, deciding which of six things a customer meant - that is a different tool, and the trade-offs are covered in AI agent vs chatbot. For the plumbing underneath, n8n vs Zapier vs Make compares the three tools most Indian SMBs end up choosing between. You can also see what we have built or browse all three service lines.

Deepanshu Singh co-founded LZ Worth, a Delhi studio that builds AI automations, apps and content systems. He has tested more than 150 AI tools and would rather tell you which ones to skip. More about him.