In this article you will find a detailed explanation regarding WhatsApp's transition toward usernames and the BSUID identifier, including who this change impacts, technical updates on the Botmaker platform, and a frequent questions guide so your company can adapt its processes and systems before june 2026.
Starting in june 2026, WhatsApp Business Platform will introduce significant changes in the way companies identify and communicate with their users. This evolution seeks to prioritize privacy, allowing people to interact with businesses without the need to share their phone number.
The Business Scoped User ID (BSUID) is a unique and anonymous identifier generated by Meta for each specific combination of user and company. It is an alphanumeric string of up to 128 characters. The BSUID identifier uses the user's two-letter country code according to the ISO 3166 alpha-2 standard as a prefix, followed by a dot and an alphanumeric string of up to 128 characters (for example: US.13491208655302741918). It does not contain personal information, only the country associated with the account. It is specific to each Meta Business Manager: a user's ID for "Company A" will be different from their ID for "Company B."
Botmaker is adapting to make this transition seamless: Chats: They will always have the BSUID information visible. Contacts: They will be grouped by BSUID to maintain information consistency. API and Integrations: Conversations can be managed using the phone number, the BSUID, or the ChatID.
To understand the technical and functional magnitude, these are the pillars of the update: Privacy of the identifier: When a user adopts a username, their phone number is hidden and the company receives the BSUID instead. Nature of the BSUID: It is a unique code generated by Meta for each specific user-company combination. It is an alphanumeric string of up to 128 characters (much longer than the 15 characters of a standard phone number).
Chats and Contacts: BSUID information will be accessible and contacts will be automatically grouped under this new ID.
New entries: New customers will arrive through organic channels (QR, links), ads (CTWA), or platforms such as Email and SMS.
Notifications to phone numbers The ability to send notification templates using traditional phone numbers will be maintained, as the system will allow referencing WhatsApp conversations through the ChatID, phone number, or the new BSUID. For those contacts who already have a registered number from previous interactions, Botmaker will keep both pieces of data to ensure service continuity.
It is important to identify which processes will be modified and which will remain the same: Those affected:
WhatsApp channels exclusively: This change does not apply to other social networks connected to Botmaker. Outbound campaigns for users who have not shared a phone number: Specifically marketing or utility campaigns. The notification can be sent, but via BSUID.
Those not affected:
User-initiated conversations (User Initiated): When the customer writes first, communication flows normally. Authentication templates (OTP): Verification code messages show no changes in their structure. Historical customers: People who have had communication with the bot between march and june 2026 will not see their future relationship with the company affected. Users who consented: Customers who, after june 2026, have explicitly accepted to share their phone number.
How will notifications be sent?
Companies will be able to refer to WhatsApp conversations and send notifications using three types of identifiers: ChatID, phone number, or BSUID. The platform will allow uploading any of these data points to initiate or maintain communication.
What happens if a user does not want to share their phone number? How are templates sent to them?
If the user chooses to hide their number, the company will receive their BSUID. You can continue sending outbound campaigns or messages through the API using this identifier instead of the phone number. If for operational reasons (such as a physical shipment or legal validation) you need the number, you can request it from the user through a utility or marketing template designed to capture that data.
Can templates still be sent to users with phone numbers?
Yes. If you already have the WhatsApp number registered from previous interactions, Botmaker will keep both data points (phone and BSUID). Additionally, for existing contacts, the phone number will remain visible and usable if the user is already in your Meta "Contact Book."
How will templates continue to be sent?
The technical process remains similar, but with greater flexibility in the identifier. Marketing campaigns and utility messages can be triggered using the BSUID. It should be noted that authentication templates (OTP) will not undergo changes in their basic operation. These can only be sent by phone number and not by BSUID.
What should companies do to adapt to this change?
To avoid interruptions, we recommend following these steps:
Update databases: Expand ID fields in your systems from 15 to 128 alphanumeric characters to support the BSUID format.
Identity mapping: Prepare your CRMs to record both the BSUID and the phone and email, linking them to a single customer profile.
Enable the contact book: In march 2026, you must configure the Contact Book function in Meta Business Suite to ensure that current customers' numbers remain visible.
Redesign flows: Adjust bots so they can initially operate with only the BSUID, without depending obligatorily on the phone number to function.
Remember to visit our Help Center for further information.