
Table of Contents
ToggleThe WhatsApp Cloud API vs BSP choice comes down to how much you want to build versus buy. A BSP gives you a ready-made inbox and tools for a recurring fee. The Cloud API wired into your own system gives you full control and no per-seat cost, with the trade-off of building it. Coexistence lets you keep the WhatsApp Business app on the same number while an API connects alongside it.
A WhatsApp Business Solution Provider is a company that packages the WhatsApp Business Platform into a ready-made product: a shared inbox, agent seats, templates, automation and support. You are still sending through Meta underneath, so Meta’s per message charges apply as normal. On top of that, many BSPs add their own monthly plan fee or a markup on each message, which is the cost of not having to build anything yourself.
Going direct on the Cloud API fits when you want custom workflows, your own data, and tight links into a CRM or internal tools. There are no per-seat fees, and you can serve several businesses from one setup. The trade-off is that someone has to build and maintain it. This is the part I handle: a WhatsApp CRM and Cloud API setup built around your own system, so you own the data and the workflows. The running cost side is covered in WhatsApp Business API pricing.
WhatsApp coexistence lets a business keep using the WhatsApp Business app while an app connects the Cloud API on the same number, with messaging history kept in sync between the two. The business customer needs WhatsApp Business app version 2.24.17 or higher, and onboarding goes through a Tech Provider or Solution Partner using Embedded Signup. If the business agrees, the most recent six months of one-to-one chat history can be synced. Group chats are not synced.
Coexistence is convenient, but it changes the Business app. After onboarding, existing broadcast lists become read-only and new ones cannot be created, voice and video calls are not supported through the API, and companion or linked devices are unlinked so only the primary device stays connected. A number used this way also has a fixed throughput of 20 messages per second. None of this breaks day-to-day chatting, but it is worth knowing before you connect a number you rely on.
The honest answer has changed. On the new WhatsApp account model, Meta no longer supports migrating a phone number away from the account that owns it, so you cannot count on moving the number out of a BSP later. That does not mean every business is trapped.
Your exit is decided on day one, by whose business portfolio the WhatsApp account sits in. If the account is in your own portfolio with the provider added as a partner, you stay in control, and access is given or removed through account sharing rather than by moving the number. The dated rules are kept on the Meta business messaging changes reference, and what to ask a provider before you sign is in how to choose a WhatsApp BSP. Getting approved on the platform is the WhatsApp business verification step, and if you run several brands, the multi-tenant WhatsApp Cloud API guide covers keeping them in one portfolio.
| BSP platform | Direct Cloud API | Coexistence | |
|---|---|---|---|
| Setup effort | Low, ready to use | Higher, built for you | Low, connect existing number |
| Monthly cost type | Plan fee or markup on Meta’s price | Meta’s message price, no per-seat fee | Meta’s message price, through a provider |
| Control over data | Lives in the provider’s tool | Fully your own | Shared between app and API |
| Custom features | What the plan offers | Anything you build | Limited by Business app changes |
| Who it suits | Teams who want it working today | Teams who want control and scale | A business keeping its current number and app |
There is no single right answer in the WhatsApp Cloud API vs BSP decision. A BSP is the fastest way to start, a direct Cloud API build gives you the most control, and coexistence is the gentlest first step on a number you already use. Meta documents the coexistence rules on its onboarding Business app users page, and the message charges on its WhatsApp pricing page.
Meta’s per message price is the same either way. A BSP often adds its own plan fee or markup, while a direct Cloud API setup has no per-seat fee but does carry build and maintenance. Which is cheaper depends on your volume and how much you would otherwise pay in seats.
Yes. Through coexistence you can keep your number and the WhatsApp Business app while connecting the Cloud API, as long as you meet the version and onboarding requirements.
With coexistence, the most recent six months of one-to-one history can sync if you agree to it. Group chats do not sync, so treat those as not carried over.
Not exactly. On the new account model you cannot rely on migrating the number away from a BSP later, so the exit is decided by whose business portfolio the WhatsApp account sits in. Keep it in your own portfolio and you change providers through account sharing, not by moving the number.
A direct Cloud API setup in one business portfolio scales across several businesses without per-seat fees. Keeping the accounts in one portfolio is what the multi-tenant setup is for.
Yes. Getting your business approved on the WhatsApp Business Platform comes first, whichever route you then choose.