Features Pricing Use cases Compare Blog
Sign in Start free

WhatsApp Business App vs API: Which One You Need

14 min read

The short answer

The WhatsApp Business app is free: one handset plus four linked devices, ten on a paid Meta subscription, and broadcast lists reaching only the 256 contacts who saved your number. The WhatsApp Business API has no interface — a platform supplies the inbox, any number of agents, and templates that reach anyone who consented. Coexistence runs both on one number.

The WabaCRM inbox in a demo workspace: a conversation list on the left with a search box, All, Unread, Mine and Unassigned filter tabs and an Available for new chats checkbox, and an open thread on the right with a banner stating how long free replies remain, an Unsubscribe button, a dropdown showing a team member's name, a Resolve button, inbound and outbound message bubbles, and a composer with attachment, emoji and lightning-bolt icons plus Send and Use template buttons.

What is the difference between the WhatsApp Business app and the WhatsApp Business API?

The WhatsApp Business app is a phone app. You install it, it holds your chats, and you answer them yourself. The WhatsApp Business API — delivered today as Meta's Cloud API — is not an app at all. It has no screen. It is a connection that a platform sits on top of, and the platform supplies the inbox, the campaigns and the reporting.

Most comparisons frame this as small business versus large business, which is how people who do not need the API end up buying one. The app is genuinely good, and for a one-person business it is the right answer.

Three published limits decide when it stops being the right answer: how many devices can answer, how many contacts fit in a broadcast list, and who actually receives one. For the platform side in full, read the WhatsApp Business API explained end to end.

What are the three WhatsApp products, and which is which?

WhatsApp Messenger is the consumer app. The WhatsApp Business app is the free app for small businesses — WhatsApp's own product page describes it as "built with the small business owner in mind" (source). The WhatsApp Business Platform is Meta's name for the API, and the Cloud API is the only version of it that still exists.

The WhatsApp consumer app, the free WhatsApp Business app and the WhatsApp Business Platform compared side by side.
Three separate products. Only the third one lets a team share a number.

That last point matters, because much of the internet still describes a choice between Cloud API and On-Premises API. There is none left to make: Meta's sunset notice states that "the final supported version of the On-Premise API client expired on October 23, 2025" and that On-Premises API "can't be used to send messages to WhatsApp users anymore" (source). A provider still selling an on-premises deployment has told you everything you need to know about them.

What you are comparing WhatsApp Business app WhatsApp Business Platform (Cloud API)
What it is An app on a phone Software with no interface, reached through a platform
What it costs Free to download and use Meta charges per template message delivered; non-template messages are free; the platform charges separately for software
People answering One phone plus up to four linked devices, or 10 on a paid Meta subscription No device ceiling — accounts and roles live in the platform
Assignment and permissions Chat assignment only on the paid multi-agent tier; no permissions, no reporting Assignment, per-person permissions, exportable history
Reaching someone who has not saved your number A broadcast list will not reach them An approved template reaches anyone who has consented
Sending in bulk Up to 256 contacts per broadcast list Up to 80 messages per second by default, with capacity upgrades available
Automation and integration Greeting messages and away messages Webhooks, chatbots, and sends triggered by your own systems
Limits Meta sets on volume A monthly broadcast limit is rolling out in some countries A new business portfolio starts at 250 unique recipients per moving 24 hours

Figures read from WhatsApp's Help Centre and Meta's developer documentation on 22 August 2026.

How many people can answer from the WhatsApp Business app?

More than the internet thinks, and this is the part most comparison articles have not updated. WhatsApp's Help Centre article on linked devices states that you can use "up to four linked devices and one phone at a time" (source).

There is a paid tier above that. WhatsApp's article on multi-agent raises the ceiling from four connected devices to 10, and adds assigning chats to agents and seeing which device or agent sent a message. It ties that ceiling to a Meta Verified or Meta One subscription, and carries its own warning that "the premium version of this feature may not be available to you yet" (source).

So the honest version of "the app is for one person" is: up to ten people, if you pay Meta a subscription and the feature has reached your market.

Going past four devices costs you something the same article states plainly and no vendor comparison repeats: "Accounts with more than 4 linked devices will only receive calls on the primary device." Buy the tier that lets ten people answer messages, and calls stop ringing anywhere but the original phone.

