WhatsApp Usernames and BSUID in 2026: The Complete Business Readiness Guide

Meta is changing how businesses recognize the people who message them on WhatsApp. Starting with a phased rollout in July 2026, WhatsApp users will be able to hide their phone number behind a chosen username – and businesses will need a completely different identifier to keep conversations, CRM records, and chatbot workflows intact. That identifier is called the Business-Scoped User ID, or BSUID.

If your team relies on WhatsApp for sales, support, or marketing automation, this is not a cosmetic update. It changes what shows up in your webhooks, what your CRM stores as a contact key, and how your automation logic identifies a returning customer. This guide breaks down exactly what’s changing, how BSUID actually works, and the concrete steps to keep your messaging stack running without interruption.



Key Takeaways

• WhatsApp usernames are optional and let users message businesses without exposing their phone number.
• Businesses receive a new identifier – the BSUID – to keep messaging users who choose a username.
• Existing contacts and phone-number-based messaging are not affected; the change mainly impacts new, username-first conversations.
• Any CRM, chatbot, or automation flow keyed strictly on phone number needs to be updated to also store and match on BSUID.
• Businesses can also reserve their own username to strengthen brand recognition inside WhatsApp.

What Exactly Is a WhatsApp Username?

For years, a WhatsApp account has been synonymous with a phone number. That’s changing. Users will soon be able to set a unique handle – something like @Jordan.Retail – and use it as their public identity instead of their mobile number when starting chats or joining groups.

The motivation is straightforward: many people are uncomfortable handing a phone number to a company just to ask a question. A username lets them start that conversation while keeping their number private, which in turn should make more people willing to reach out to businesses in the first place.

Here’s how visibility actually plays out once a user adopts a username:

• New contact, username adopted: the business sees the username, not the phone number, unless there’s a qualifying prior interaction.
• No username set: nothing changes – the phone number remains visible exactly as it does today.
• Existing relationship: if a business already had the number on file, or exchanged a message within the 30 days before the user switched on a username, the number stays visible.

Claiming a Business Username

Businesses aren’t limited to receiving usernames – they can reserve one too, giving customers a memorable, searchable handle to find them by. Reservations for Official Business Accounts and Meta Verified profiles opened on June 29, 2026, through both WhatsApp Manager and Meta Business Suite.

Via WhatsApp Manager:

1. Open WhatsApp Manager and select Phone number, then your number.
2. Go to Profile and scroll down to Username.
3. Select Create, then type your desired handle (or pick one from the suggested list).
4. Save and close.

Via Meta Business Suite:

1. Navigate to WhatsApp Accounts and select your number.
2. Open Phone numbers, then click the edit (pen) icon.
3. Scroll to Username, choose Create, and enter your handle.
4. Save and close.

Reserved usernames activate automatically once the feature launches in your region, and Meta notifies you when it goes live.

BSUID: The Identifier That Keeps Your Messaging Working

Hiding a phone number on the front end creates a real problem on the back end: how does a business keep talking to someone it can no longer identify by number? Meta’s answer is the Business-Scoped User ID (BSUID) – a stable, anonymized identifier issued per user, per business.

According to Meta’s own developer documentation, BSUID uniquely identifies a WhatsApp user and is tied to a specific business, and the identifier is designed to change how API requests, responses, and webhook payloads behave once usernames roll out. A few properties matter most for anyone building automation on top of it:

• Business-scoped, not global. The same person messaging two different companies will show up with two completely different BSUIDs – there is no cross-business tracking.
• Tied to your Business Manager. One BSUID stays consistent across every phone number and WABA registered under the same Facebook Business Manager.
• Persistent. A BSUID doesn’t rotate on its own. It only changes if the underlying user switches their phone number.
• Format: an ISO 3166 country-code prefix followed by an alphanumeric string, up to 128 characters – for example, HK.13491208655302741918.

Independent platform documentation confirms the same core mechanics from a different angle: a business-scoped user ID is a unique, stable identifier for a WhatsApp user within a business portfolio, following the format of an ISO 3166 alpha-2 country code plus a period and up to 128 alphanumeric characters. That consistency across independent sources is a good sign the format is stable enough to build lasting logic around.

How BSUID Shows Up Depending on the User

Scenario	What your business receives
User hasnot adopted a username, and you support BSUID	Phone numberand BSUID
User hasnot adopted a username, and you don’t support BSUID	Phone number only
Userhas adopted a username, no prior interaction	BSUID only
Userhas adopted a username, with a qualifying prior interaction	Phone numberand BSUID

