WhatsApp Business App vs the Cloud API: which one does your business need?

Almost every business that outgrows WhatsApp asks the same question, and almost every answer online is written by someone selling the more expensive option. So let us start with the part vendors tend to skip: most small businesses do not need the API, and moving to it too early makes daily work harder, not easier.

Here is how to tell which side of the line you are on.

What each one actually is

The WhatsApp Business App is a free phone app. It is a WhatsApp account with a catalogue, quick replies, labels and away messages bolted on. It runs on one phone, and you can link a handful of additional devices to the same account.

The WhatsApp Business Platform — what people mean by "the API" — is not an app at all. There is no interface. It is a programming interface that Meta hosts, and it does nothing on its own. You point it at a system that can send and receive messages, and that system becomes your inbox. Without software on the other end, the API is an unusable phone number.

This is the single most common misunderstanding. Businesses apply for API access expecting a better app and receive a set of credentials instead.

The decision, in one table

Question	Business App	Cloud API
How many people can reply at once?	Realistically one, awkwardly a few	Your whole team, in parallel
Can two agents avoid answering the same chat?	No	Yes — assignment and status
Automated replies	Away message and greeting only	Anything you can program
Does chat history survive a lost phone?	Only via backup	Yes, it lives in your system
Cost	Free	Per-message fees, plus software
Setup effort	Ten minutes	Days, including Meta review
Send to a list of customers	Broadcast lists, capped and manual	Yes, with approved templates

Four signs you have outgrown the free app

1. Two people are fighting over one phone. This is the clearest signal. The moment replying is a rota rather than a job, the app is the bottleneck.
2. You are losing chats. Nobody can tell which conversations were answered, so some are answered twice and some never.
3. The phone is a single point of failure. If the person holding it is on leave, your customer service stops.
4. You want to message customers first. Broadcast lists only reach people who have saved your number, which in practice is a small fraction of your customers.

If none of these describe you, stay on the free app. Genuinely. You will spend money and weeks of approval time to solve a problem you do not have.

What moving to the API actually involves

Expect four things, roughly in this order:

• A Meta Business account, with your business verified. This wants real documents — trade licence, proof of address, a matching website.
• A phone number that is not currently on WhatsApp. This trips people constantly: a number already registered on the Business App must be deleted from it first, and that deletes its chat history. Many businesses move to the API on a new number for exactly this reason.
• A display name that survives review. Meta checks it matches your actual business.
• Software to connect it to. The API is plumbing; the inbox is a separate decision.

The rule that surprises everyone: the 24-hour window

Once you are on the API, you cannot simply message whoever you like. When a customer messages you, a 24-hour customer service window opens, and inside it you may reply freely, in your own words, as many times as the conversation needs.

Outside that window, free-form messages will not deliver. You may only send a template — a message whose wording Meta approved in advance. Templates fall into Marketing, Utility and Authentication categories, and they are priced differently, with marketing the most expensive.

The practical consequence is that your first reply matters twice over. Answer within the day and the conversation costs you nothing extra. Answer three days later and you are paying for a template just to restart it.

What it costs

Meta charges per message for templates, at rates that vary considerably by country — a marketing template to a customer in India and one in the UAE are not close in price. Meta has also revised this pricing model more than once. Rather than quote a figure that will be wrong by the time you read this, check Meta's current rate card for the countries you actually message.

Budget for two line items, not one: what Meta charges for messages, and what your inbox software charges. They are unrelated.

Choosing the software, not just the API

Since the API does nothing alone, the software is the decision that determines your daily experience. Worth asking:

• Can several numbers live in one workspace, with replies going out from whichever number the customer wrote to?
• When someone leaves, can you cut their access without changing a shared password?
• Does the chat history belong to you, exportable, or is it hostage to the subscription?
• Does it handle template submission, or leave you in Meta's interface?

That last one matters more than it sounds. Template rejection is the most common reason a WhatsApp rollout stalls.

In short

Stay on the free app while one person can comfortably answer everything. Move to the Cloud API when the constraint is your team rather than your phone — and when you move, choose the inbox before you chase the credentials.