WhatsApp BSUID Explained: a 2026 guide for every platform (GHL, respond.io, Wati, SleekFlow, Bird, Twilio and more)

What is a WhatsApp BSUID?

A BSUID is a Business-Scoped User ID - a stable, unique identifier that Meta assigns to each WhatsApp user inside the scope of a single business. It looks like US.13491208655302741918 (a country code, then a numeric suffix). Two different businesses messaging the same person get two different BSUIDs. The ID is private to your business and doesn't change when the user updates their phone number.

That definition is the short answer. The rest of this guide is what it actually means for the way you run WhatsApp today.

Why this matters right now

If you run customer conversations on WhatsApp, something is shifting underneath you this year. It isn't a new feature. It isn't a new message template. It's a change to the thing your entire WhatsApp setup is built on: how a customer is identified.

It affects every business using the WhatsApp Business Platform, no matter which provider you use. GHL (GoHighLevel), respond.io, Wati, SleekFlow, Twilio, Bird, 360dialog, Gupshup, Zoko, Interakt, DoubleTick. They all sit on top of Meta's platform, and they all have to adapt.

This post breaks down what's changing, what quietly breaks if you ignore it, and what good preparation looks like across the major platforms.

What's actually changing on the WhatsApp Business Platform

Meta is rolling out two connected changes.

The first is the BSUID itself. The second is WhatsApp usernames. Users will soon be able to pick a username and use it to hide their phone number from any business they haven't messaged in the last 30 days. For those users, your incoming messages will carry only the BSUID, not a phone number.

Put simply: the phone number has been WhatsApp's main customer ID since day one. That stops being true later this year.

Why Meta is making this change

WhatsApp is no longer a phonebook with chat bolted on. It's turning into a social platform where people want to talk to businesses without handing over their main phone number. Usernames are the privacy layer. BSUIDs are the plumbing that lets businesses keep running without that phone number in hand.

For users, that's a privacy win. For businesses, it's a data change. Your systems need a new way to recognise the person on the other end.

WhatsApp BSUID rollout timeline

Here's what Meta has shared publicly.

• April 2026BSUIDs begin appearing in incoming messages.
• May 2026Businesses can start sending messages using the BSUID.
• End of June 2026Phone numbers may stop appearing for users who've turned on a username.
• Later in 2026Usernames roll out broadly to WhatsApp users.

Translation: you have roughly two months to get your stack ready before the first customers start arriving without phone numbers.

What quietly breaks if you do nothing

Most WhatsApp setups use phone number as the main way to match a customer. That assumption is baked into five places that will fail in the background if you don't touch them.

1. Your contact list. Matching, merging, and "find existing user" logic usually runs on phone number. A user who arrives with only a BSUID will be created as a brand new contact, even if they spoke with you last month. Your list starts to duplicate.
2. Your automations. Any workflow that filters, routes, or segments by phone will skip contacts without one. Silent drops are the worst kind of bug, because no one notices until a customer complains.
3. Your CRM and reporting. HubSpot, Salesforce, Zoho, spreadsheets, Zapier, your data warehouse. Anything downstream that matches on phone will miss a growing slice of your audience. Attribution reports, lifecycle tags, and revenue-to-contact mapping start to drift.
4. Your outbound campaigns. You can't cold-message a user who only has a BSUID. They have to message you first, or you have to be inside the 30-day window. If you run campaigns that pull contacts from outside sources, this changes how that works.
5. Your login and authentication flows. WhatsApp's one-tap, zero-tap, and copy-code authentication still need a phone number. Those templates won't accept the BSUID. If you use WhatsApp for login codes, you need a separate plan for users without one.

Want the printable version? Grab our BSUID Readiness Checklist - a one-page audit you can run on your own setup in 15 minutes.

A 60-second self-check

Before we get into platform-specific notes, run through this. If you answer "no" or "I don't know" to more than two, you have real work to do.

1. Does your contact schema have a dedicated field for the BSUID?
2. When a new message arrives, do you capture both the phone and the BSUID (when available)?
3. Do your automations have a fallback path for contacts without a phone number?
4. Does your CRM carry the BSUID into its own contact record?
5. Do you know which of your message templates are authentication templates?
6. Do you know how new contacts enter your WhatsApp platform today (ads, QR codes, forms, imports)?
7. Is someone specifically responsible for the phone/ID field across your stack?

How the WhatsApp BSUID change affects each platform

The migration work is the same shape everywhere, but the tooling is different on each one.

GHL (GoHighLevel) - Hugely popular with agencies and SMBs running WhatsApp through LeadConnector. GHL's contact deduplication is phone-first by default, so the first symptom you'll see is duplicate contacts piling up for username users. You'll need a custom field for the BSUID, workflow triggers updated to handle BSUID-only contacts, and merge tags like {{contact.phone}} reviewed across templates and SMS-fallback flows. If you ship sub-account snapshots that include WhatsApp templates, those need updating too. The LeadConnector layer handles routing, but the field mapping, automations, and pipelines on top are on you.

respond.io - The change lives in contact fields, workflows, and the integrations layer. Adding a custom BSUID field is straightforward. The care goes into the workflows that read the phone field and the tools connected on the other side (CRM, Google Sheets, webhooks).

