WhatsApp BSUID for Businesses: What Breaks, What Changes & Your Step-by-Step Preparation Guide

Starting March 31, 2026, WhatsApp webhooks include a new Business-Scoped User ID (BSUID) for every user. When users adopt usernames (later in 2026), their phone numbers may no longer appear in webhooks. Businesses must update webhook handlers, CRMs, and messaging logic to support BSUIDs before May 2026, or risk breaking customer conversations.

Why Should Businesses Care About WhatsApp BSUIDs?

Today, every WhatsApp webhook includes the user's phone number. Once users adopt usernames, phone numbers may be omitted. If your systems expect phone numbers and can't handle BSUIDs, incoming messages will break your integrations. Meta has stated there is no recourse for unprepared businesses.

Your CRM, chatbots, marketing automations, analytics — they all rely on phone numbers as the primary customer identifier. That foundation is about to shift.

Critical warning from Meta: "If you have not yet adopted BSUID and are not able to process messages from username adopters, there will not be any recourse or corrective action that you can take."

What Is a WhatsApp BSUID?

A BSUID (Business-Scoped User ID) is a unique identifier auto-generated by WhatsApp for every user–business portfolio pair. It looks like US.13491208655302741918 and replaces phone numbers as the primary identifier when users enable usernames. Each business gets a different BSUID for the same user.

How Is WhatsApp BSUID Different from a Phone Number?

What Breaks If Your Business Is Not Ready for WhatsApp BSUIDs?

• Webhook handlers crash. If your code expects a phone number in the wa_id field and it's missing, your system fails to process the message.
• CRM records break. If your CRM uses phone numbers as primary keys, messages from username adopters create orphan conversations that can't be linked to existing customers.
• You can't reply to new customers. After May 2026, if you haven't updated your send logic to support BSUIDs, you can't respond to users who didn't share their phone number.
• Chatbots and automations fail silently. Any workflow triggered by phone number matching won't fire for BSUID-only contacts.
• Marketing campaigns miss recipients. Campaign tools relying on phone numbers won't reach username adopters.

When Will Businesses Still Receive Phone Numbers in Webhooks?

Even for username-enabled users, phone numbers appear in webhooks if: (1) you've exchanged messages or calls with the user's phone number in the last 30 days (per business phone number, not portfolio-wide), or (2) the user is stored in your Meta-hosted contact book. For everyone else — especially brand-new customers — you'll only have their BSUID.

What Is the WhatsApp Contact Book and How Does It Help?

The WhatsApp contact book is a Meta-hosted feature (launching early April 2026) that automatically stores user phone numbers and BSUIDs whenever your business interacts with a user. It requires no integration work and acts as a safety net for maintaining phone number access.

• No setup needed. Meta hosts it automatically.
• Only captures post-launch interactions. No retroactive data from before April 2026.
• Portfolio-scoped. Not shared across linked portfolios.
• Can be disabled in Meta Business Suite. But disabling permanently deletes all stored data.

Tip: Keep the contact book enabled (it's on by default). It's your best safety net for maintaining phone number access as users adopt usernames.

How to Request Phone Numbers from WhatsApp Users

From early May 2026, add a REQUEST_CONTACT_INFO button to utility and marketing message templates. When a user taps it, their phone number and vCard are shared via a contacts webhook. The button is non-customizable and sharing is entirely the user's choice. Design for BSUID-first: not every user will tap the button. Your flows must work with or without a phone number.

What Changes in the WhatsApp Business API?

The API adds a "recipient" field (BSUID) alongside "to" (phone number) for sending messages. All webhooks now include user_id (BSUID), optional parent_user_id and username fields. Phone number fields may be omitted for username-enabled users. Two new webhook types are added:

• user_id_update — fires when a customer's BSUID changes (phone number change). Includes old and new BSUIDs.
• business_username_update — fires when your business username status changes (approved, reserved, or deleted).

WhatsApp BSUID Timeline: What to Do and When

• Now: Test BSUIDs available in App Dashboard. Update webhook handlers and test all 4 scenarios.
• March 31, 2026: BSUIDs in production webhooks. Ensure production systems handle new fields.
• Early April 2026: Contact book launches. Verify it's enabled and capturing interactions.
• Early May 2026: Phone number request button available. Add REQUEST_CONTACT_INFO to key templates.
• May 2026: APIs accept BSUIDs for sending. Update send logic to support BSUID messaging.
• Later 2026: Usernames go live. Monitor adoption and expect more BSUID-only webhooks.

How to Prepare for WhatsApp BSUIDs: Step-by-Step Checklist

Priority 1: Webhook Handling (Do This Now)

• Update webhook parsers to read user_id, parent_user_id, and username fields.
• Handle missing wa_id and from fields gracefully — don't crash if phone number is absent.
• Subscribe your apps to user_id_update and business_username_update webhooks.
• Test all 4 scenarios in the App Dashboard webhook testing tool.

Priority 2: CRM and Database Updates

• Add BSUID as a customer identifier in your CRM or database.
• Add parent BSUID field if you use multiple linked portfolios.
• Build logic to link BSUIDs to existing phone-number-based records when both are present.
• Handle BSUID changes (user_id_update webhook) by updating customer records.

Priority 3: Messaging and Conversation Flows

• Update send message logic to support the new recipient field (BSUID) alongside to (phone number).
• Add REQUEST_CONTACT_INFO buttons to key message templates (available May 2026).
• Design conversation journeys that work even if the user doesn't share their phone number.
• Update chatbot flows to handle BSUID-only customer identification.

Priority 4: Business Username and Cross-Portfolio Setup

• Check for reserved username suggestions in WhatsApp Manager or Meta Business Suite.
• Claim your preferred business username.
• If you have multiple portfolios, contact Meta about linking them for parent BSUIDs.
• Keep the contact book feature enabled (default setting).

How Gallabox Helps You Prepare for WhatsApp BSUIDs

At Gallabox, we're building native BSUID support directly into our WhatsApp Business Platform — seamless transition for your team, unified customer profiles, built-in phone number request flows, and multi-portfolio support to manage parent BSUIDs across linked portfolios from a single dashboard.