The catch is what those devices are not. They are devices, not seats. Below the paid tier there is no assignment rule, no permission model, no record you can report on and no customer history beside the chat.

Everything also hangs off one handset — WhatsApp states that linked devices "will log out if your phone is unused for over 14 days" — and creating or viewing broadcast lists on a linked device is listed as unsupported, so the one job you would want a laptop for is the one the laptop does not get. What a real team inbox does differently is the subject of how a shared WhatsApp inbox actually works.

How many people can a WhatsApp broadcast list actually reach?

Two numbers matter here, and the second is the detail almost every article omits.

The first is the cap. WhatsApp's Help Centre article on broadcast lists states that "you can include up to 256 contacts in each broadcast list", while letting you create as many separate lists as you like (source).

The second is a requirement on the recipient, not on you. The same article's first listed requirement is to "make sure all contacts in the broadcast list have saved your number in their address book", and it repeats the point as a note: "Only people who've added you to their phone's contacts will receive your broadcast message."

Its advice for a customer who is not receiving your broadcasts is to ask them to add you to their contacts, which is not a campaign anyone can run.

This is the failure that sends people looking for the API. You split 900 numbers across four lists, send, and a large share receive nothing — no bounce, no error, no list of who missed it. The send looks like it worked.

Two smaller constraints sit alongside: broadcast lists "aren't supported on Windows, Mac, or Web", and "people in some countries might see a monthly broadcast limit".

WhatsApp is also rolling out a paid in-app broadcast product, priced by each recipient's country code and "currently available in limited countries" (source). Whether it lifts the address-book requirement is not documented on any WhatsApp page we could find on 22 August 2026, so treat that as unknown rather than solved.

It does report how many people read and replied. Read the note underneath, though: WhatsApp says that figure "won't reflect recipients who have turned off read receipts" (source). That is WhatsApp's own reason why nobody — us included — can honestly quote you a WhatsApp open rate.

What can the WhatsApp Business API do that the app cannot?

Four things, and they are the only four worth paying for.

A real shared inbox. Any number of people on one number, with conversations assigned, permissions set per person, and a record of who said what and how quickly.

Reach beyond your saved contacts. Outside the 24-hour window you send an approved template to anyone who has consented, saved or not. Meta sets the mechanic out plainly: "when a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts", and "when the window closes, you can only send pre-approved template messages" (source).

The WabaCRM templates screen in a demo workspace, listing four message templates in a table with columns for name, category, language, number of variables and status; the statuses shown are Pending, Approved and Rejected, the rejected row carries a short reason underneath, each row has a Preview button, and Sync from Meta and New template buttons sit above the table next to a status filter.
Templates carry the approval status Meta returned for them, and only an approved one can be sent outside the 24-hour window.

Volume without hand-maintained lists. Meta's documentation states that business phone numbers "can send up to 80 messages per second by default, with capacity upgrades available" (source).

Everything you connect to it. Webhooks, an order confirmation fired by your own shop, a chatbot, a customer record beside the chat, exportable reporting. The app has none of it, by design.

What does each one actually cost?

The app is free to download and free for ordinary messaging; the multi-agent tier needs a Meta subscription. The API carries two separate bills, and confusing them is the most common budgeting mistake in this market: Meta charges for messages, and a platform charges for software.

Meta's per-message pricing has applied since 1 July 2025. Its pricing documentation states that "conversation-based pricing is deprecated" and "was replaced with per-message pricing on July 1, 2025" (source). That matters when you read anything else on this subject, because the widely repeated "1,000 free conversations per month" allowance no longer exists and is still printed on vendor pages dated 2026.

What Meta still makes free, until 1 October 2026: "all non-template messages are free" and "utility templates delivered within an open customer service window are free". Meta's non-template-messages documentation states both become chargeable per message from that date, with no volume tiers — see what changes on 1 October 2026. Free entry point windows, which "remain open for 72 hours", are unaffected. The full picture is in what is genuinely free on the API and what is not.

