Tutorial · 5 min read
Getting the WhatsApp Business API in India: What Differs
The steps to get onto the WhatsApp Business Platform are the same in Mumbai as in Manchester. What differs is which of them slow you down, and in India the answer is consistently the paperwork and the display name — not the code.
This post assumes you know the general sequence. If you do not, the setup post covers it end to end. What follows is the India-specific texture.
Business verification is the whole timeline
Meta verifies that the legal entity you claim exists, and it does that by matching documents to what you have entered. The mismatch that stalls Indian applications is almost always the same one: the business name in Meta Business Manager is the brand, and the documents are in the name of the registered entity.
If your storefront is "Sunrise Kicks" and your registration says "Sunrise Trading Company Private Limited", enter the registered name. The brand goes in the display name later, which is a separate review.
Proprietorships and partnerships take more attention than private limited companies, simply because the documentation is less standardised. It is not a blocker. It just means you should read Meta's current requirements page rather than a checklist someone posted two years ago.
The display name review is separate, and stricter than people expect
Business verification says the entity is real. The display name review says the name you show to customers is defensible. Two names, two reviews, two chances to wait a week.
The names that get rejected in practice:
- A generic word that is not the business — "Offers", "Support", "Shop Now".
- A name with no visible relationship to the verified entity or a domain you control.
- Anything that reads as a claim rather than a name.
Pick the name customers already call you, and make sure it appears somewhere public — your website, your Instagram bio, your GST-registered signage.
Choosing the phone number
This is the decision people reverse least happily.
A number registered to the Cloud API stops working in the free WhatsApp Business app. If the number currently on your shop's board is the one your regulars message, and it is running on a phone behind the counter, moving it onto the API means that phone goes dark.
Move the existing number
Take a fresh number
Most Indian businesses that already get real volume on a counter number should take a fresh number for the API and migrate deliberately, not on a Tuesday afternoon.
Templates in Hindi, Hinglish and regional languages
Templates are submitted to Meta with a language, and they are reviewed. A few practical notes from how the review behaves:
- Submit the language you will actually send. A Hinglish template written in Latin script is submitted as such. Do not submit English and then hope to vary it — the approved text is the text.
- Placeholders need context. A template that is mostly variables, especially one that opens with one, reads as spam-shaped to a reviewer. Write real sentences with variables inside them.
- Category honestly. A festive discount is marketing, whatever you call it. Filing it as utility to change the economics is the kind of thing Meta reclassifies.
An approved template is a format, not permission. Opt-in is a separate obligation and Meta requires you to have it.
Opt-in, and why Indian businesses should be careful here
Meta requires businesses to obtain opt-in before sending template messages. That is a platform rule, and it exists independently of Indian data protection law, which also has opinions about consent and notice.
The practical version: record how and when each contact opted in, keep the record, and make opting out easy and instant. A number scraped from a customer list you bought is not opt-in, and the consequences show up as a falling quality rating long before anyone sends you a legal notice.
What this costs to run
Meta charges per conversation, by category, and rates vary by country. India is one of the largest WhatsApp markets in the world and it is priced on the same model as everywhere else — a model, not a flat fee. Do not budget from a blog post; read Meta's pricing page on the day. The cost drivers are worth understanding separately, because the levers you control are structural rather than negotiated.
A realistic plan
- Start verification immediately, before you have decided anything else. It is the longest step and everything queues behind it.
- Settle the number question while verification runs, since it needs a human decision rather than a form.
- Write four or five templates and submit them early, so rejections happen during the wait rather than after it.
- Build receiving before sending. A reliable webhook is worth more on week one than a clever flow.
- Pilot on a small opted-in group so the first real invoice and the first real quality signal both arrive at a size you can read.
If you are weighing this against a channel with a public entry point and no per-message charge, the honest comparison is here — including what PostEngage actually does today, which is Instagram.
