WhatsApp has become an important communication channel for many organisations. Meta continues to actively evolve the platform, with a strong focus on privacy, scalability and security. One of the most impactful upcoming changes is the introduction of WhatsApp Business Scoped IDs.
Meta has announced that this feature will officially be rolled out in 2026. This timeline is based on Meta’s current guidance and may still change in future.
At Spotler, we are already fully prepared. This means our Spotler Message and Spotler Engage customers do not need to wait adjustments or risk disruption once Meta activates this change.
From phone numbers to Scoped IDs
Until now, the phone number has been the central and universal identifier on WhatsApp. It acted as the fixed technical key to recognise customers, conversations and message history, regardless of the WhatsApp Business environment or integration used.
With WhatsApp Business Scoped IDs, this model fundamentally changes. The phone number remains a contact detail, but it is no longer always shared or used as the technical identifier. Instead, WhatsApp introduces a unique Scoped ID for each user and each WhatsApp Business account. A Scoped ID looks like this:
Before — phone number
+61 412 345 678
Universal and works across all platforms and integrations.
After — Scoped ID
AU.13491208655302741918
Unique per user and per business account. Cannot be shared across organisations.
The phone number remains part of the contact information, but it will no longer always be shared or used as the technical identifier. The Scoped ID becomes the stable, privacy-safe way to recognise a user within your WhatsApp Business account.
Important: the same user will have a different Scoped ID for your business than for another organisation. This prevents users from being tracked across companies.
Communicating via a username instead of a phone number
MMeta is introducing the option for end users to communicate with businesses using a WhatsApp username. When an end user chooses this option:
- The phone number is no longer shared with the business
- The business receives a WhatsApp Business Scoped ID instead
- The Scoped ID becomes the primary technical identifier for the conversation
In practice, this means that organisations can no longer assume that a phone number is always available for CRM matching, reporting, or cross-channel synchronisation. The Scoped ID is the stable, privacy-focused way to identify a user within a specific WhatsApp Business account.
A phone number may still be visible if you have communicated with the user in the past 30 days, or if the number already exists in your customer database. Only when neither applies and the user has set a username will you receive only the Scoped ID.
Important: every WhatsApp user will receive a Scoped ID, even if they have not set a username. This means you will receive this ID regardless.
Why is Meta introducing WhatsApp Business Scoped IDs?
Meta is introducing Scoped IDs and username-based communication for several key reasons:
Stronger privacy protection
End users gain more control over how they share personal data, such as their phone numbers.
Clear separation between WhatsApp Business accounts
Identifiers are scoped per business account, preventing reuse across organisations.
A future-proof foundation for WhatsApp
Scoped IDs and usernames enable WhatsApp to operate independently of phone numbers as the technical basis for identification.
What is the impact on organisations?
The impact differs depending on the situation. It helps to distinguish between two scenarios.
New customer via username
You receive only a Scoped ID. No phone number is available unless the user chooses to share it. The Scoped ID becomes the starting point of the customer profile.
Existing customer with a phone number
You can continue using the phone number for outbound messages. However, if the same customer later contacts you via a username, your systems must be able to link the Scoped ID to the existing profile.
The combination of Scoped IDs and username-based communication can have a significant impact, especially for organisations using WhatsApp at scale.
CRM and CDP integrations
Integrations that rely solely on phone numbers as primary keys must be adapted. If they are not, conversations may no longer automatically link to the correct customer profile. This can result in duplicate records or incomplete conversation history within the CRM.
Chatbot and automation flows
Workflows that expect a phone number as input may no longer function correctly and will require adjustment.
Customer recognition across channels
Linking WhatsApp conversations to SMS or other channels via phone number matching may no longer work when the number is not shared. This can cause customers to appear as separate identities across channels, reducing visibility of their full interaction history.
Conversation history and reporting
Without proper support for Scoped IDs, conversations can become fragmented across different identifiers. This can lead to incomplete reporting or broken conversation timelines.
Tip: review your most important customer journeys as if phone numbers were no longer available. This will help identify dependencies before Meta rolls out usernames.
Checklist: how to prepare your organisation for WhatsApp Business Scoped IDs
Want to understand what needs to change within your organisation? Review this checklist and get started today.
How is Spotler prepared?
Within Spotler Message and Spotler Engage, we have fully prepared our infrastructure for WhatsApp Business Scoped IDs ahead of Meta’s announced rollout.
Our readiness focuses on continuity, correct identification, handling, and data integrity.
Native support for WhatsApp Business Scoped IDs
Spotler Message and Spotler Engage supports Scoped IDs as primary conversation identifiers, independent of phone numbers. Conversations are rendered and grouped based on the identifier provided by Meta.
Flexible conversation initiation
Conversations can be initiated and continued whether WhatsApp provides a phone number, a Scoped ID, or both. The system automatically adapts without requiring workflow changes.
Preserving conversation history and context
Existing conversations and message history remain intact.
When a conversation was originally linked via a phone number and WhatsApp later provides a Scoped ID, Spotler Message maps the new Scoped ID to the existing customer profile. This ensures that historical and ongoing conversations remain connected under the same contact record.
Seamless integrations
Standard integrations that run through Spotler Message continue to function because the platform handles both phone numbers and Scoped IDs internally.
Organisations with custom-built integrations that rely solely on phone numbers outside Spotler Message’s identification logic may need to assess and adjust their implementation.
Zero disruption during Meta’s rollout
When Meta enables Scoped IDs by default, no migration or reconfiguration is required for customers using the standard Spotler Message WhatsApp integration. The transition is handled within the platform.
Ready for the new reality?
WhatsApp Business Scoped IDs change the technical basis of identification within WhatsApp: from a universally shared phone number to a Scoped ID unique to each business account.
With Spotler Message and Spotler Engage, you are ready for this new reality.
Want to understand what this specifically means for your CRM integration, chatbot flows or existing setup? View our checklist or get in touch, we will be happy to help.
