There are three ways to use WhatsApp for business, and they are frequently confused — including by people selling the more expensive one.
Getting this wrong is costly in a specific way: the most common route to needing the API is having your number restricted while using something else.
The three options
Personal WhatsApp. What is on your phone. No business features. Fine for a sole trader with a handful of conversations, and genuinely fine — do not let anyone tell you otherwise if that is where you are.
WhatsApp Business app. Free, still runs on one phone. Adds a business profile, a product catalogue, quick replies, labels and away messages. For most small businesses this is the correct answer and the story ends here.
WhatsApp Business Platform (Cloud API). No phone required — it runs on servers. Multiple agents can work the same number, it connects to a CRM, and it supports template messages at volume. It costs money per conversation and it takes real setup.
The line between them
You need the API when one of these is true:
- More than one person needs to answer the same number at the same time
- You need conversations logged against records in another system
- You need to message more than a handful of people at once, reliably
- You need chatbot handling or automatic routing before a human picks up
- You have already had sending limits imposed or a number restricted
If none of those apply, the Business app is not a compromise. It is the right tool, and moving to the API will add cost and complexity for no gain.
The banning problem
The most common way businesses end up on the API is unpleasant. They use the Business app to broadcast to a few hundred contacts, recipients report the messages, the quality rating drops, sending limits are cut, and eventually the number is restricted.
That number is often printed on vehicles, business cards and every listing. Losing it is a real cost.
The broadcast rules that actually matter:
- People must have opted in, meaningfully
- The first message should be relevant to why they gave you their number
- Every message needs an obvious way to stop
- Send in segments, not to your entire list at once
These apply on the API too. The API does not make broadcasting safe; it makes it measurable, and it gives you a quality rating you can watch before things go wrong.
What the API setup actually involves
It is more work than most people expect, and worth knowing before you commit:
- Meta Business verification, which requires real company documents
- A phone number not currently registered to WhatsApp, or one migrated off it
- Display name approval, which can be rejected for reasons that seem arbitrary
- Message templates submitted for review, per template, per language
- A platform or integration to actually send and receive
The template review step is where most projects stall. Templates get rejected for being too promotional, too vague, or for using variables in ways the reviewer does not like. Writing them to pass first time is a skill, and rewriting one that failed without knowing why is frustrating.
The green tick is not what you think
Business verification and the verified badge are separate things. Verification is required to use the API at any scale. The green tick is a brand-recognition decision Meta makes, and most businesses will not get it regardless of how legitimate they are.
Do not let anyone sell you the API on the promise of a green tick.
Cost
You are billed per conversation window, not per message, and the rate varies by country and by whether you or the customer started it. Customer-initiated conversations are cheaper. Marketing conversations are the most expensive.
For most businesses moving from the Business app, the monthly bill is modest — but it is not free, and it scales with volume, which the free app did not.
The honest recommendation
If you are one person answering messages, stay on the Business app.
If you have a team sharing a number, or you are sending to a list and worrying about it, move to the API before something breaks rather than after. Migrating a restricted number is considerably harder than migrating a healthy one.
If you are not sure which side of the line you are on, count two things: how many people need to answer, and how many outbound messages you send in a normal week. Those two numbers decide it.
