WhatsApp Business app vs the API: which one you need, and what happens to your number

Most businesses start on the free WhatsApp Business app. At some point they want something the app can't do: send to a list, plug in a website or a CRM, share one number across a team, or let an AI assistant draft the messages. That means the WhatsApp Business Platform (the Cloud API), and the first question is always the same: what happens to my number and my chats?

This guide answers that. SendFromChat is independent and not affiliated with Meta or WhatsApp.

The short version

• The app is a phone app for one business, run by hand. Free, no setup.
• The API is how software sends and receives WhatsApp messages. You pay Meta per template message, and you need something on top of it (a dashboard, your own code, or a tool like SendFromChat).
• A number normally lives in one place. To use it on the API you either move it off the app, or use Meta's coexistence option, which keeps both (rules below).

What each one is good for

	WhatsApp Business app	WhatsApp Business Platform (API)
Who uses it	You, on a phone (plus linked devices)	Software: a dashboard, your app, an AI assistant
Sending to a list	Manual, one chat at a time	Template messages to a contact list, in bulk
Integrations	None	Your website, shop, CRM, webhooks
Team inbox	Limited	Shared inbox in the tool you connect
Automation	Basic quick replies and away messages	Chatbot flows, sequences, AI assistants
Cost to you	Free	Meta charges per template message (pricing guide) plus your tool
Setup	Minutes	A Meta business account and a connected number

Stay on the app if you handle a few chats a day, one person answers them, and you never message people first. Move to the API when you need to send to many people, connect another system, or give a team a shared inbox.

Two rules that change when you move to the API

1. The 24-hour window. On the API, you can reply freely for 24 hours after a customer writes. After that you need an approved template (how the window works, template rules). For numbers that use both the app and the API (coexistence, below), Meta's documentation says the 24-hour window applies only to Cloud API messages.

2. Consent matters more. Bulk sending to people who never asked for it gets numbers restricted. See bulk messaging without getting banned.

What happens to your number

There are two routes.

Route A: move the number to the API

A number that is registered on the WhatsApp or Business app can't also be registered with the Cloud API in the normal way. In practice you either use a new number for the API (the simplest, and the one we suggest if you can), or you move your existing number over, which means taking it off the app. Moving it off the app means you stop using that number in the app. We have not found a Meta page that promises your chat history moves with it, so export anything you need to keep first.

Our Cloud API setup guide says the same: the real number must not be registered on the app at the same time.

Route B: coexistence (keep the app and add the API)

Meta has a feature for businesses already on the Business app: connect the existing number to the Cloud API and keep using the app. Details below are from Meta's developer documentation, "Onboarding WhatsApp Business app users", read 19 October 2026:

• The business needs WhatsApp Business app version 2.24.17 or higher.
• Contacts and message history are synchronised when you connect. Meta says you have 24 hours to synchronise the history.
• A number used with both the app and the Cloud API has a fixed throughput of 20 messages per second.
• Not supported: group chats are not synchronised, and voice and video calls, broadcast lists and disappearing messages are not supported.
• Linked companion devices work, except WhatsApp for Windows and WearOS, which are unsupported.
• Billing: Cloud API messages are billed at Cloud API rates. Messages sent from the app stay free.
• The disconnect rules include the primary phone being inactive for about 14 days, so keep the app in use.

Unchecked: whether coexistence is available in your country. Meta's page we read has no country list, and we could not confirm availability for the EU, EEA or UK from a primary source. You will find out at connection time, so check before you plan around it. SendFromChat's connection flow does not include a coexistence option today (checked in our code on 19 Oct 2026), so treat this route as Meta's option, not something we offer.

Which route to choose

• You can use a new number for automation: use Route A with the new number and keep your old number on the app for personal chats with customers. No migration risk.
• Your customers know your current number and you want to keep chatting by hand: look at coexistence, and check eligibility for your country first.
• You don't need the API: stay on the app.

Where SendFromChat fits

SendFromChat is software for the WhatsApp Business Platform. You connect a number with Continue with Facebook in Facebook's own window, which usually takes a few minutes, with no developer setup. After that you can run it three ways:

• Ask an AI assistant such as Claude or ChatGPT (how it works).
• Use the web dashboard, with a shared inbox that shows whether the 24-hour window is open.
• Call the REST API from your own app (docs).

Plans start at $19 a month. The 30-day free trial needs no card. Meta's message charges are billed by Meta to your WhatsApp Business account and are separate. For European setups see WhatsApp Business API in Europe.

Start free for 30 days

Sources: Meta for Developers, "Onboarding WhatsApp Business app users", read 19 October 2026. Meta's rules change; confirm current details on developers.facebook.com before you migrate a live number.