The WhatsApp Business app
The free app on a phone. One device, one person, no integration. Fine for a shop; it falls apart the moment two people must answer the same number, and it cannot be driven by your software.
What it actually is, what you need before you can have it, what Meta charges, and how to tell a provider worth paying from one that is reselling you your own messages. Written for the person who has to make the decision, not for a search engine.
Most of the confusion in India is vocabulary, not technology.
The free app on a phone. One device, one person, no integration. Fine for a shop; it falls apart the moment two people must answer the same number, and it cannot be driven by your software.
Meta hosts it. Your number lives on Meta's servers, your software talks to it over HTTPS, and many people can answer at once. This is what everyone means today when they say "the API".
The old model, where a provider ran a container on their own servers. Meta has retired it. If someone is still quoting you an on-premises setup in 2026, that is a reason to ask more questions.
Less than most people are told, and none of it costs money.
The verified badge beside a business name is a different, discretionary Meta decision based on how notable the brand is. No provider can sell it to you, and any that claims to is telling you something useful about themselves.
Historically, yes — moving a number onto the API meant the app on the handset stopped working, which is why so many Indian businesses never moved. That is no longer true.
Coexistence lets the WhatsApp Business app and the Cloud API run on the same number at the same time. Your team keeps replying from the phone exactly as they do now, while the same conversations also appear in a shared inbox on a computer. Recent chat history and contacts come across during onboarding.
In practice this removes the only real objection. Nobody has to change how they work on day one; the desk simply gains a second, better way of working.
A Coexistence number stays tied to the handset's WhatsApp account. If somebody logs out of the app, reinstalls on a new phone or disconnects the business account, the link can break and the number silently stops working on the API. Ask your provider whether they monitor for that, or whether you will find out when a customer complains.
Meta bills your own Meta account for business-initiated messages, at published Indian rates that differ by category — marketing, utility, authentication. A customer writing to you is treated differently from you writing to them, and there is a monthly allowance of free service messages before any of it starts.
The inbox, the CRM, the automation — that is the subscription. The question worth asking on every sales call is whether the provider also takes a cut of Meta's message charges. Many do, quietly, by reselling conversations at a markup.
SaarFlow does not: Meta bills you directly at Meta's rates, and our invoice is the plan and nothing else. See the pricing →
Ask these on the first call. The answers are short, and they are revealing.
It should be you, inside your own Meta Business account. If the provider owns it, leaving them means leaving your number and your history behind.
A straight no is the answer you want, with Meta billing you directly so you can see the usage yourself in Business Manager.
Per-seat pricing on a shared inbox punishes you for putting the whole team on it — which is the entire point of a shared inbox.
A good provider can point Meta's webhooks at your endpoint, so your software keeps working whatever happens to them. Ask whether that is possible at all.
Encrypted at rest and never sent to a browser. If nobody can answer this, nobody has thought about it. Ours is written down.
A customer who says STOP must be unreachable by every campaign, API call and bot afterwards — enforced in the server, not left to whoever builds the next campaign.
The technical part is minutes: onboarding runs through Meta's own signup flow and the number is live once the one-time verification is done. What takes longer is the part worth doing properly — your display name, your first message templates and your pipeline. Expect a working desk within a few days rather than months.
Yes, through Coexistence, and that is usually the right answer: your customers already have it saved and your chat history comes across. The alternative — a new number — means starting from zero in every customer's phone.
Because WhatsApp separates conversations a customer started from ones you started. Inside the service window you can write freely; outside it, you may only send a template Meta has approved. It is the mechanism that stops WhatsApp becoming SMS spam, and it is not negotiable by any provider.
A new number starts on a modest daily limit of business-initiated conversations and is raised by Meta as the number builds a history of good-quality sending. Software that paces sends inside that limit — rather than dumping a list and being throttled — is what keeps a number healthy.
Yes. Either send through an API from the system you already run, or have Meta's webhooks delivered straight to your own endpoint so the messages reach your software directly. Our API reference is public — your developer can read it before you buy anything.
Technically you can build against the Cloud API yourself; Meta does not force a middleman. In practice a provider is worth it for the inbox, the templates, the pacing, the reports and someone to call when a number gets flagged. What is not worth it is one that holds your account hostage or resells your messages.
Twenty minutes on a call, your number live through Meta's own signup, and your WhatsApp Business Account in your name — where it belongs.
By industry: travel · real estate · coworking · schools