"WhatsApp Business" has become the name of two very different things. One is the free app you download from the app store. The other is the WhatsApp API, which Meta calls the WhatsApp Business Platform, used by systems and customer service platforms. Picking between them decides what you pay, how many people can answer and what you can automate.
Summary table
| WhatsApp Business app | WhatsApp API (official) | |
|---|---|---|
| Cost | Free | Per template message, plus your provider |
| How you use it | On your phone, plus linked devices | Through a system or platform |
| Agents | You and a few linked devices | As many as the system allows |
| Automation | Greeting, away message, quick replies | Anything, through code or a platform |
| Starting conversations at scale | Not built for it | Yes, with approved templates |
| Groups | Yes, like regular WhatsApp | Limited and newer |
| Verification badge | Meta Verified, paid | Available for verified businesses |
The WhatsApp Business app
The app is regular WhatsApp with business tools: a business profile with address and hours, a catalog, labels to organize chats, and three simple automations (greeting message, away message and quick replies). The away message setup is in WhatsApp away message.
Pros: it's free, you keep your usual number, it works in groups and you can start in minutes.
Limits: the account lives on the main phone, with a few linked devices (computer, tablet, a second phone). The standard limit is four linked devices alongside the main phone (WhatsApp blog), and Meta Verified packages raise it for some businesses. The free plan has no queue and no assigning chats to agents, and the automations don't read what the customer wrote.
Good for: freelancers, local businesses, small teams and anyone who handles customers from a phone.
The WhatsApp API
The WhatsApp Business Platform is the official way for a system to send and receive messages. You don't use it through an app. You use it through a platform (Twilio, Gupshup, 360dialog, Wati, respond.io and many others) or directly through Meta's Cloud API if you have someone to write the code.
How pricing works: since July 1, 2025, Meta charges per delivered template message, split by category (marketing, utility, authentication). When the customer writes to you, a customer service window opens in which free-form replies are not charged, according to Meta's pricing page. Your provider adds its own monthly fee or markup.
Pros: many agents on one number, integration with your CRM and other systems, chatbots and AI without the risk of running an unofficial client, and outbound messaging at scale to people who opted in.
Limits: you pay per message, starting a conversation requires approved templates, the number has to be registered on the platform, and group support is much more restricted than in the app.
Good for: businesses with volume, support teams, e-commerce, and anyone who needs to send notices and reminders at scale. If you're shopping for a provider, see Twilio WhatsApp alternatives and Wati alternatives.
The middle path: unofficial connections
There is a third route that developers use a lot: connecting a system to WhatsApp as if it were one more linked device, the same way WhatsApp Web works. That's how Evolution API, WAHA, Z-API and libraries such as Baileys operate.
It combines the best of both (your own number, groups, no per-message cost, free-form automation) with a real risk: WhatsApp's terms don't authorize this kind of client, and bulk sending through it gets numbers banned. We compare the options in open-source WhatsApp APIs and best WhatsApp APIs.
How to decide
Answer in order and stop at the first yes:
- Do you need to message lots of people first? (reminders, notices, campaigns) Go with the official API.
- Do more than three people answer the same number at the same time? Official API with a customer service platform. More on that in one WhatsApp number, multiple users.
- Does your support happen inside client groups? The app, or a tool that connects to the app, because the API still handles groups poorly.
- Do you work alone or with one other person, only answering people who reach out? The app is enough, and some automation on top helps with volume.
Can I switch later?
From app to API, yes. The number has to be registered on the platform, and the app's chat history does not move into the new system. That's why it pays to export or back up your history before migrating.
FAQ
Can I use the same number in the app and the API at the same time? Not in the traditional setup. Registering the number on the API stops it working in the app. Meta has been rolling out "coexistence" for some cases, so check with your provider before migrating.
Is the WhatsApp API paid even for replies? Replying inside the customer service window, which opens when the customer writes, is not charged by Meta. What you pay for are template messages, used to start a conversation or outside the window. Your provider may charge its own fee.
Do I need a registered company for the API? Meta asks for a verified business in Business Manager to unlock all features. To start testing, the Cloud API gives you a test number.
Where WACrew fits
WACrew is an open-source agent that connects to your app number as one more linked device, through Baileys. It was built for case 3 above: people who support clients in groups and want a queue sorted by wait time, voice note transcription and AI-written replies reviewed before they go out. Because it doesn't use the official API, it's for answering people who already talk to you, never for bulk sending. The code is on GitHub.



