WhatsApp automation in India: the rules, the costs and what to build

WhatsApp is the only app that is reliably installed, open and understood by almost every customer in India, which makes it the most effective interface a business can build on. It is also a platform with strict rules, metered pricing and the ability to block your number. Those three facts are not obstacles to work around; they are the design constraints, and software that ignores them gets the business disconnected. This is what we have learnt building on it.

Two different WhatsApp integrations

We have built both and use them for different jobs. The official Cloud API is correct for anything customer-facing and anything at scale. Linked-device libraries are pragmatic for internal notifications where a per-message fee is not worth the paperwork, but they depend on an unofficial interface and will break. When we built a delivery service on one, the design centred on a durable queue precisely because disconnection is normal rather than exceptional.

The 24-hour window, which decides your whole interface

A business may send free-form messages only within 24 hours of the customer's last message. Outside that window, only templates Meta has pre-approved may be sent. This single rule shapes the product more than anything else.

Software that pretends otherwise produces an agent who types a helpful reply, presses send, and watches it fail. In the CRM we built, the countdown is visible on every conversation and the free-form composer is swapped for a template picker the moment the window closes. The rule is enforced by the interface rather than discovered through errors, which is the difference between a tool people trust and one they work around.

Templates are a writing problem, not a technical one

Every message you send outside the window goes through Meta's approval, with variables in place of the parts that change. The technical work is trivial. The difficulty is writing templates that get approved and do not read like spam, and the two failure modes pull in opposite directions: too promotional and it is rejected, too vague and the customer ignores it.

• Write templates for a specific moment, not a general category. 'Your report is ready' outperforms 'Update from our lab'.
• Put the useful content in the template, not in a link. A message asking the customer to click to find out anything is a worse message.
• Keep a utility template utility. Mixing a promotion into a transactional notification is the most common rejection reason we see.
• Submit variants before you need them. Approval is not instant, and a campaign blocked waiting for review is an avoidable problem.

What it costs, and why that should be on screen

Meta bills by conversation category, with rates that differ by country and change periodically. The important structural fact is that messaging is metered, so a campaign has a cost that is knowable before it is sent and frequently is not shown.

We built per-message cost tracking into the WhatsApp CRM for exactly this reason: a campaign of ten thousand messages should display its cost before anyone presses send. Businesses that cannot see the number discover it on the monthly bill, and the usual response is to stop using the channel entirely. The implementation is described in the CRM case study.

Show the cost before the send. Every other rule follows from respecting the meter.

Where AI belongs in a WhatsApp flow

An auto-reply that answers routine questions immediately is genuinely valuable, because the alternative is a customer waiting twenty minutes for an answer that was always going to be the same. The rule we apply is that every automated reply must leave a way to reach a human in one step, and the bot must escalate rather than persist when it is out of depth.

The failure we see most often is a bot that loops. A customer asks something slightly unusual, the bot rephrases its previous answer, and the customer repeats the question with increasing frustration. Detecting that loop and handing over is more valuable than making the bot cleverer.

Consent, and not becoming the business people block

Capture consent to be messaged at registration, make opting out a single word, and honour it immediately. This is partly about the DPDP Act, which expects purpose limitation and withdrawal, and partly about the platform: recipients who report your messages damage your quality rating, and a poor rating reduces how much you are allowed to send. The commercial incentive and the legal obligation point the same way.

A design checklist

1. The message is a copy; the system is the record. Never let WhatsApp be the only place a fact exists.
2. Show the 24-hour window, and never allow a send that will be rejected.
3. Show the cost before a campaign goes out.
4. Every automated reply offers a human in one step.
5. Consent at registration, opt-out in one word, honoured immediately.
6. Conversations belong to the business, so they survive the salesperson leaving.

That last point is why businesses outgrow running sales from personal WhatsApp accounts. When a salesperson leaves, the conversation history leaves with the phone, and nothing was ever attributable.

Frequently asked questions

What is the 24-hour window in WhatsApp Business?

A business can send free-form messages only within 24 hours of the customer's last message. After that, only templates pre-approved by Meta are permitted. Good software displays the countdown on each conversation and switches the composer to a template picker when the window closes, so staff never compose a message the platform will reject.

How much does the WhatsApp Business API cost in India?

Meta bills per conversation, with rates that vary by conversation category and country and that change periodically. Because it is metered rather than flat, the cost of a campaign is knowable before it is sent, so insist that any software you buy displays the projected cost before the send. Check current published rates when budgeting, since they are revised more often than most vendors mention.

Can I send bulk WhatsApp messages legally?

Yes, within the platform's rules: outside the 24-hour window you may only send approved templates, each message is billed, and recipients need a legitimate basis to be contacted. Unofficial bulk-sending tools that bypass this get numbers blocked. Capture consent at registration and make opting out a single word, both because the DPDP Act expects it and because reports from recipients lower your quality rating and your sending limits.

Should I use the official Cloud API or a library like whatsapp-web.js?

Use the official Cloud API for anything customer-facing or at scale, because it is supported, versioned and compliant. Linked-device libraries are reasonable for low-volume internal notifications where no per-message fee is worth the setup, but they rely on an unofficial interface and will break without notice, so build a durable queue around them if you depend on delivery.