WhatsApp decision tool
WhatsApp Automation Fit: Business App or Cloud API?
Three products share the WhatsApp name and only one of them fits how you work. Answer what applies to you and get a straight recommendation—with the reason it came out that way.
Nothing is sent anywhere. The result is worked out in your browser and shown in full, with no email asked for.
13 questions in total — the last two only appear if they apply to you.
Volume and team
How much conversation you handle, and who handles it.
What actually differs between the three
Three different products share the WhatsApp name, and most of the confusion comes from treating them as tiers of one thing. They are not: the Business app is not a smaller API, and no amount of growth turns it into one. These are the lines that decide which you need.
| Capability | WhatsApp (consumer) | WhatsApp Business app | Business Platform (Cloud API) |
|---|---|---|---|
| People answering one number | One person, on their phone | One phone plus a handful of linked devices | As many as the inbox software on top allows |
| Messaging people who have not saved your number | No | No — broadcast lists only reach contacts who have you saved | Yes, using approved message templates |
| Scheduled and event-triggered messages | No | No | Yes, using approved message templates |
| Connecting to your CRM or other systems | No | No official path — the gateways that claim otherwise risk your number | Yes: it is an API, with webhooks for incoming messages |
| Automated replies | None | Greeting and away messages, quick replies | Anything you build, from menus to an AI agent |
| Reporting and audit trail | None | Almost none, and nothing you can export | Yes, through the platform you connect |
| Cost | Free | Free | Paid per message, plus whatever software sits on top |
| What you need before starting | A phone number | A phone number | Meta Business verification, and a number not already tied to the Business app |
How this questionnaire decides
It is not a score. Six of the answers are hard limits of the Business app rather than matters of degree, and any one of them sends you to the platform no matter how small your volume is. Everything else only decides how soon.
- Volume and team
Start with how many conversations you handle and how many people answer them. Team size is the limit people hit first: the Business app is built around one phone, so a number several people share is already stretched past what it was designed for.
- Outbound and campaigns
Replying to messages is easy on any of the three. Starting conversations is where they diverge — especially reaching people who have not saved your number, which broadcast lists cannot do. Click-to-WhatsApp Ads are the common exception to the rule: they work with the Business app too, so the ads alone do not force a migration. What forces it is what you want to happen after the click.
- Automation
Greeting and away messages are as far as the Business app goes. Anything that branches, qualifies, or reads what the customer wrote needs the platform — and if you want an agent that understands the question rather than matching a keyword, that is AI automation, not an auto-reply.
- Operations and constraints
The last step is what makes the recommendation real: reporting, Meta Business verification, and whether the cost of per-message pricing is one you want to carry. If a hard requirement showed up earlier, this is also where the tool asks whether your number is already registered in the Business app — that one decides whether you have a migration ahead of you.
If the answer is the Cloud API
The platform is an API, which means incoming messages arrive as webhooks rather than notifications on a phone — worth understanding how webhook delivery works before you scope the build. Connecting it to a CRM is a normal integration with normal failure modes, so run it against the integration checklist first, and design for the messages that do not go through: failure-ready automations covers what to do with a delivery that fails at 2am. If the reason you are here is that inbound enquiries sit unanswered too long, the mechanics are the same ones behind this lead response automation.
WhatsApp automation FAQ
- What is the real difference between the WhatsApp Business app and the Cloud API?
- They are two different products, not two sizes of the same one. The Business app is a phone app: one number, one phone plus a few linked devices, greetings and away messages, quick replies, labels and a catalog. The Cloud API is infrastructure: no interface of its own, but it can be connected to your systems, send templates to people who have never saved your number, and sit underneath a shared inbox that a whole team works from. Growing does not turn the app into the API — you migrate, or you do not.
- Do Click-to-WhatsApp Ads require the Cloud API?
- No, and this is the most common misunderstanding. A Click-to-WhatsApp ad can open a chat with a number running on the Business app perfectly well. What pushes you toward the API is what you want to happen after the click: qualifying the lead automatically, routing it to the right person, or writing it into a CRM. If a human is going to read every conversation anyway, the ads alone are not a reason to migrate.
- Can I keep my phone number when I move to the Cloud API?
- Yes, but it has to be migrated, because a number cannot be active in the Business app and on the platform at the same time. The part that surprises people is that the chat history stored in the app does not travel with it. Export or archive anything you need to keep before you start, and plan the switch for a quiet window rather than the middle of a campaign.
- Can I connect the WhatsApp Business app to my CRM?
- Not through any official route. Services that advertise this work by driving the app the way a person would, which is against WhatsApp's terms, and the usual outcome is the number being banned — taking the conversation history with it. If WhatsApp genuinely needs to exchange data with another system, that requirement alone is enough to justify the platform.
- How many people can answer from the same number?
- On the Business app, one phone holds the account and a small number of linked devices can work alongside it, which stretches to a couple of people sharing a shift and no further. On the platform there is no such limit: the number of people who can work the same number is decided by the inbox software you connect on top of the API, not by WhatsApp.
- Is the Cloud API free?
- The hosting is provided by Meta, but the messages are charged, and there is normally a second cost for whatever software you connect on top to give your team an interface. If your requirement is that WhatsApp stays free, that is a real constraint and it points at the Business app. Just be clear about what it buys you: the free path cannot do integrations, templates to unsaved contacts, or scheduled sends at any volume.
- What do I need before I can start with the platform?
- Meta Business verification for the business itself, and a phone number that is not already tied to the Business app. Verification is the step that decides your timeline more than anything technical does, so start it early — and if the business cannot be verified, the honest conclusion is that this path stays closed until it can.