Three different products carry the words “WhatsApp Business”, and the naming does a good job of hiding which one you need. People install the free app, hit a wall six months later, and discover that moving to the API means starting the phone number over.
It is worth ten minutes to get this right before you commit a number.
The three things called WhatsApp Business
1. The WhatsApp Business App
A free app you install on a phone. It gives you a business profile, a catalogue, quick replies, labels and away messages. It is a messaging app with a few shop features bolted on, and for a sole trader or a small shop it is genuinely enough.
2. The WhatsApp Business Platform (Cloud API)
Not an app. An API hosted by Meta that your software talks to. There is no inbox, no interface, no notification sound. It sends and receives messages and nothing else. What your team actually looks at is whatever you connect to it.
3. The On-Premises API
The older self-hosted version, which Meta has been retiring in favour of the Cloud API. Unless you have a specific reason and an existing deployment, this is not the one you want. Build on Cloud.
What actually differs
| Business App | Cloud API | |
|---|---|---|
| Cost | Free | Pay Meta per conversation or message |
| Interface | Built in | None – you supply it |
| Agents at once | One device, limited linked devices | As many as your software allows |
| Runs without a phone | No | Yes |
| Automation and bots | Canned replies only | Anything you can code |
| Connects to your CRM | No | Yes |
| Setup | Minutes | Business verification, app, software |
When the free app is the right answer
Most advice on this topic is written by companies selling API access, so it tends to skip this part. The free app is the correct choice when:
- One or two people handle every conversation
- Nobody needs to see who replied to what
- You are not sending notifications to people who have not messaged you first
- Conversations do not need to appear in any other system
If that describes you, stop here. You would be adding cost and complexity for capability you will not use.
The four walls people hit
Teams move to the API when one of these becomes painful, usually in this order:
The phone is the server. The Business App needs the handset to be on and connected. Flat battery, lost phone, or an employee who leaves with it in their pocket, and your support channel is down.
Two people cannot work the same inbox. Linked devices help a little, but there is no assignment, no internal notes, no way to see whether a colleague already answered. Two agents double-reply to the same customer.
No proactive messaging at scale. Order confirmations, delivery updates, appointment reminders – sending these one at a time by hand stops being viable fast.
The conversation is trapped. Nothing reaches your CRM, your order system, or your reporting. Customer history lives on one phone.
The part the API does not solve
This is the step most people miss when they budget. The Cloud API has no interface. Getting access does not give your team anywhere to read or answer messages. You have built a pipe, not an inbox.
So the real decision is two decisions:
- How you get API access
- What software your agents actually sit in front of
For the second, options range from commercial platforms charging per agent per month, to open-source tools you host yourself. We use Chatwoot, which is open source, supports WhatsApp alongside email and web chat in one inbox, and can run on a small server for the price of a coffee a month.
One warning about your phone number
A number registered on the Cloud API cannot also be used in the WhatsApp Business App, and a number currently active on WhatsApp has to have that account deleted before it can be registered on the API.
Deleting a WhatsApp account deletes its chat history. If the number you are planning to migrate is the one your customers already message, you lose that history in the move. Think about which number you want on the API before you print it anywhere.
Deciding
- One or two people, reactive support, no other systems – the free Business App. Revisit in a year.
- A team sharing an inbox, or notifications to send – Cloud API, plus software to sit on top of it.
- Already on the Business App and outgrowing it – plan the number migration before anything else. That is the part with no undo.
Pricing, messaging limits and verification requirements change regularly. Check Meta’s current documentation for figures rather than trusting any number quoted in a blog post, including ours.