Explore all articles
A BSUID (Business-Scoped User ID) is a unique code that WhatsApp auto-generates for every user–business pair. It replaces phone numbers as the primary identifier when users enable the username feature. Each business gets a different BSUID for the same user, preventing cross-business tracking.
BSUIDs start appearing in production webhooks on March 31, 2026. However, businesses won't be able to send messages using BSUIDs until May 2026. Usernames become available to all users later in 2026.
If your system can't handle BSUIDs, messages from username-enabled users may break your integrations. Meta has stated there is no recourse or corrective action for unprepared businesses.
Yes. Phone numbers continue to work for users who haven't adopted usernames, and for users whose phone numbers are available through the 30-day lookback or contact book. You can include both a phone number and BSUID in the same API request — the phone number takes priority.
No. Changing a username does not affect the BSUID. BSUIDs only change when a user changes their phone number. When this happens, businesses receive a user_id_update webhook with the old and new BSUIDs.
One-tap authentication templates, zero-tap authentication templates, and copy code authentication templates still require the user's phone number. All other message types — text, media, templates, interactive — work with BSUIDs.
WhatsApp is introducing usernames and Business-Scoped User IDs (BSUIDs) in 2026. Users can set a username (like @yourname) to hide their phone number from businesses. Businesses will receive a unique BSUID for each customer instead. BSUIDs start appearing in webhooks on March 31, 2026, and become usable for sending messages in May 2026.
A WhatsApp username is an optional, unique handle (like @sarah_designs) that any WhatsApp user can set. Once enabled, businesses see the username instead of the user's phone number. Usernames follow the same format as Instagram handles and are launching later in 2026.
Think of it like picking a display name for a game — except this one protects your phone number from every business you message on WhatsApp.
WhatsApp usernames must be 3–35 characters long, contain only English letters (a–z), numbers (0–9), periods (.), and underscores (_), include at least one letter, and cannot start/end with a period, contain consecutive periods, start with "www," or end with a domain extension like .com.
One important detail: capitalization doesn't matter (MyName and myname are the same), but periods and underscores do (my.name and my_name are different usernames).
A BSUID (Business-Scoped User ID) is a unique identifier that WhatsApp automatically generates for every user–business pair. It looks like US.13491208655302741918 — a country code prefix followed by up to 128 alphanumeric characters. BSUIDs replace phone numbers as the primary way businesses identify WhatsApp users who enable usernames.
Here's the key concept: if you message three different businesses on WhatsApp, each business gets a different BSUID for you. Business A cannot use their BSUID to figure out that you also talk to Business B. Your identity stays compartmentalized.
A BSUID like US.13491208655302741918 has three parts:
Here's how a BSUID compares to a traditional phone number:
A parent BSUID is an additional cross-portfolio identifier for companies with multiple linked business portfolios. It looks like US.ENT.11815799212886844830 (note the ENT prefix) and works across all linked portfolios, solving the problem of different BSUIDs per portfolio for the same customer.
To enable parent BSUIDs, you must contact your Meta point of contact and check eligibility. Once your portfolios are linked, parent BSUIDs automatically appear in webhooks via a new parent_user_id field.
Key difference: A regular BSUID is scoped to one portfolio. A parent BSUID (format: US.ENT.xxxxx) works across all linked portfolios. Parent BSUIDs require Meta approval and are designed for companies managing multiple business portfolios.
The WhatsApp contact book is a Meta-hosted feature launching in early April 2026 that automatically stores user phone numbers and BSUIDs whenever a business and user interact. It requires no integration work and is scoped to the business portfolio level.
Starting in early May 2026, businesses can add a REQUEST_CONTACT_INFO button to utility and marketing message templates. When a user taps this button, their phone number and virtual contact card (vCard) are shared with the business via a contacts webhook.
The button can't be customized — it's a standard WhatsApp element. Not every user will tap it, so design your flows to work with or without a phone number.
WhatsApp Business usernames are optional, unique handles that businesses can adopt. Unlike user usernames, business usernames do NOT hide the business's phone number. They make businesses searchable by exact username on WhatsApp — something display names don't support.
The WhatsApp Business API now supports two addressing fields: "to" (phone number) and "recipient" (BSUID or parent BSUID). All webhook types include new user_id, parent_user_id, and username fields, while phone number fields like wa_id may be omitted for username-enabled users.
The WhatsApp username and BSUID rollout is one of the most significant changes to the WhatsApp Business Platform in years. At Gallabox, we're building native BSUID support directly into our platform — seamless transition for your team, unified customer profiles, and built-in phone number request flows.
WhatsApp is introducing usernames and Business-Scoped User IDs (BSUIDs) in 2026. Users can set a username (like @yourname) to hide their phone number from businesses. Businesses will receive a unique BSUID for each customer instead. BSUIDs start appearing in webhooks on March 31, 2026, and become usable for sending messages in May 2026.
A WhatsApp username is an optional, unique handle (like @sarah_designs) that any WhatsApp user can set. Once enabled, businesses see the username instead of the user's phone number. Usernames follow the same format as Instagram handles and are launching later in 2026.
Think of it like picking a display name for a game — except this one protects your phone number from every business you message on WhatsApp.
WhatsApp usernames must be 3–35 characters long, contain only English letters (a–z), numbers (0–9), periods (.), and underscores (_), include at least one letter, and cannot start/end with a period, contain consecutive periods, start with "www," or end with a domain extension like .com.
One important detail: capitalization doesn't matter (MyName and myname are the same), but periods and underscores do (my.name and my_name are different usernames).
A BSUID (Business-Scoped User ID) is a unique identifier that WhatsApp automatically generates for every user–business pair. It looks like US.13491208655302741918 — a country code prefix followed by up to 128 alphanumeric characters. BSUIDs replace phone numbers as the primary way businesses identify WhatsApp users who enable usernames.
Here's the key concept: if you message three different businesses on WhatsApp, each business gets a different BSUID for you. Business A cannot use their BSUID to figure out that you also talk to Business B. Your identity stays compartmentalized.
A BSUID like US.13491208655302741918 has three parts:
Here's how a BSUID compares to a traditional phone number:
A parent BSUID is an additional cross-portfolio identifier for companies with multiple linked business portfolios. It looks like US.ENT.11815799212886844830 (note the ENT prefix) and works across all linked portfolios, solving the problem of different BSUIDs per portfolio for the same customer.
To enable parent BSUIDs, you must contact your Meta point of contact and check eligibility. Once your portfolios are linked, parent BSUIDs automatically appear in webhooks via a new parent_user_id field.
Key difference: A regular BSUID is scoped to one portfolio. A parent BSUID (format: US.ENT.xxxxx) works across all linked portfolios. Parent BSUIDs require Meta approval and are designed for companies managing multiple business portfolios.
The WhatsApp contact book is a Meta-hosted feature launching in early April 2026 that automatically stores user phone numbers and BSUIDs whenever a business and user interact. It requires no integration work and is scoped to the business portfolio level.
Starting in early May 2026, businesses can add a REQUEST_CONTACT_INFO button to utility and marketing message templates. When a user taps this button, their phone number and virtual contact card (vCard) are shared with the business via a contacts webhook.
The button can't be customized — it's a standard WhatsApp element. Not every user will tap it, so design your flows to work with or without a phone number.
WhatsApp Business usernames are optional, unique handles that businesses can adopt. Unlike user usernames, business usernames do NOT hide the business's phone number. They make businesses searchable by exact username on WhatsApp — something display names don't support.
The WhatsApp Business API now supports two addressing fields: "to" (phone number) and "recipient" (BSUID or parent BSUID). All webhook types include new user_id, parent_user_id, and username fields, while phone number fields like wa_id may be omitted for username-enabled users.
The WhatsApp username and BSUID rollout is one of the most significant changes to the WhatsApp Business Platform in years. At Gallabox, we're building native BSUID support directly into our platform — seamless transition for your team, unified customer profiles, and built-in phone number request flows.
Take Gallabox for a 7-day ride