Updated 20 November 2026. Written for businesses and developers who use the WhatsApp Business Platform (Cloud API) directly or through a provider. Based on Meta's developer documentation and industry reports; check the latest docs before you change production code.
Short answer: WhatsApp is rolling out usernames, which let people chat without showing their phone number. To make that work for businesses, Meta added a business-scoped user ID (BSUID) to API webhooks. According to Meta's BSUID documentation, BSUIDs began appearing in webhooks in early April 2026, and when a customer has a username their phone number can be missing from the webhook. If your CRM, chatbot or order system identifies customers only by phone number, it needs an update.
What are WhatsApp usernames?
A username is an optional handle a person or business can set instead of sharing a phone number. Meta says usernames roll out gradually during 2026. Businesses could reserve a username from 29 June 2026 through WhatsApp Manager, Meta Business Suite or the Username API, and a reserved name stays pending until the feature is live in that region. WABetaInfo reported that users are told in the app when usernames become available in their country.
Meta has not published a country-by-country launch list in its developer docs, and we could not find an official launch date for India. Treat it as something that can switch on at any time and prepare now.
Business username rules
Per Meta's docs, a business username:
- uses only lowercase letters a to z, digits, periods and underscores, and must contain at least one letter;
- is 3 to 35 characters long, with no leading or trailing period and no double period;
- cannot start with "www." or end in a domain such as ".com";
- maps to one business phone number. If the name is already used on your linked Facebook Page or Instagram account, you need to link those assets first.
What is a BSUID?
A BSUID is an ID WhatsApp gives a customer that is unique to your business portfolio. It starts with a two-letter country code and a period, followed by a long alphanumeric string. Important points from Meta's documentation:
- It is the same for that customer across the phone numbers in your portfolio, but a different business sees a different ID.
- It is regenerated if the customer changes their phone number. WhatsApp sends a system message with the previous ID so you can join the two records.
- It appears in incoming message webhooks (as
user_id/from_user_id) and in status webhooks, whether or not the customer has a username.
When will the phone number be missing?
This is the change that breaks systems. Meta says that if a customer has adopted a username, the phone number is left out of webhooks unless:
- your business phone number messaged or called them in the last 30 days;
- they messaged or called your business number in the last 30 days; or
- they are in your WhatsApp contact book, a Meta-hosted store of phone-to-BSUID mappings created from your interactions.
The 30-day check is per business phone number. Meta also says the contact book only captures interactions after it launched; older chats are not added backwards. So a customer who last spoke to you a year ago and has since set a username may reach you with a BSUID only.
Sending messages to a BSUID
Meta added support for sending to BSUIDs in July 2026. In the messages API you pass the BSUID in a recipient field instead of the phone number in to; if both are present, the phone number wins. Two limits matter for Indian businesses:
- OTP and login messages: one-tap, zero-tap and copy-code authentication templates still need a phone number. If your login, KYC or payment confirmation flow sends OTPs on WhatsApp, keep the phone number as the key for that flow.
- Marketing: the Marketing Messages API accepts BSUIDs, but Meta still recommends phone numbers where you have them.
To get a number when you need one, Meta added a request contact info button that can be used in utility and marketing templates or as an interactive message. If the customer taps it, a webhook returns their phone number.
Checklist for your CRM, chatbot and order system
- Store the BSUID on every contact record, next to the phone number. Make the phone field optional in your database and webhook parser so a missing number does not crash the handler.
- Match in order: look up the BSUID first, then the phone number. Create a new lead only if both fail.
- Handle ID changes: listen for the system message that carries the previous ID and merge the two records.
- Keep OTP flows on phone numbers and test what happens when a username-only customer asks for an OTP. Use the request contact info button to collect the number with consent.
- Review opt-ins: your marketing consent records should link to the BSUID as well as the phone number, so an opt-out is honoured whichever ID arrives.
- Check your provider: if you use a BSP or a no-code inbox, ask whether it already stores BSUIDs and supports sending by
recipient. Vendors such as Splashify Pro advise keeping phone-number sending as the default until your provider confirms BSUID support. - Reserve your username now, so customers can find the real brand and not a lookalike.
What does not change
Template approval, the 24-hour customer service window and pricing work as before. Service conversations and their costs are covered in our post on WhatsApp Business API service message charges. If you are new to the platform, start with what the WhatsApp Business API is.
Need help updating your integration?
Nextinera builds WhatsApp integrations, CRMs and order systems for Indian businesses. We can add BSUID storage, safe matching and username-aware chatbot flows to your existing setup. See our API development and integration and CRM development services, or book a free call.