WhatsApp is rolling out some important updates that will change how users and businesses connect on the platform.
Meta’s upcoming changes to WhatsApp will introduce new usernames and a backend identifier known as the Business-Scoped User ID (BSUID), but for Community customers, the immediate reality is far less disruptive: nothing about how you message users today needs to change.
But it’s helpful to understand what’s coming and how it may impact your messaging strategy over time so we’ve laid out some information below with a link to more technical documentation.
The update, scheduled to begin rolling out in June 2026 and launch globally in August 2026, is expected to gradually reshape how users are identified on WhatsApp. In the short term, however, Community customers can continue relying on phone numbers as they do today, with no required action or impact to existing messaging flows. The more significant changes, particularly around BSUID, will emerge over time, not overnight.
That said, the shift is important to understand because it introduces a future where phone numbers are no longer guaranteed to be available in every interaction. As users gain the option to create usernames, their phone numbers may stop appearing in APIs and webhooks unless there has been a recent interaction within 30 days or the user is saved as a contact. Even so, this change will not immediately break current implementations, as phone numbers will continue to be supported alongside the new identifiers.
The longer-term transition centers on BSUID, a unique identifier Meta assigns to each user’s relationship with a specific business. This identifier will begin appearing in webhooks as early as April 2026 and will support outbound messaging starting in May. Over time, it is expected to become the primary way businesses identify and message users, particularly in cases where phone numbers are no longer accessible.
For Community customers, the practical implication is not urgency but awareness. Systems built entirely around phone numbers will continue to function, but they should eventually evolve to store and support BSUID as well. Community is already preparing for that transition and will provide guidance as capabilities are rolled out.
The introduction of usernames, while more visible to end users, plays a much smaller role in how businesses operate. Users may choose to display a username instead of their phone number within the app, and businesses can adopt usernames for branding purposes, but these names do not replace the underlying identity systems. They may appear in webhooks and receipts, offering opportunities for personalization, but they are not designed to function as unique identifiers.
In the near term, then, the takeaway for Community customers is straightforward: continue operating as usual. The changes announced by Meta represent a gradual evolution rather than an immediate disruption. Phone numbers still work, messaging flows remain intact, and no immediate updates are required.
What is changing is the direction of the platform. Over the coming months, as BSUID becomes more prominent and phone number visibility becomes less consistent, businesses will need to adapt. Community is actively working with partners to ensure customers are supported through that transition, with more detailed guidance expected as the rollout progresses.
In the meantime, if you’re looking for more technical information, please check out this support doc we’ve created.