{"id":254202,"date":"2026-02-16T16:54:48","date_gmt":"2026-02-16T15:54:48","guid":{"rendered":"https:\/\/spotler.com\/blog\/whatsapp-business-scoped-ids"},"modified":"2026-06-25T22:48:14","modified_gmt":"2026-06-25T20:48:14","slug":"whatsapp-business-scoped-ids","status":"publish","type":"blog","link":"https:\/\/spotler.com\/en-au\/blog\/whatsapp-business-scoped-ids","title":{"rendered":"From phone numbers to usernames: understanding WhatsApp Business Scoped IDs"},"content":{"rendered":"<p><strong><strong><strong>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.<\/strong><\/strong><\/strong><\/p>\n<p><a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/business-scoped-user-ids\/\" target=\"_blank\" rel=\"noopener\">Meta has announced<\/a> that this feature will officially be rolled out in <strong>2026<\/strong>. This timeline is based on Meta\u2019s current guidance and may still change in future.<\/p>\n<p>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.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">From phone numbers to Scoped IDs<\/h2>\n<p>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.<\/p>\n<p>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:<\/p>\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column border1px-blue has-light-blue-background-color has-background is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:50%\">\n<h4 class=\"wp-block-heading has-text-align-center\">Before \u2014 phone number<\/h4>\n<p class=\"has-text-align-center\">+61 412 345 678<\/p>\n<p class=\"has-text-align-center no-mar-bottom\">Universal and works across all platforms and integrations.<\/p>\n<\/div>\n<div class=\"wp-block-column border1px-blue has-light-blue-background-color has-background is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:50%\">\n<h4 class=\"wp-block-heading has-text-align-center\">After \u2014 Scoped ID<\/h4>\n<p class=\"has-text-align-center\">AU.13491208655302741918<\/p>\n<p class=\"has-text-align-center no-mar-bottom\">Unique per user and per business account. Cannot be shared across organisations.<\/p>\n<\/div>\n<\/div>\n<p>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.<\/p>\n<p><strong>Important:<\/strong> the same user will have a different Scoped ID for your business than for another organisation. This prevents users from being tracked across companies.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">Communicating via a username instead of a phone number<\/h2>\n<p>MMeta is introducing the option for end users to communicate with businesses using a WhatsApp username. When an end user chooses this option:<\/p>\n<ul class=\"wp-block-list\">\n<li>The <strong>phone number is no longer shared<\/strong> with the business<\/li>\n<\/ul>\n<ul class=\"wp-block-list\">\n<li>The business receives a <strong>WhatsApp Business Scoped ID<\/strong> instead<\/li>\n<\/ul>\n<ul class=\"wp-block-list\">\n<li>The Scoped ID becomes the primary technical identifier for the conversation<\/li>\n<\/ul>\n<p>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.<\/p>\n<p>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 <em>and<\/em> the user has set a username will you receive only the Scoped ID.<\/p>\n<p><strong>Important:<\/strong> every WhatsApp user will receive a Scoped ID, even if they have not set a username. This means you will receive this ID regardless.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">Why is Meta introducing WhatsApp Business Scoped IDs?<\/h2>\n<p>Meta is introducing Scoped IDs and username-based communication for several key reasons:<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Stronger privacy protection<\/h4>\n<p>End users gain more control over how they share personal data, such as their phone numbers.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Clear separation between WhatsApp Business accounts<\/h4>\n<p>Identifiers are scoped per business account, preventing reuse across organisations.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">A future-proof foundation for WhatsApp<\/h4>\n<p>Scoped IDs and usernames enable WhatsApp to operate independently of phone numbers as the technical basis for identification.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">What is the impact on organisations?<\/h2>\n<p>The impact differs depending on the situation. It helps to distinguish between two scenarios.<\/p>\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column border1px-blue has-light-blue-background-color has-background is-layout-flow wp-block-column-is-layout-flow\">\n<h4 class=\"wp-block-heading has-text-align-center\">New customer via username<\/h4>\n<p class=\"has-text-align-center no-mar-bottom\">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.<\/p>\n<\/div>\n<div class=\"wp-block-column border1px-blue has-light-blue-background-color has-background is-layout-flow wp-block-column-is-layout-flow\">\n<h4 class=\"wp-block-heading has-text-align-center\">Existing customer with a phone number<\/h4>\n<p class=\"has-text-align-center no-mar-bottom\">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.<\/p>\n<\/div>\n<\/div>\n<p>The combination of Scoped IDs and username-based communication can have a significant impact, especially for organisations using WhatsApp at scale.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">CRM and CDP integrations<\/h4>\n<p>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.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Chatbot and automation flows<\/h4>\n<p>Workflows that expect a phone number as input may no longer function correctly and will require adjustment.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Customer recognition across channels<\/h4>\n<p>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.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Conversation history and reporting<\/h4>\n<p>Without proper support for Scoped IDs, conversations can become fragmented across different identifiers. This can lead to incomplete reporting or broken conversation timelines.<\/p>\n<p><strong>Tip:<\/strong> review your most important customer journeys as if phone numbers were no longer available. This will help identify dependencies before Meta rolls out usernames.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<div class=\"wp-block-group has-light-blue-background-color has-background\">\n<div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<h4 class=\"wp-block-heading\">Checklist: how to prepare your organisation for WhatsApp Business Scoped IDs<\/h4>\n<p>Want to understand what needs to change within your organisation? <a href=\"https:\/\/spotler.com\/en-au\/blog\/checklist-whatsapp-usernames\">Review this checklist and get started today<\/a>.<\/p>\n<\/div>\n<\/div>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">How is Spotler prepared?<\/h2>\n<p>Within Spotler Message and Spotler Engage, we have fully prepared our infrastructure for WhatsApp Business Scoped IDs ahead of Meta\u2019s announced rollout.<\/p>\n<p>Our readiness focuses on continuity, correct identification, handling, and data integrity.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading has-medium-font-size\">Native support for WhatsApp Business Scoped IDs<\/h4>\n<p>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.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Flexible conversation initiation<\/h4>\n<p>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.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Preserving conversation history and context<\/h4>\n<p>Existing conversations and message history remain intact.<\/p>\n<p>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.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Seamless integrations<\/h4>\n<p>Standard integrations that run through Spotler Message continue to function because the platform handles both phone numbers and Scoped IDs internally.<\/p>\n<p>Organisations with custom-built integrations that rely solely on phone numbers outside Spotler Message\u2019s identification logic may need to assess and adjust their implementation.<\/p>\n<div style=\"height:15px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h4 class=\"wp-block-heading\">Zero disruption during Meta\u2019s rollout<\/h4>\n<p>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.<\/p>\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<h2 class=\"wp-block-heading\">Ready for the new reality?<\/h2>\n<p>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.<\/p>\n<p>With Spotler Message and Spotler Engage, you are ready for this new reality.<\/p>\n<p>Want to understand what this specifically means for your CRM integration, chatbot flows or existing setup? <a href=\"https:\/\/spotler.com\/en-au\/blog\/checklist-whatsapp-usernames\" data-type=\"link\" data-id=\"https:\/\/spotler.com\/en-au\/blog\/checklist-whatsapp-usernames\">View our checklist<\/a> or <a href=\"https:\/\/spotler.com\/en-au\/sales\" data-type=\"page\" data-id=\"167156\">get in touch<\/a>, we will be happy to help.<a id=\"_msocom_1\"><\/a><\/p>\n<div class=\"button-block\">\n                                    <a class=\"btn ghost-btn\" href=\"https:\/\/spotler.com\/en-au\/sales\"><span>Contact us<\/span><\/a>\n                                        <\/div>\n","protected":false},"excerpt":{"rendered":"<p>Discover what WhatsApp Business Scoped IDs change and how Spotler Message ensures continuity during the rollout. <\/p>\n","protected":false},"author":80,"featured_media":233553,"template":"","cat_industry":[2668,2663],"cat_topic":[2670,2682],"class_list":["post-254202","blog","type-blog","status-publish","has-post-thumbnail","hentry","cat_industry-b2b-en-au","cat_industry-b2c-en-au","cat_topic-customer-service-en-int","cat_topic-whatsapp-marketing-en-au"],"acf":[],"_links":{"self":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/users\/80"}],"version-history":[{"count":2,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254202\/revisions"}],"predecessor-version":[{"id":254223,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254202\/revisions\/254223"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/media\/233553"}],"wp:attachment":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/media?parent=254202"}],"wp:term":[{"taxonomy":"cat_industry","embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/cat_industry?post=254202"},{"taxonomy":"cat_topic","embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/cat_topic?post=254202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}