WhatsApp usernames and BSUIDs: what changes for businesses
WhatsApp usernames let a person be found and messaged by a chosen handle instead of their phone number, and a Business-Scoped User ID (BSUID) is the identifier Meta can give a business for that same person when the phone number itself is not shared. Together they mean a contact's identity is no longer guaranteed to be a phone number.
- A WhatsApp username is a chosen handle a person can be contacted through, similar in spirit to an Instagram or Telegram handle.
- A BSUID (Business-Scoped User ID) is an identifier tied to one specific business, used when a customer's real phone number is not exposed.
- Usernames can be changed by the person who owns them; a phone number historically has not been treated as changeable in the same casual way.
- CRMs and bots built assuming 'phone number = unique customer' need to also store BSUID or username as a valid identity.
- Support for usernames and BSUIDs is rolling out gradually — treat this as an evolving area of WhatsApp Business, not a finished standard.
The definitions
A WhatsApp username is a handle a person can choose, similar to an Instagram or Telegram username, that others can use to find and message them without needing to know their actual phone number. A BSUID (Business-Scoped User ID) is a separate concept: an identifier Meta can hand a specific business to represent one customer, used in situations where that customer's real phone number is deliberately not shared with the business.
Both changes point the same direction: WhatsApp is moving away from treating a phone number as the only possible way to identify and reach someone on the platform.
It helps to keep the two concepts separate in your head: a username is something the customer chooses and controls, the way they present themselves to any business on WhatsApp. A BSUID, by contrast, is generated behind the scenes and is specific to the relationship between one customer and one business, it is not something the customer sees or manages directly. A username can also, in principle, change hands or be updated by its owner at any time, while a BSUID is generated and controlled entirely by WhatsApp's own systems.
Why Meta is doing this
A phone number is personal and permanent in a way many people are increasingly uncomfortable handing to every business they message. A username gives people a way to be reachable on WhatsApp without exposing that number to a stranger or a company, the same trade-off already familiar from Instagram, Telegram or a work email alias versus a personal one.
For businesses, this mirrors a broader trend already visible on other channels: a growing share of contacts will be reachable but not necessarily fully phone-number-identified, and systems built around the old assumption need to adapt.
Why this matters for an Indian business specifically
Indian businesses have historically leaned on the phone number more heavily than most: it doubles as the customer record key in the CRM, the identifier used for order lookups, and often the same number used for a call, an SMS reminder and a WhatsApp message to the same person. That convenience was only possible because a number was assumed to be shared freely and to stay stable over time.
As younger, more privacy-conscious customers start reaching businesses through a username rather than a shared number, a business whose entire system is wired around "phone number as primary key" risks quietly losing the ability to recognise a returning customer, tie their WhatsApp conversation to a past order, or send them anything outside that one chat thread.
Phone number identity vs username/BSUID identity
| Phone number | Username / BSUID | |
|---|---|---|
| Typically stable | Rarely changes | A username can be changed by its owner |
| Reveals personal number | Yes | Not necessarily |
| Works as a CRM unique key | Traditionally yes | Only if your CRM also tracks it |
| Familiar to businesses | Yes, the long-standing default | New, still rolling out |
What this changes for your CRM and bot
Most WhatsApp bots and CRMs were built assuming a phone number is both the way to message someone and the permanent key that identifies them as "the same contact" across every visit. As usernames and BSUIDs become more common, that assumption weakens on two fronts: the identifier you message someone through is not always their number, and a username, unlike a number, can be changed by the person who owns it.
Practically, this means your contact records should be able to store more than one identity field for the same person, and your team should not assume "same phone number means same customer" is the only reliable match going forward.
It is also worth checking how your existing broadcasts, campaigns and reminder flows reference contacts, a flow or report built assuming every contact row has a usable phone number field may need a fallback path for contacts identified only by a username or BSUID.
Common mistakes
- Treating a username as permanent: unlike a number, it can be changed, so do not use it as the sole long-term key for a customer record without a fallback.
- Assuming every contact still has a visible number: some conversations will only expose a BSUID, and flows that hard-code logic around a phone-number field will break for those contacts.
- Ignoring the change until it is forced: since rollout is gradual, it is easy to assume this does not affect you yet, but CRM fields and flow logic are easier to widen early than to retrofit later.
How it shows up in Convo360
Convo360's Contacts & CRM support storing a contact's WhatsApp identity alongside custom fields, so a business can keep both a phone number (where available) and a username or BSUID against the same customer record without losing conversation history. As Meta expands username and BSUID support, including for AI voice calls over WhatsApp, this identity flexibility carries through the same Flow Builder and system variables you already use — check Meta's WhatsApp Business Platform documentation for the current state of rollout in your region. Because Convo360's flow logic references a contact record rather than assuming a raw phone number string, flows built today are already positioned to keep working as more customers arrive identified only by a username or BSUID.
Example conversation
Manage every contact identity in one CRM
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can I message a customer on WhatsApp if I only have their username, not their number?
If the customer has messaged your business through their username, you can continue that conversation using the identifier WhatsApp provides, without necessarily knowing their underlying phone number.
Is a BSUID the same for a customer across every business they message?
No, a Business-Scoped User ID is specific to one business's relationship with that customer, not a single global identifier usable across every business on WhatsApp.
Do I need to change my CRM immediately because of usernames?
Not urgently, since rollout is gradual, but it is worth checking that your contact records and flow logic can handle an identity that is not a phone number before it becomes common among your customers.
Can a customer have both a phone number and a username visible to my business?
Yes, this is common — many customers will still share their number as before, with usernames and BSUIDs applying mainly to customers who deliberately choose not to expose it.
Does this affect WhatsApp templates or the 24-hour window?
No, template rules and the customer-service window are governed by the conversation itself, not by which identifier was used to start it, so your existing template approvals and messaging limits are unaffected.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.