Three options, frequently confused — including by people selling the expensive one.
Personal WhatsApp. What is on your phone. Fine for a sole trader, and genuinely fine.
WhatsApp Business app. Free, one phone. Business profile, catalogue, quick replies, labels, away messages. For most small businesses this is the correct answer and the story ends here.
WhatsApp Business Platform (Cloud API). Runs on servers, not a phone. Multiple agents on one number, CRM integration, template messages at volume. Costs money per conversation and takes real setup.
When you actually need the API
Only when one of these is true:
- more than one person must answer the same number at the same time
- conversations need to be logged against records in another system
- you need to message more than a handful of people at once, reliably
- you need routing or a bot before a human picks up
- you have already had sending limits imposed
If none apply, the Business app is not a compromise. Moving to the API adds cost and complexity for no gain.
The failure mode that forces the upgrade
The most common route to needing the API is unpleasant: a business broadcasts to a few hundred contacts from the Business app, recipients report it, the quality rating drops, sending limits are cut, and eventually the number is restricted.
That number is on your vehicles, cards and every listing. Losing it is a real cost.
The rules that matter, on either platform:
- people must have opted in, meaningfully
- the first message should relate to why they gave you the number
- every message needs an obvious way to stop
- send in segments, not to the whole list at once
The API does not make broadcasting safe. It makes it measurable, and gives you a quality rating you can watch before things go wrong.
What setting it up involves
More than most people expect:
- Meta Business verification, which needs real company documents
- a phone number not currently registered to WhatsApp, or migrated off it
- display name approval, which can be rejected for opaque reasons
- message templates submitted for review, per template, per language
- a platform or integration to send and receive
Template review is where projects stall. Rejections come for being too promotional, too vague, or for variable placement the reviewer dislikes. Writing them to pass first time is a skill.
Integration is the part that pays
Getting connected is not the goal. The goal is that a conversation is attached to a lead.
In practice that means a webhook receiving inbound messages, matching the sender against your CRM by phone number, and appending to that record. Outbound sends log the same way. The result: whoever picks up the conversation next can see what was already said, and nothing lives only on one phone.
Without that, the API is an expensive way to do what the free app already did.
The green tick
Business verification and the verified badge are different things. Verification is required to use the API. The green tick is a brand-recognition decision Meta makes, and most businesses will not get it regardless of legitimacy.
Do not let anyone sell you the API on the promise of a tick.
Cost
Billed per 24-hour conversation window, not per message, varying by country and by who started it. Customer-initiated is cheaper; marketing is dearest. For most businesses moving up from the free app the monthly bill is modest — but it scales with volume, which the app did not.