Wati - Popular with SMBs, especially in India and Southeast Asia. The Wati contact model is simple, so adding a BSUID field is quick. The risk sits in the Shopify, HubSpot, and Google Sheets connectors that run a lot of Wati accounts today. Those need the BSUID carried through.

SleekFlow - APAC-focused, often deployed with commerce stacks (Shopify, BigCommerce, Magento). Segmentation and broadcast rules that filter on phone are the main thing to review. The commerce integrations also need attention so customer matching against orders still works.

Twilio - A developer platform, so the work is engineering-led. Your Conversations API consumers need to read and store the new identifier. Anything you've built on top (custom CRM bridges, serverless functions, your own UIs) needs the same treatment.

Bird - Bird has already started communicating the change to customers, which is how this is coming up in the first place. Their SDK updates land automatically, but the account-level integration and field mapping work is still on you.

360dialog - An API-only provider, so there's no UI to worry about. Everything is in the stack you've built on top. The entire burden sits with whoever owns that application.

Gupshup, Zoko, Interakt, DoubleTick - Common SMB platforms in India. Most lean heavily on Shopify or WooCommerce. The risk is less in the bot logic and more in the commerce matching layer that pairs WhatsApp users with order history.

The punchline: whichever platform you're on, this is a data model change, not a platform rebuild. The tools differ, the work is the same.

What good BSUID preparation looks like

Across platforms, here's the order of operations we use.

1. First, schema. Add the BSUID field to every contact record, in the messaging platform and in every system downstream. Nothing else matters if the field isn't there.
2. Second, ingestion. Make sure every new message writes both the phone (when available) and the BSUID. Check webhooks, API routes, and any custom ingestion scripts.
3. Third, matching logic. Update every "find existing contact" rule so it checks BSUID first, then phone. This prevents most duplication.
4. Fourth, workflows. Review automations that filter, route, or segment by phone and add fallback paths.
5. Fifth, integrations. Walk every connected tool (CRM, warehouse, spreadsheets, custom apps) and confirm the BSUID is carried forward end to end.
6. Sixth, authentication review. Flag templates that won't work on BSUID-only users and design a separate path for them.
7. Seventh, test. Send real messages, watch the full data trail, and confirm nothing drops between systems.

How Zelix Labs can help

Zelix Labs builds AI teams for companies. WhatsApp, respond.io, GoHighLevel and the rest are just the tools we build on - the actual job is standing up AI employees that handle your sales, support, and follow-up across every channel your customers use. The BSUID switch is exactly the kind of plumbing change those AI employees are built to absorb.

When we build your team, the BSUID migration comes with it. We know where workflows, snapshots, custom fields, merge tags, and platform integrations quietly depend on phone numbers, and we rebuild them to key off the BSUID so nothing drops when the phone numbers start disappearing. Whatever stack you run today - respond.io, GHL, Wati, SleekFlow, Twilio, Bird, or another provider - your AI team is built to work with it.

Frequently asked questions about the WhatsApp BSUID

What does BSUID stand for?

BSUID stands for Business-Scoped User ID. It's the new identifier Meta assigns to each WhatsApp user inside the scope of a single business.

When will WhatsApp BSUIDs go live?

BSUIDs begin appearing in incoming messages in April 2026. Businesses can start sending messages by BSUID in May 2026. Phone numbers may stop appearing for username users by end of June 2026.

Will my customers' phone numbers disappear?

Only for users who turn on a WhatsApp username and hide their phone number. You'll keep seeing phone numbers for everyone else, and for username users you've messaged in the last 30 days.

Do I need to rebuild my GHL, respond.io, Wati, or SleekFlow account?

No. This is a data model change, not a platform rebuild. You need to add a BSUID field, update matching logic, and check your connected tools.

How does the BSUID change affect GoHighLevel (GHL) specifically?

GHL contacts are deduplicated by phone number, so the first thing you'll see is duplicate contacts for username users. You'll need a custom BSUID field, workflow triggers updated, merge tags reviewed, and any sub-account snapshot that ships WhatsApp templates updated as well.

Will WhatsApp authentication templates still work?

One-tap, zero-tap, and copy-code authentication still need a phone number. They won't work on BSUID-only users, so you need a separate path for those users.

Can I cold-message a user using their BSUID?

No. You can only message a user by BSUID if they've messaged you first or are within the 30-day window from your last conversation.

Does the BSUID change if a user changes their phone number?

The BSUID stays stable for the user inside your business scope. Your platform handles the rotation in the background, so you don't need to manage it manually.

What happens to my CRM integration?

Any CRM, spreadsheet, or warehouse that matches on phone needs to carry the BSUID across as well. Without it, you'll see duplicate records and broken segments over time.

Final words

WhatsApp is growing into a place where people can talk to businesses without trading their phone number for it. That's good for customers, and handled well, it's fine for businesses too. The job is to stop treating the phone number as the identity and start treating it as an attribute.

Businesses that plan for this in the next two months will barely feel the switch. Businesses that wait will spend the back half of 2026 chasing data quality bugs.