WhatsApp’s Update of the Year: The messaging app is phasing out mobile phone numbers as its primary identifier and switching to BSUID

WhatsApp is rolling out its most significant architectural update in recent years. Starting in 2026, a phone number will no longer be a required or guaranteed identifier for users on the messaging app. The company plans to begin implementing these changes as early as July.
For companies that use the WhatsApp Business API for sales and support, this means a change in their existing workflows.

Let’s take a closer look.

BSUID Instead of a Phone Number

Until now, a phone number has served as a universal “key” that businesses used to identify customers across various systems. In 2026, this will change:

  1. BSUID (Business-Scoped User ID) becomes the primary identifier. This is a unique user ID linked specifically to your business account.
  2. Username becomes an alternative. Customers will be able to find companies and message them by name (like on Telegram) without revealing their phone number.
  3. Phone numbers become optional. Users will decide for themselves whether to share their number with a company or remain anonymous.

Why is this happening?


Meta is working to enhance privacy. Now, users can start a conversation with a brand, check prices or product availability, without sharing their personal information (such as their phone number) until they complete a transaction.

What risks does this pose to the business?

If your CRM system or backend is configured so that customer profiles are created strictly based on phone numbers, you may encounter the following issues:

  • Loss of leads: Messages from users with a username but no phone number will not be captured by the system.
  • Duplicate contacts: The same person might message you anonymously at first and later with a phone number, and the system won’t be able to automatically merge them.
  • Analytics glitches: It will become harder to track the customer’s journey from the first click to the purchase.

How can you prepare for the changes?

It’s time to start preparing your architecture now:

  1. Review the customer identification logic in your CRM. The BSUID should be the primary field for searching for a customer, while the phone number should be an additional attribute.
  2. Adapt your chatbots. If you need a phone number to complete a task (such as placing an order or verifying an account with a bank), add a step to the bot’s script asking the user to share their contact information.
  3. Reserve your username. As soon as possible, secure your brand name in Meta Business Suite. This will make it easier for new customers to enter the sales funnel.

Our role in the transition

As an official WhatsApp Business API provider, edna Pulse handles the technical complexities of this transition. We provide full support for the new identifiers:

  • Data Transfer: Our webhooks already include fields for BSUID and Username.
  • Backward Compatibility: Existing integrations will continue to work, but we’ll provide all the tools you need to update your logic to meet Meta’s new requirements.
  • Conversation History: The platform will help map user IDs so you don’t lose your communication history.

However, despite these changes, the company will still be able to send a message to a customer if it has their phone number. For example, if a user submitted a request on the website and provided their mobile phone number.

Summary: The transition to BSUID is not merely a technical update, but a paradigm shift in messaging. Companies that are the first to adapt their systems to support anonymous interactions and usernames will gain a competitive edge by enabling customers to enter conversations more easily and securely.