The software bill is where platforms differ most, usually through per-agent charges. WabaCRM is priced per 1,000 contacts, not per agent — ₹96 per 1,000 contacts a month, with the first 1,000 free and no expiry on that allowance.

One part no platform can remove: Meta's message fees are billed to your own card on your own WhatsApp Business Account, so you attach a payment method to Meta before your first template send. As a Meta-verified Tech Provider we are not permitted to resell those fees.

Do I need the WhatsApp Business API, or just the app?

Your situation Use Why
One person, answering their own phone Business app Free, immediate, nothing to set up. The API adds cost and a verification wait for no gain.
Two or three people, each with a device, low volume Business app Four linked devices covers it. Add the Meta subscription if you need chat assignment.
More than ten people need to answer API Ten devices is the app's documented ceiling, and it has no permissions or routing above it.
You need to reach customers who have not saved your number API A broadcast list silently skips them, and tells you nothing.
You send to more than a few hundred people at a time API 256 per list, maintained by hand, with no delivery reporting.
Messages must fire from your shop, CRM or booking system API The app has no integration surface at all.
You need to know who answered what, and how fast API The app keeps no agent-level history you can export.
You want to keep answering from your phone as you do now Coexistence Both at once — see the next section.
You are still testing whether WhatsApp works for you Business app Prove the channel first. Moving later costs you nothing you have built.

Can you run the WhatsApp Business app and the API on the same number?

Yes, and this is the option most comparison articles leave out. Meta calls it coexistence: the number stays registered in the WhatsApp Business app on the phone and connects to the Cloud API at the same time, with messages mirrored both ways. WabaCRM offers it as a connection option, so you can keep your number on your phone and still run a team inbox on it.

The trade is real, and Meta documents it. Throughput is fixed: numbers in use with both the WhatsApp Business app and Cloud API have, in Meta's words, "a fixed throughput of 20 mps" — a quarter of the ordinary default. The business "must use WhatsApp Business app version 2.24.17 or higher" (source).

Several things also switch off in the phone app. Meta's list is specific: "Broadcast lists will be disabled. Business will not be able to create new Broadcast lists. Existing Broadcast lists will become read-only." Disappearing messages "will be turned off for all individual (1:1) chats", and view once and live location messages are disabled for those same chats.

Groups are a separate case, and the distinction matters. Your group chats keep working on the handset — but Meta states that "group chats will not be synchronized", and its Groups API documentation records that groups are "not available for WhatsApp Business app phone numbers" (source). So groups stay on the phone and never appear in the shared inbox at all.

One thing no vendor page mentions: your new inbox may start empty. Meta permits a platform to synchronise messages "sent or received within 180 days of the time when the business was onboarded onto Cloud API", but each provider chooses whether to implement it.

WabaCRM deliberately does not, so past chats stay on the handset and the shared inbox begins from your next incoming message. Better said here than discovered on day one. The rest of the list is in exactly what stops working under coexistence.

What actually changes on day one after you move to the API?

You cannot broadcast to your whole list immediately. Meta's documentation states that "newly created business portfolios have a messaging limit of 250", defined as "the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period" (source).

It caps people, not messages, and rises to 2,000, then 10,000, 100,000 and Unlimited as you scale. That ladder is Meta's, not your platform's — the detail is in what actually caps how many people you can reach.

The WabaCRM WhatsApp numbers screen in a demo workspace, with a Connect a number card and green button at the top, a webhook callback URL field with a Copy button beneath it, and a connected number's card below showing Default and Connected badges, its quality rating, messaging tier, template count and when it was last checked, with Refresh, Sync templates, Auto-assign, Edit and Disconnect buttons and a collapsed Webhook details section.
A connected number's card shows the messaging tier and quality rating Meta reports for it — the rung on that ladder the number currently sits on.

Business verification is Meta's too, and takes days rather than an afternoon. Every message outside the 24-hour window has to be a template Meta has approved. And consent stops being a courtesy: a WhatsApp user can block or report a business from the chat itself, and your quality rating is built on signals you never see.

None of that argues against the API. It argues for moving at the point where the app has actually stopped working — which, on the numbers above, is a moment you can identify rather than guess at.

