WhatsApp now lets people hide their phone number behind a username. How do I follow up and match click-to-WhatsApp leads in our CRM?
WhatsApp opened username reservations on June 29, 2026 and is turning usernames on by country; MacRumors reported the first ones active on July 17. When someone with a username messages you first, you see the username, not their number. API webhooks then carry a business-scoped user ID (BSUID) instead, unless you and that number exchanged messages or calls in the last 30 days, or it's in your contact book. Meta says click-to-WhatsApp advertisers must support BSUIDs, and its APIs send to them from July 2026. Match CRM records on the BSUID and ask for contact details in the chat.
Ask Tofu next
Pick a question and Tofu Ads Agent answers it in chat.
- Which of my click-to-WhatsApp leads came in without a phone number last month?
- Map WhatsApp BSUIDs to contacts in HubSpot for leads from my click-to-WhatsApp ads
- Write a WhatsApp utility template that asks a new lead for their work email
- Do I need parent BSUIDs if our WhatsApp numbers sit in two business portfolios?
- How do I send qualified WhatsApp chats back to Meta as lead events?
As of November 2026.
What changed
| Before | Now | |
|---|---|---|
| What a new lead shows you | Their phone number | Their username, if they turned one on |
| Who can hide their number | No one | Any WhatsApp user who sets a username (it's optional) |
| How webhooks identify the person | Phone number (wa_id) | A BSUID in user_id, in every messages webhook. Phone fields are left out for username users, with two exceptions |
| Replying through the API | To the phone number | To the phone number or, from July 2026, the BSUID |
| Getting the number | It came with every message | The person shares it, for example with a request contact info button |
The two exceptions, per Meta's developer guide:
- Recent contact. You messaged or called that number, or got a message or call from it, in the last 30 days. Meta checks this per business phone number.
- Your contact book. The number is in your contact book, which Meta hosts and fills as you message or call numbers, or hear from them.
A BSUID looks like US.13491208655302741918: a two-letter country code, a period, then up to 128 letters and numbers. It's scoped to your business portfolio, so a phone number in another portfolio can't message it. It's "regenerated if a user changes their phone number."
Who it affects
- Businesses on the WhatsApp Business Platform, directly or through a partner. Meta says "supporting business-scoped user IDs (BSUID) is required for all partners and directly-integrated businesses," and it names click-to-WhatsApp advertisers too. Its reason: "you cannot control whether your users adopt usernames," and you must support BSUIDs "to avoid losing the ability to process their messages."
- Teams on the WhatsApp Business app. Meta's announcement says that when someone messages a person or business for the first time, "they will no longer see your phone number, if you enabled your username." The developer guide covers the API, so it doesn't say how the app shows these leads beyond that.
- Agencies and companies with several portfolios. The same person gets a different BSUID in each portfolio. Meta offers parent BSUIDs, which any business phone number in a set of enrolled portfolios can use. They include
ENTafter the country code and arrive in webhooks asparent_user_id. Managed businesses ask their Meta contact whether their portfolios are eligible. - Who can ignore it. People who don't set a username, numbers you've talked to in the last 30 days, and numbers in your contact book still come with a phone number. Instant Form leads aren't part of this change. Meta's docs on usernames are about WhatsApp only and don't mention Messenger.
What to do now
- Add a BSUID field to your CRM. Store the full ID with its country code and period; Meta says BSUIDs must be sent in full. The ID arrives as
user_idincontactsand asfrom_user_idon incoming messages. Match each chat on phone number when the webhook has one, and on BSUID when it doesn't. - Handle number changes. When a user changes number, Meta sends a system message:
user_changed_numberif it can share the new number,user_changed_user_idif it can't. The old ID comes inprevious_user_id. Use it to update the existing record instead of creating a duplicate. - Ask for contact details in the chat. Meta's request contact info button (
REQUEST_CONTACT_INFO) goes in utility or marketing templates, or in an interactive message. If the person taps it, "their WhatsApp phone number will be shared in the message thread," and you get a contacts webhook withoriginset tocontact_request. For B2B, also ask for a work email. It's the field most likely to match an account already in your CRM. - Keep your contact book on. Meta says "the contact book is provided and hosted by Meta; no integration work is required," and it uses it to put phone numbers back into webhooks. You can turn it off in Business info in Meta Business Suite's Business settings, but that deletes the stored data. Meta's Contact Book API can check whether a number is in it.
- Reply by BSUID when you have no number. Meta says BSUIDs can be used to send any type of message except one-tap, zero-tap and copy-code authentication templates. For marketing messages, Meta says "sending messages to phone numbers is recommended." For what follow-ups cost and where marketing messages now go, see service message charges for click-to-WhatsApp leads and marketing messages leaving the Cloud API.
- Check every tool that touches the chat. Ask your WhatsApp partner, CRM connector and any AI agent you use (such as Meta's Business Agent) whether they store and send by BSUID. A tool that keys only on phone numbers can lose username leads or create duplicates.
- Keep ad feedback separate. Telling Meta which chats became qualified leads is a different job, done through the Conversions API for Business Messaging. See how to tell Meta which chats turned into qualified B2B leads.
Dates to watch
| Date | What happens |
|---|---|
| Early April 2026 | BSUIDs start appearing in webhooks, before users can set usernames |
| June 29, 2026 | WhatsApp opens username reservations and says usernames launch later in 2026. Businesses can reserve their business username too |
| Early July 2026 | The request contact info button becomes available, per Meta's changelog |
| July 2026 | Meta's APIs start supporting messages sent to BSUIDs |
| July 17, 2026 | MacRumors reports the first users getting notices that their usernames are active |
| The coming months | Usernames reach more countries. WhatsApp says it will notify people when they're available in their country |
Meta's developer guide keeps changing: its changelog has entries from August 11, August 24, September 15, October 23 and November 5, 2026. Check it before you build.
Sources
- It's Time to Reserve Your WhatsApp Username (Meta Newsroom, June 29, 2026), checked November 8, 2026
- Business-scoped user IDs (Meta for Developers), checked November 8, 2026
- WhatsApp Begins Rolling Out New Username Feature (MacRumors, July 17, 2026), checked November 8, 2026