{"id":254193,"date":"2026-06-10T10:17:05","date_gmt":"2026-06-10T08:17:05","guid":{"rendered":"https:\/\/spotler.com\/blog\/checklist-whatsapp-usernames"},"modified":"2026-06-25T22:31:22","modified_gmt":"2026-06-25T20:31:22","slug":"checklist-whatsapp-usernames","status":"publish","type":"blog","link":"https:\/\/spotler.com\/en-au\/blog\/checklist-whatsapp-usernames","title":{"rendered":"Checklist: How to prepare your organisation for WhatsApp usernames\u00a0"},"content":{"rendered":"

WhatsApp is introducing usernames, making it easier for users to connect with businesses without sharing their phone number. To support this change, Meta uses Scoped IDs: unique identifiers that ensure conversations remain linked to the same user, even if that username changes over time. Want to understand exactly how this works? Read our blog.<\/a><\/strong><\/p>\n

Spotler Message and Spotler Engage are fully prepared for this change. Standard integrations will continue to work as usual, so no action is required from your side. The biggest impact isn’t on the platform itself, but on your internal processes, CRM connections, chatbot flows, and ways of working. This checklist helps you identify what may need to be adjusted within your organisation.<\/strong><\/p>\n

<\/div>\n

1. Map your dependencies on phone numbers<\/h2>\n

What to keep in mind<\/h4>\n

Soon, a WhatsApp user\u2019s phone number may no longer be automatically available. This affects things such as customer recognition, CRM integrations, routing, reporting and callback requests.<\/p>\n

What you can do<\/h4>\n

Identify where phone numbers are currently used in your processes and systems. For each dependency, determine what needs to change once phone numbers are no longer automatically available.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> Spotler Message and Spotler Engage already support Scoped IDs technically.<\/p>\n

<\/i> Do you use custom integrations, external systems or internal automations that rely on phone numbers? Check whether these will continue to function properly.<\/p>\n

<\/div>\n

2. Adjust your customer identification<\/h2>\n

What to keep in mind<\/h4>\n

If a customer contacts you using a username, you will not have a phone number available for lookup. This makes it harder to immediately recognise the customer or link them to an existing profile.<\/p>\n

What you can do<\/h4>\n

Determine which alternative data points you can use to identify customers, such as an email address, customer number, order number or a combination of identifiers. Update your processes accordingly.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> Spotler supports WhatsApp Scoped IDs as a primary identifier and links Scoped IDs to existing customer profiles, ensuring conversations and history remain intact.<\/p>\n

<\/i> Does your process ask for additional customer data for identification purposes? Check whether these steps still work when no phone number is available.<\/p>\n

<\/i> Do you use Call Deflection from telephony to WhatsApp? Verify whether employees and automated processes can still recognise and assist customers without a phone number. Where needed, request additional information during the WhatsApp conversation.<\/p>\n

<\/div>\n

3. Actively request contact details<\/h2>\n

What to keep in mind<\/h4>\n

If a customer requests a callback or another form of follow-up, you need a phone number. However, this may no longer be automatically available.<\/p>\n

What you can do<\/h4>\n

Update conversations, forms and chatbot flows so phone numbers are explicitly requested when needed.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> In many cases, this requires an adjustment to your own processes, chatbot flows, and work instructions. Spotler cannot display a phone number if a user chooses not to share it via WhatsApp.<\/p>\n

<\/i> To make it easier to request phone numbers from WhatsApp users, Meta has made an interactive button available: REQUEST_CONTACT_INFO<\/strong>. This button can be added to utility and marketing templates, or sent as an interactive message. When a user clicks this button, the WhatsApp phone number is shared in the conversation. In addition, a contacts webhook<\/strong> is triggered containing the user’s phone number. Note: If a WhatsApp user shares contact details using WhatsApp\u2019s Share Contact<\/em><\/strong> feature instead, the webhook will also include the shared contact\u2019s vCard<\/strong>.<\/p>\n

<\/div>\n

4. Review your chatbot and automation flows<\/h2>\n

What to keep in mind<\/h4>\n

Many chatbot dialogues and automated workflows still assume a phone number is available. Without one, flows may fail or behave incorrectly.<\/p>\n

What you can do<\/h4>\n

Review your automated processes and add steps where needed to request missing contact details or identification information.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> The Spotler infrastructure supports Scoped IDs, but the logic within your own chatbot or automation flows may need to be adjusted wherever they explicitly work with phone numbers.<\/p>\n

<\/div>\n

5. Check your CRM and system integrations<\/h2>\n

What to keep in mind<\/h4>\n

Many CRM systems use the phone number as unique identifiers to recognise customers or exchange data. If phone numbers are no longer consistently available, integrations may stop functioning correctly.<\/p>\n

What you can do<\/h4>\n

Check whether your integrations keep working without a phone number, and determine whether you need to use a different unique identifier, such as the Scoped ID.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> Standard integrations via Spotler Message and Spotler Engage will keep working. Spotler can process both phone numbers and Scoped IDs.<\/p>\n

<\/i> Do you have custom or external CRM integrations? Make sure to verify that these continue to function.<\/p>\n

<\/div>\n

6. Store the Scoped ID with every customer profile<\/h2>\n

What to keep in mind<\/h4>\n

Every WhatsApp user will soon receive a Scoped ID, even if that person hasn’t set a username. You’ll receive this ID as well.<\/p>\n

What you can do<\/h4>\n

Store the Scoped ID in each customer profile within your CRM. If a user later switches to a username and no longer shares a phone number, you’ll still be able to recognise that person and link them to the right profile.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i>  Spotler automatically receives and processes the Scoped ID and links it to the existing customer profile.<\/p>\n

<\/i> Do you store customer data in an external CRM or other system? Ensure the Scoped ID is also stored there as a dedicated field.<\/p>\n

<\/div>\n

7. Prevent duplicate customer profiles<\/h2>\n

What to keep in mind<\/h4>\n

If a phone number is missing, there’s a greater chance a customer won’t be automatically recognised and will instead be created as a new profile. This leads to duplicate records and messy data.<\/p>\n

What you can do<\/h4>\n

Take a critical look at how customer profiles are matched and add extra checks or enrichment steps where needed to maintain data quality.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> Spotler links new Scoped IDs to existing customer profiles if a phone number was previously available, so conversation history is preserved.<\/p>\n

<\/i> Do you use external data sources or systems outside Spotler for profile matching? Additional setup may be required.<\/p>\n

<\/div>\n

8. Check your verification and privacy processes<\/h2>\n

What to keep in mind<\/h4>\n

Some organisations use the phone number as a verification method before sharing account or personal data. If that number is no longer available, these processes may break down.<\/p>\n

What you can do<\/h4>\n

Determine which alternative verification methods are needed to safely identify customers.<\/p>\n

Hoe zit dat bij Spotler?<\/h4>\n

<\/i> This is outside the scope of what Spotler can support directly. If a user chooses not to share their phone number, alternative verification methods need to be put in place.<\/p>\n

<\/div>\n

9. Inform and train employees<\/h2>\n

What to keep in mind<\/h4>\n

Employees are used to customer information such as a phone number being automatically available. This will not always be the case going forward, requiring a different way of working.<\/p>\n

What you can do<\/h4>\n

Update work instructions, scripts and training so employees know what information to request and how to identify customers without a phone number.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> This is something your organisation needs to manage internally. Make sure employees understand how to act when only a username or Scoped ID is available.<\/p>\n

<\/div>\n

10. Check consent and opt-in processes<\/h2>\n

What to keep in mind<\/h4>\n

If a phone number is no longer automatically available, it can become harder to link a WhatsApp contact to existing marketing consents. This can affect how you register and manage consent.<\/p>\n

What you can do<\/h4>\n

Check whether your opt-in, consent, and preference management processes still function correctly when identification no longer relies on a phone number.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i> This depends on how your organisation manages consent registration. For many organisations, this is especially relevant in combination with CRM or marketing platforms.<\/p>\n

<\/div>\n

11. Test your WhatsApp customer journey without a phone number<\/h2>\n

What to keep in mind<\/h4>\n

Dependencies often only become visible when you actively walk through your processes. Everything may look fine on paper, but real-world behaviour can be different.<\/p>\n

What you can do<\/h4>\n

Walk through your key customer journeys as if no phone number were available and verify whether all processes, automations and follow-up actions still function properly.<\/p>\n

How does this work at Spotler?<\/h4>\n

<\/i>  Spotler Message and Spotler Engage are fully prepared for this change and require no migration or reconfiguration for customers using standard integrations.<\/p>\n

<\/i> We strongly recommend testing your own processes, CRM connections, and automations.<\/p>\n","protected":false},"excerpt":{"rendered":"

WhatsApp is replacing phone numbers with Scoped IDs. Use this checklist to check what your organisation needs to change.<\/p>\n","protected":false},"author":120,"featured_media":251475,"template":"","cat_industry":[],"cat_topic":[2682],"class_list":["post-254193","blog","type-blog","status-publish","has-post-thumbnail","hentry","cat_topic-whatsapp-marketing-en-au"],"acf":[],"_links":{"self":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254193","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\/120"}],"version-history":[{"count":2,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254193\/revisions"}],"predecessor-version":[{"id":254207,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/blog\/254193\/revisions\/254207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/media\/251475"}],"wp:attachment":[{"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/media?parent=254193"}],"wp:term":[{"taxonomy":"cat_industry","embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/cat_industry?post=254193"},{"taxonomy":"cat_topic","embeddable":true,"href":"https:\/\/spotler.com\/en-au\/wp-json\/wp\/v2\/cat_topic?post=254193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}