
Table of Contents
ToggleThe most important question when choosing a WhatsApp provider is no longer about features or price. It is about ownership, because a business phone number can no longer simply be migrated away from one account to another.
Per Meta’s WhatsApp Business Platform changelog of 18 August 2026, phone number migration is not supported for accounts on the new WhatsApp account model. The request is rejected unless the destination account already owns the number, and disconnecting the number does not make it available. That single change reshapes how to choose a WhatsApp BSP.
The exit question used to be easy. If you left a provider, you migrated your number out. Now that door is mostly closed, so the question moves to the front of the process.
The documented alternative is account sharing. The provider that owns the WhatsApp account shares it with you, which gives access without moving the number. So how to choose a WhatsApp BSP now starts with who will own the account and the number. If you are still weighing a BSP against running the Cloud API yourself, that decision is in WhatsApp Cloud API vs BSP.
This is the group that protects you later. Ask it before anything else, because it decides whether you can ever walk away cleanly. Getting ownership right is the core of how to choose a WhatsApp BSP today.
Meta’s changelog of 29 August 2026 also confirms a WhatsApp account is linked to exactly one business phone number, and messaging_account_id selects the messaging account when a token can reach more than one on the same number. If you run several brands, the structure is in multi-tenant WhatsApp Cloud API.
If you run ads, the referral data from the first message is your attribution. Providers handle it differently, and the difference decides whether you can track sales.
Meta states that Click-to-WhatsApp advertisers must support business-scoped user IDs. With usernames live, contacts can also arrive without a phone number, so the provider must handle both.
Onboarding has changed recently, so the flow a provider uses tells you how current they are. Embedded Signup v2 reaches its deprecation date on 8 October 2026.
Meta’s v4 Phone Number First flow, described on 3 September 2026, enters Coexistence automatically when the number is already in use with the WhatsApp Business app and Coexistence is enabled.
The last group is the everyday experience. It rarely shows up in a demo, so ask directly.
Sitting in on this choice, writing the shortlist questions and reading the answers with you, is the kind of work I take on as a service. The ownership and tracking questions are where most businesses get locked in later, so they are worth getting right before you sign. That is really what how to choose a WhatsApp BSP comes down to now.
See the WhatsApp CRM and Cloud API service
Ownership. Since phone number migration is not supported on the new account model, who owns the WhatsApp account and number decides whether you can leave cleanly.
Not by migration on the new account model. The documented route is account sharing, where the owner shares the account instead of moving the number.
Confirm the provider passes Meta’s referral data or lets you forward webhooks, and agree who sends the Conversions API events before you sign up.
Meta requires Click-to-WhatsApp advertisers to support them, and contacts can arrive without a phone number, so the provider has to handle BSUIDs properly.
A current one. Embedded Signup v2 reaches its deprecation date on 8 October 2026, and newer flows handle Coexistence automatically.
Price matters, but ownership, tracking and data export decide whether the choice holds up over time. The pricing mechanics are a separate question.