Key points
If your customer service operation runs on WhatsApp, there is an infrastructure change coming that will directly affect your campaigns, your CRM, and your service flows. It is not optional. And it has a deadline: June 2026.
Why WhatsApp is moving away from the phone number as a universal identifier
Until now, every WhatsApp conversation revolved around a phone number. It was the universal identifier: the field that linked the user to their CRM record, the data point that triggered a campaign, the anchor of any service flow.
That is changing with the rollout of WhatsApp Usernames for businesses in 2026.
Research conducted by Meta across more than 40,000 users in ten markets shows that control over personal information is one of the top concerns when using WhatsApp. The platform's response is structural: if users adopt a username instead of exposing their phone number in conversations, they gain greater control over how they share their contact information. The data also shows that users feel more comfortable engaging with businesses when their personal information remains private.
The practical result: the phone number will no longer be automatically shared with businesses when a user adopts a username. WhatsApp will replace it with a new backend identifier called the BSUID (Business Scoped User ID).
This is not a peripheral privacy improvement. It is a reconfiguration of the identity layer on which your entire conversational infrastructure operates.
What the BSUID (Business Scoped User ID) is and how it affects your operation
The BSUID is the new identifier WhatsApp will provide to partners and businesses using the Cloud API, in place of the user's phone number.
It is unique per user within your business. No two users share the same BSUID on your platform.
It is business-scoped, not universal. Two different businesses will receive different identifiers for the same user. This guarantees additional privacy, but also means the BSUID in your CRM is not portable or comparable with that of another provider or a different Business Manager account.
It arrives in the same webhooks where the phone number arrives today. It is not a new field in a new place: it replaces the phone number at existing integration points for users who have adopted a username.
A relevant technical detail for product teams: if a user changes their phone number, WhatsApp generates a new BSUID, in the same way that conversation history is lost today when a phone number changes.
Click-to-WhatsApp and Service Messages: the flows that break if you do not adopt the BSUID
This is where urgency becomes concrete.
If a business or partner does not adopt the new identifier on time, the message flows that will break when interacting with a user who has adopted a username are two: receiving messages originating from Click-to-WhatsApp ads, and receiving inbound service messages.
Translated into contact center reality:
- Click-to-WhatsApp campaigns: any Meta ad driving users to WhatsApp will stop generating conversations for that user segment. Ad spend keeps running. Conversations do not.
- Inbound service messages: users reaching out with a query, a request, or an issue will not arrive on your platform if their phone number is not visible and your system is not prepared for the BSUID.
The failure carries no visible technical alert. Conversations simply do not arrive. This is what we call Operational Silence: the operation appears to be running, but a growing portion of users falls out of reach without dashboards immediately reflecting it. For businesses with active paid social investment and WhatsApp as a primary service channel, this risk is direct and immediate.
Passkeys, the 30-Day Window, and Operational Continuity: what changes and what doesnot
The change is not abrupt for every scenario. WhatsApp has designed transition mechanisms worth knowing.
The 30-day window. WhatsApp will automatically return a user's phone number for a period of 30 consecutive days following any interaction between the business and that number. Outside that window, a feature in development will allow continued access to the phone number provided there has been prior communication with it.
Users without a username. If a user has not adopted a username, there are no changes to phone number visibility. Authentication messages continue to be sent to phone numbers only, as they are today.
Business-initiated messages. Businesses can continue sending messages to phone numbers they already have, even if the user has set up a username.
Passkeys. In addition to a username, users will be able to set a passkey: a code that other people must know to contact them for the first time. Businesses using the WhatsApp Business API will not need to provide this passkey as long as they already have the user's phone number or BSUID, which demonstrates a prior connection.
The practical conclusion: prior conversational history is a business asset. Users with whom you already have an established relationship are protected during the transition. Those arriving for the first time through an ad or a new channel are not.
How to claim your Business Username on WhatsApp before june 2026
Beyond the operational impact, WhatsApp Usernames for businesses open a brand positioning window.
Usernames will allow businesses to consolidate their presence on WhatsApp, making it easier for customers to find and identify them directly by name, without needing to know a phone number. Verified businesses with a blue badge have their brand protected throughout this transition.
Starting in early June 2026, businesses using the API will be able to claim their existing names: WhatsApp display names, verified accounts, Facebook or Instagram business usernames, and gain early access to a username reserved for them.
Brands that act first secure their handle. In competitive sectors such as contact centers, financial services, retail, or telecoms, arriving late can mean a suboptimal username or a brand dispute process. Early claiming is a low-cost, high-impact action.
Roadmap: what to do before june 2026
Meta's partner roadmap structures preparation across three phases. For a contact center operating on WhatsApp Business API, these are the concrete actions:
Now, planning phase:
- Audit all message flows that use the phone number as the primary identifier.
- Identify downstream systems that will need the BSUID: CRM, automation tools, reporting and measurement systems.
- Define which flows require actively requesting the phone number from the user when needed for other purposes (authentication, CRM lookup, identity verification).
- Secure internal stakeholder commitment: IT, product, operations.
H1 2026, implementation phase:
- Adopt the BSUID on the platform and update the CRM with the new identifier field.
- Review chatbot flows and message journeys to handle users without a visible phone number.
- Update connected workflows: automated campaigns, third-party measurement systems, integrations.
- Update bots and message journeys to proactively request the phone number when needed.
H1-H2 2026, testing and launch phase:
- Participate in end-to-end BSUID testing with Meta.
- Implement and validate the phone number request mechanism for use cases that require it.
- Claim the business username before the global launch.
For Technical Teams: Implementing the BSUID step by step
This section is directed at engineers and product teams.
Data model: from 1D to 2D
Businesses will need to add a new field to the customer profile for the BSUID, alongside existing fields. The user identity model shifts from unidimensional (phone number always present) to bidimensional.
Possible states after launch:
User typeAvailable identifiersNo usernamePhone number + BSUID (if the business has adopted it)Username, prior conversation (30 days)BSUID + phone numberUsername, no prior conversationBSUID only
Webhooks: what changes in the payload
The BSUID will be available in all webhooks that currently carry the user's phone number. No new endpoints are required, but the logic processing the payload must account for the absence of the phone field and operate correctly with the BSUID as the primary identifier.
Critical point: any deduplication logic, CRM lookup, or campaign trigger that today assumes wa_id is always a phone number must be reviewed. The recommendation is to implement a matching algorithm that first attempts the phone number (for users imported via CSV or with prior history) and falls back to the BSUID.
Native phone number sharing flow
WhatsApp is introducing a native sharing flow to minimise errors when collecting the phone number when the business needs it. Users can choose when to share it. Bots and message journeys must be updated to incorporate this flow at the points where the phone number is needed for other purposes (verification, CRM lookup, authentication).
Passkeys: API impact
Businesses using the WhatsApp Business API will not need to provide the user's passkey to send them messages, as long as they already have their phone number or BSUID, which demonstrates a prior connection. The passkey requirement applies only to individuals and businesses without that established relationship.
BSUID across Business Manager accounts
Meta acknowledges there are legitimate reasons to share a BSUID across two accounts within the same Business Manager and is still evaluating this functionality. If your multi-WABA architecture depends on shared user identifiers across accounts, log this with your Meta partner to ensure it is documented in their consultation process.
FAQs About WhatsApp Usernames and BSUID
What is the WhatsApp BSUID?
The BSUID (Business Scoped User ID) is a unique identifier that WhatsApp assigns to each user within the context of a specific business. When a user adopts a WhatsApp username, businesses no longer automatically receive their phone number and instead receive this backend identifier. It is unique per user and per business: the same user will have a different BSUID with each business they interact with.
When do WhatsApp Usernames for businesses come into effect?
The rollout in test countries begins in June 2026, with global expansion during the rest of the year. Businesses using the API can also start claiming their usernames from early June 2026. Technical preparation (BSUID adoption, CRM and flow updates) must be completed before that date.
What happens to my Click-to-WhatsApp campaigns if I do not adopt the BSUID?
If your system is not prepared for the BSUID, it will stop receiving messages generated by users who have adopted a username and arrive through Click-to-WhatsApp ads. The ad will keep running and the user will be able to click, but the conversation will not reach your platform. There is no technical alert: the failure is silent.
Does the BSUID replace the phone number in the CRM?
It does not replace it: it complements it. Businesses will need to add a new field to the customer profile for the BSUID, alongside existing fields such as phone number and email. The user identity model shifts from unidimensional (phone number always present) to bidimensional. Any deduplication logic or CRM lookup that assumes the WhatsApp identifier is always a phone number must be reviewed.
Can businesses still request phone numbers from users after the change?
Yes. The phone number does not disappear; it becomes optional for users who adopt a username. Businesses can continue to actively request it through the native sharing flow WhatsApp is implementing. Bots and message journeys must be updated to incorporate this flow at the points where the phone number is needed for other purposes.
What happens if I migrate my WABA to another provider after the launch?
When a business re-registers its WABA (for example, when migrating from one BSP to another), Meta generates new BSUIDs for all customers, as the business portfolio has a new identity. BSUIDs stored in the CRM before the migration will be invalidated. This is a critical point to factor into any provider change planned from 2026 onwards.
.jpg)
