WhatsApp's technology is fine. Its rules are the problem.

When I built on it, a few years ago, you couldn't integrate directly unless you had a WhatsApp Business account, and getting one was a long, painful process. So we went through WATI, one of the official partners (Business Solution Providers) that sat between businesses and WhatsApp, and that helped us get approved. WATI wasn't bad and wasn't great: it got us live, and it added a layer and a bill. Once we were approved, the API itself was easy to use. A month after launch, with paying users, WhatsApp blocked the account without warning. Users complained, the appeal process was miserable, and we moved the whole product to Telegram.

Some things have changed since. Meta opened its Cloud API to every business in May 2022, and today you can start without verifying the business, but only up to 250 people a day, on a display name Meta still reviews. To grow past that, you either get the business verified with official documents (registration certificate, tax or bank records whose details match the application exactly, with up to three resubmissions if Meta rejects them) or prove 2,000 good-quality messages in 30 days. So you can integrate directly, and on AWS, End User Messaging Social connects WhatsApp to your account with no partner at all. A partner like WATI still earns its fee when non-developers need a shared inbox, a chatbot builder and broadcasts without code. It doesn't protect you from a ban.

What hasn't changed is the gatekeeping: business verification, display names reviewed by Meta, templates approved before you can start a conversation, daily limits that start at 250 people, and enforcement that can lock an account overnight. It's rigid and heavily policed. I understand why, on a network of 3 billion people, but it's nowhere near as easy to build on as Telegram, where nobody asks who you are. Plan for it as a compliance project, not an integration.

So I use WhatsApp when the users leave me no choice, which in Australia is often. Verify the business, get opt-in on your own site, keep the wording far from anything that looks like a scam, and always keep a second channel ready for the day the account goes dark.

Use it when

Your users are on WhatsApp and won't install anything else. In Australia that's most of them: about 16 million active users against 2 million on Telegram.
Notifications and support conversations that users opted in to, from a verified business.
On AWS: End User Messaging Social connects WhatsApp to your account directly, with no partner in the middle.

Don't use it when

Your audience is happy on Telegram: same job, a fraction of the rules.
A product whose AI assistant is the main thing it offers: since 15 January 2026, Meta's terms bar general-purpose AI chatbots from the platform.
Any offer that could read as "get paid to…": the policy forbids business models Meta judges misleading, and it enforces by blocking the account.

Pricing

Per message delivered, by category and the recipient's country. Marketing, utility and authentication templates are charged. Since 1 October 2026, replies inside the 24-hour window are free only for the first 1,000 a month per number, and utility templates inside the window are charged too. A partner such as WATI adds a monthly plan and, reportedly, a markup on Meta's fees.

In my words: what hurts

Approval, not technology, is the problem: business verification, display-name review, template approval, opt-in rules and messaging limits that start at 250 people a day.
Enforcement without warning: an account can be locked or disabled overnight, and appeals are slow, with no guarantee.

Gotchas, with fixes

Gotcha: A new business starts at 250 people a day. Launch to a big list and you hit the wall on day one.

Fix: Verify the business before launch, then ramp up: limits rise to 2,000, 10,000, 100,000 and unlimited as you use half of them with good quality.

Gotcha: You can open a conversation, or write after 24 hours of silence, only with an approved template.

Fix: Design the templates first and get them approved before you build the flow around them.

Gotcha: An account can be locked or disabled for policy reasons, and a partner like WATI can't appeal for you.

Fix: Subscribe to the account_update webhook, keep a fallback channel ready (SMS, email or Telegram), and appeal yourself in Business Support Home.

Gotcha: Since 1 October 2026, a bot that only replies is no longer free beyond 1,000 messages a month per number, and delivery stops without a payment method on file.

Fix: Budget the replies, and put a card on the account before launch.

Provisioning

No provider · No Terraform provider

Accounts, numbers, display names and templates are set up and approved in Meta's dashboards, not provisioned.

Instead, consider

Telegram Bot API Your users will install it: no approval, no per-message fees, a direct API.
Amazon SES Notifications that don't need a conversation: email, with no platform that can switch you off.

Worked examples

WhatsApp or Telegram

Where it fits

A bot users message: Pick 02.
When your users are only on WhatsApp. Verify the business first, and plan the templates and the opt-in.

Sources

Last reviewed 22 October 2026 by Nicolas Dao

WhatsApp Business Platform