Overview
Meta has announced an upcoming update to WhatsApp that introduces usernames for both WhatsApp Users and Businesses. In addition, they are introducing a new backend identifier for businesses called the Business-Scoped User ID (BSUID).
These changes are designed to modernize how users are identified and messaged on WhatsApp.
- Initial rollout (usernames): June 2026
- General availability: August 2026
- Community is actively preparing for this change in collaboration with key partners and will keep customers informed as more details become available
What’s Changing?
1. Usernames for WhatsApp Users (Optional)
WhatsApp Users will have the option to create a username, which may be displayed instead of their phone number in the app.
- Usernames for users are optional
- Each user can have one username, but can update it over time
- Usernames do not replace the underlying phone number or identity
- Messaging functionality remains unchanged
Important: Usernames are primarily a display feature, not a replacement for identity or messaging infrastructure.
2. Business Usernames
Businesses can also adopt usernames.
- Business usernames are not designed for privacy
- Your business phone number (in this case your Community phone number) will still be visible
- The Business Username is primarily a branding or discoverability feature
- Business usernames must be set individually. While Community cannot configure this on your behalf, we will provide guidance and instructions to support you through the process.
3. New Identifier: Business-Scoped User ID (BSUID) for businesses
Meta is also introducing a new identifier called the BSUID, which will become critical for messaging moving forward.
What is a BSUID?
- A unique identifier for each user-business relationship
- Example format: US.13491208655302741918
- Automatically generated by Meta
- Tied to a specific business portfolio (WABA)
Why it matters:
- You can message users without needing their phone number
- BSUID will become a primary identifier in APIs and webhooks
Key Behavioral Changes
1. Phone Numbers May Not Always Be Available
If a user enables usernames:
- Their phone number may no longer appear programmatically (APIs, webhooks)
Phone numbers will only be included if:
- You’ve interacted with the user in the last 30 days
- The user is in your contact list
Implication: Community’s system should not rely solely on phone numbers to identify users moving forward.
2. BSUID Will Be the New Standard
- BSUID will appear in all webhooks (starting April 2026 - specific date not yet identified)
- Messaging via BSUID will be supported starting May 2026
- You can send messages using:
- Phone number
- BSUID
- Or both
Implication: Community’s system should begin supporting BSUID-based messaging and storage
3. BSUIDs Are Portfolio-Specific
- BSUIDs are tied to a specific business portfolio (WABA)
- They cannot be used across different portfolios
Example:
- If Brand A generates a BSUID → only Brand A can use it
- Another brand (even within the same CPaaS) cannot use that BSUID
4. Usernames in APIs
- Usernames will appear in:
- Incoming message webhooks
- Delivery/read receipts
- They can be used for personalization, but not as a unique identifier
What This Means for You
- No immediate action is required at this time. We will share additional guidance and next steps as they become available to support enabling usernames
- Community’s system will continue using phone numbers as usual
- Community is aware of this change and is actively preparing, and will continue to keep customers updated as we roll out support for User Usernames, Business Usernames, and BSUIDs.