Every figure attributed to Meta's developer documentation was re-read there on 22 August 2026, and every figure attributed to WhatsApp's Help Centre was read from the article linked beside it the same day. Both change without notice; the linked pages are authoritative and this one is not.

Questions people also ask

Is the WhatsApp Business app free?

The app is free to download and free to use for ordinary messaging. Two things inside it are not. WhatsApp's multi-agent feature, which raises the connected-device ceiling from four to 10 and adds chat assignment, is tied to a Meta Verified or Meta One subscription. And WhatsApp has begun rolling out a paid in-app broadcast product in limited countries, priced by each recipient's country code. Checked on 22 August 2026.

Can two people use the WhatsApp Business app at the same time?

Yes. WhatsApp's Help Centre puts the ceiling at up to four linked devices and one phone at a time, and its multi-agent feature raises that to 10 devices on a Meta Verified or Meta One subscription. Those are devices, not seats in a shared inbox. Below the paid tier there is no chat assignment, no permission model and no reporting, and linked devices log out if the primary phone goes unused for over 14 days.

Why did my WhatsApp broadcast only reach some people?

Almost always because the rest have not saved your number. WhatsApp's broadcast list requirements begin by telling you to make sure all contacts in the list have saved your number in their address book, and the same article notes that only people who have added you to their phone's contacts will receive the broadcast. Nothing tells you who missed it. The second cause is the cap of 256 contacts per list.

Do I need the WhatsApp Business API if I only have 300 customers?

Probably not. If one person answers the phone and your customers already have your number saved, the free app does the job and the API adds cost and a verification wait for nothing. The deciding line is not customer count. It is whether a second person needs to answer the same number, whether you need to reach people who have not saved you, or whether messages must fire from another system.

Do I have to give up the WhatsApp Business app to move to the API?

Yes, through coexistence. The number stays live on the phone and mirrors into the Cloud API at the same time. Meta fixes throughput at 20 messages per second for such numbers, disables broadcast lists in the app, and turns off disappearing messages, view once and live location in one-to-one chats. Whether your past chats appear in the new inbox depends on the platform, not on Meta.

Keep reading

The WabaCRM WhatsApp numbers screen in a demo workspace: a Connect a number card at the top, a webhook callback URL field with a Copy button, and one connected number's card showing Default and Connected badges, Refresh, Sync templates, Auto-assign, Edit and Disconnect buttons, a quality rating, a messaging tier, a template count and when it was last checked.

Coexistence

WhatsApp Coexistence Limitations: What Stops Working

Every feature coexistence switches off, from Meta's own docs: broadcast lists, view once, the 20 mps cap, and the inactivity rule that disconnects you.

13 min read

The WabaCRM campaigns list in a demo workspace: a search box, a status filter and a New campaign button above three campaign rows in Scheduled, Sending and Completed states, each with a progress bar, a sent and read count against the audience size and a When column; the Sending row has Pause and Cancel buttons beside it.

Concepts

WhatsApp broadcast limits: what actually caps your reach

Four separate ceilings decide how many people a WhatsApp broadcast reaches: the 256-contact list, your messaging limit, throughput and quality rating.

11 min read

The WabaCRM WhatsApp numbers screen for a demo workspace: a Connect a number card with a green Connect a number button, a webhook callback URL field with a Copy button, and a connected number card marked Default and Connected that lists quality rating, messaging tier, template count and last-checked time alongside Refresh, Sync templates, Auto-assign, Edit and Disconnect buttons.

Concepts

WhatsApp BSP vs Tech Provider vs Solution Partner

Meta's partner documentation names Solution Partners, Tech Providers and Tech Partners — not BSPs. Only one of those tiers can bill you for messages.

11 min read

Your customers are already on WhatsApp

Free for your first 1,000 contacts, with no time limit and no card. Setting up the workspace takes minutes; connecting a number takes as long as Meta's own review of it.

Create your free workspace

Sign up with your company email address. No sales call, no onboarding fee, nothing to schedule.

Why this is safe to point your customer list at

Payments are processed by Razorpay on their own checkout — your card details are never entered on, or stored by, WabaCRM. Every inbound WhatsApp webhook is checked against its signature before it is trusted.

Tech Provider is a Meta platform access tier — not a partnership, a reseller agreement or an endorsement.