How to choose a WhatsApp BSP checklist showing ownership, tracking and onboarding questions for a provider

How to Choose a WhatsApp BSP: 5 Essential Questions Before You Commit

The 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.

What changed about 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.

Who owns the WhatsApp account, and what happens if you leave?

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.

  • Whose business portfolio will my WhatsApp account and phone number sit in, mine or yours? A good answer puts the account in your own business portfolio, with the provider added as a partner.
  • If I leave, do I keep the number and the account, or does it stay with you? A good answer is that the account is yours and you simply remove their access.
  • Since numbers cannot be migrated on the new account model, how would an exit actually work? A good answer names account sharing and access removal, not a migration promise they cannot keep.
  • Will you share the account that owns the number, or ask me to share mine? A good answer matches who you want holding ownership long term.

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.

What does the provider do with your Click-to-WhatsApp ad data?

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.

  • Do you pass Meta’s raw referral object from the inbound webhook, or rename its fields? A good answer gives you the raw object, or documents exactly how fields are renamed.
  • Can I forward webhooks to my own endpoint so I keep the ad click ID? A good answer is yes, with a clear setup path.
  • Do you send Conversions API events yourselves, or hand me the data to send? A good answer is whichever you need, stated plainly, not a vague “it is handled.”
  • Which Conversions API event names do you support? A good answer lists the events, not just “purchases.”

How does the provider handle business-scoped user IDs and missing phone numbers?

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.

  • Do you expose the BSUID fields such as user_id and from_user_id in the data I receive? A good answer is yes, as first-class fields.
  • How do you handle a contact that arrives with no phone number? A good answer keeps the BSUID as the contact key rather than creating a duplicate.
  • Do you capture previous_user_id when a user’s BSUID changes? A good answer links the old and new record so history is not lost.

Which Embedded Signup flow do you use, and how is Coexistence handled?

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.

  • Which Embedded Signup version do you onboard with? A good answer is a current flow, not v2 after its deprecation.
  • If my number is already on the WhatsApp Business app, do you support Coexistence? A good answer is yes, with the app and the API running together.
  • Will I complete the WhatsApp business verification steps as part of onboarding? A good answer walks you through it rather than leaving you stuck.

What are the day-to-day operations, from templates to data export?

The last group is the everyday experience. It rarely shows up in a demo, so ask directly.

  • How do you handle template creation, approval and category changes? A good answer is a clear process, not a support ticket each time.
  • How are my messaging limits and quality rating surfaced to me? A good answer shows them in your dashboard.
  • What is your support response time when sending breaks? A good answer is a concrete window, not “we will look into it.”
  • Can I export my contacts and message history if I leave? A good answer is a full export in a usable format.
  • How is per-message pricing billed, Meta’s rate plus your margin or a bundle? A good answer is transparent, and the underlying rates are in WhatsApp Business API pricing.

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

Frequently asked questions

What is the most important part of how to choose a WhatsApp BSP?

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.

Can I move my number to another provider later?

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.

How do I keep my ad tracking with a BSP?

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.

Why do business-scoped user IDs matter when choosing a BSP?

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.

Which Embedded Signup flow should a provider use?

A current one. Embedded Signup v2 reaches its deprecation date on 8 October 2026, and newer flows handle Coexistence automatically.

Should price decide how to choose a WhatsApp BSP?

Price matters, but ownership, tracking and data export decide whether the choice holds up over time. The pricing mechanics are a separate question.