Platform vendors that sit between Meta and businesses have been rolling out matching support for months. One notable example: Meta launched a contact book feature in early April 2026 that automatically stores phone number and BSUID pairs from prior interactions, and once a user is in that contact book, their phone number keeps appearing in webhooks regardless of whether they’ve since adopted a username. That’s a helpful safety net for businesses with an existing customer base, but it doesn’t cover brand-new, username-only conversations – which is exactly where BSUID becomes essential.

Getting Your Stack Ready: A Practical Checklist

The businesses that sail through this transition are the ones treating it as a data-model update, not just a feature announcement. Here’s the sequence worth following:

1. Add a BSUID field to your CRM. Don’t overwrite phone number as your primary key – store both side by side so historical records stay intact. This is exactly the kind of structured customer record that a purpose-built CRM Contacts system is designed to hold, keeping phone number, BSUID, and conversation history unified under one profile.
2. Update contact-resolution logic so it can match a returning customer by either identifier – not phone number alone. As other platforms have publicly confirmed, a BSUID is tied to a business portfolio rather than to any individual phone number within it, and any phone number belonging to that portfolio can message a BSUID scoped to the same portfolio, which means your matching logic needs to think in terms of portfolios, not just numbers.
3. Audit every automated flow – welcome sequences, cart-recovery messages, support routing – for hardcoded assumptions that a phone number will always be present. A visual Flow Builder makes this audit far easier, since you can trace exactly where a conversation checks for a phone number and insert a BSUID fallback without rewriting logic from scratch.
4. Keep AI-driven conversations resilient. If AI Agents handle your first response, make sure they’re not blocked from replying just because a phone number field is empty – the BSUID alone is enough to continue the thread.
5. Use native sharing prompts when a phone number is genuinely required (shipping, verification), rather than assuming you can always request one manually.
6. Reserve your business username early, so your brand has a clean, recognizable handle the moment the feature is live in your market.

Vendors serving high-volume WhatsApp integrations have already flagged this as a breaking-change risk for anyone not paying attention. One migration guide notes that legacy client records not yet updated by Meta will still show a phone number rather than a BSUID, so integrations need to handle both formats simultaneously during the rollout window – a detail worth building into your testing plan rather than discovering in production.

Where ChatbotX Fits Into This Transition

This is exactly the kind of infrastructure shift where an open-source, omnichannel platform earns its keep. ChatbotX connects your WhatsApp number alongside Messenger, Instagram, Telegram, and more inside a single workspace, so BSUID adoption doesn’t mean rebuilding your customer data model channel by channel. Because the platform is fully open source, technical teams can inspect exactly how contact identity is stored and extend it directly in the ChatbotX GitHub repository – including tracking upcoming BSUID-related updates through the project’s release history.

If you’re already comparing WhatsApp infrastructure providers for reasons beyond this one update, our guide to choosing a WhatsApp Business Solution Provider in 2026 walks through the broader evaluation criteria – compliance, pricing structure, and automation depth. And if your operation spans multiple regions and messaging apps at once, the Greater Bay Area omnichannel playbook covers how to keep WhatsApp, WeChat, and LINE identity data unified across borders – a similar challenge to the one BSUID introduces within WhatsApp alone.

Frequently Asked Questions

Do I have to adopt BSUID?

Usernames themselves are optional for end users, but if any of your customers choose one, your business needs BSUID support to keep messaging them. Ignoring it risks losing contact with that segment entirely.

Will my current WhatsApp broadcasts stop working?

No. Any contact you can already message by phone number keeps working exactly as before. The change mainly affects new, inbound conversations from customers who message you for the first time after adopting a username.

Can I still see phone numbers for existing customers?

Yes, provided you had the number on file already or interacted within the 30 days before they switched on a username. Outside that window, you’ll rely on BSUID and can request the number directly through WhatsApp’s native sharing flow.

Is a business username the same thing as BSUID?

No. A business username is a public-facing handle customers can search for. BSUID is a private backend identifier your systems use to keep messaging a specific user – the two solve different problems.

Ready to Future-Proof Your WhatsApp Automation?

BSUID adoption is a one-time engineering lift, but the businesses that treat it seriously now will avoid a very real risk of losing conversations later this year. Start by mapping your CRM fields, testing your automation flows against both identifier types, and reserving your business username before the rollout reaches your market. If you’d rather not manage this migration channel by channel, explore how ChatbotX brings WhatsApp, CRM, and AI-driven automation together in one open-source platform – start free at chatbotx.io, no credit card required.