A blank brown card luggage tag with a looped white string, lying on a plain white surface

CRM sync

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?

By The Tofu team ·

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.

As of November 2026.

What changed

BeforeNow
What a new lead shows youTheir phone numberTheir username, if they turned one on
Who can hide their numberNo oneAny WhatsApp user who sets a username (it's optional)
How webhooks identify the personPhone 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 APITo the phone numberTo the phone number or, from July 2026, the BSUID
Getting the numberIt came with every messageThe 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 ENT after the country code and arrive in webhooks as parent_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

  1. 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_id in contacts and as from_user_id on incoming messages. Match each chat on phone number when the webhook has one, and on BSUID when it doesn't.
  2. Handle number changes. When a user changes number, Meta sends a system message: user_changed_number if it can share the new number, user_changed_user_id if it can't. The old ID comes in previous_user_id. Use it to update the existing record instead of creating a duplicate.
  3. 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 with origin set to contact_request. For B2B, also ask for a work email. It's the field most likely to match an account already in your CRM.
  4. 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.
  5. 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.
  6. 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.
  7. 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

DateWhat happens
Early April 2026BSUIDs start appearing in webhooks, before users can set usernames
June 29, 2026WhatsApp opens username reservations and says usernames launch later in 2026. Businesses can reserve their business username too
Early July 2026The request contact info button becomes available, per Meta's changelog
July 2026Meta's APIs start supporting messages sent to BSUIDs
July 17, 2026MacRumors reports the first users getting notices that their usernames are active
The coming monthsUsernames 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

Let an agent build your next campaign.

Tofu Ads Agent reads your CRM, plans the funnel, builds the audience and creative, and stages full campaigns across LinkedIn, Google and Meta for your approval.