WhatsApp Username vs. Business Phone Number

Last updated: July 2026

TL;DR

• A WhatsApp username is a public handle customers use to find and message you without seeing your phone number. A phone number is still what identifies you inside WhatsApp's system.
• On personal accounts, the username replaces the visible phone number. On business accounts, both show side by side.
• Use both in your marketing. New links use the username; existing links using your phone number keep working. There's no reason to break what already ranks or gets shared.
• On the backend, the change is bigger. Your CRM, AI assistant, and automations should identify customers by BSUID (Business-Scoped User ID) rather than only by phone number, because a growing share of customers will message you with their number hidden.

Username or phone number is not really a choice. WhatsApp uses both, layered on top of each other, and each has a role. Below is what changes, what stays the same, and what your team should actually do.

The short version: they do different things

A WhatsApp business phone number is what identifies your account inside WhatsApp's platform. It is how Meta bills you, how BSPs route your messages, and how your account is authenticated. It is the primary key of your presence on the platform.

A WhatsApp business username is a public-facing handle that customers use to find you. It sits on top of your phone number. It does not replace it, and on business accounts, it does not hide it either.

For customers, the username is easier to share, easier to remember, and does not expose them or you to unwanted number swapping. For your systems, the phone number is still what most infrastructure was built around, and the username is a new layer that arrives with a new identifier (BSUID) attached.

Both are part of every business account. The question is not which one to have. It is how to use each of them well.

Side-by-side comparison

The two identities, side by side. Same account, different jobs.

Two things the diagram compresses that are worth spelling out:

• What it is. Your phone number is the primary key of your account inside WhatsApp's platform. Your username is a public-facing handle that sits on top. The number is what Meta bills, routes, and authenticates against; the username is what customers see and share.
• What breaks if you change it. Changing your phone number requires an account migration and re-verification, and any existing chat or wa.me/PHONE link breaks. Changing your username is free and takes seconds, but old @handle links stop working during a cooldown period.

When to use each

Both are yours. Different situations call for different formats.

Use your phone number when...

• A customer has your number saved. Do not push them to a username they will have to look up.
• You are already listed by phone on Google Business Profile, Instagram, or Facebook. Add the username; do not remove the number.
• A partner integration or CRM was built around your number and your team is confident BSUID handling is not yet complete.
• You appear in printed materials (menus, business cards, signage). Adding a QR code beside the number is easier than reprinting everything.
• A customer clicks a click-to-WhatsApp ad. wa.me/PHONE links have been around forever and work everywhere.

Use your username when...

• You are updating public-facing materials for the first time (website, social bio, new campaign).
• A customer is finding you for the first time. A short handle beats a phone number for memorability.
• You want to signal that you are on a modern, actively-maintained WhatsApp presence. A @brava.cosmetics handle in an ad feels current in a way a phone number does not.
• You are running international ad creative. A single handle works in every country. A phone number invites "is that a US number I have to pay to text?" hesitation.
• You care about brand consistency across channels. If your Instagram is @brava.cosmetics, so should your WhatsApp be.

Use both when...

Almost always. The two do not compete. Add the username as the new default, keep the phone number alive, and let the customer pick what feels natural to them.

What changes on the backend (this is where mistakes happen)

Setting a username takes minutes. Making sure your automations keep working takes longer.

The biggest shift: your systems can no longer assume a customer's identity equals their phone number. As username adoption grows, incoming messages will increasingly arrive without a phone number in the webhook. What is always present, per Meta's developer documentation, is a BSUID (Business-Scoped User ID) in the user_id field. That is the identifier your systems need to be built around.

The "business-scoped" part is literal: a BSUID is unique per user AND per Meta business portfolio pair. Your business portfolio is the entity you set up in Meta Business Manager, and each WhatsApp Business account belongs to one. The same customer will have a different BSUID for a different business's portfolio, which is why the identifier stays private and can't be used to track a person across companies.

A Meta business portfolio is the scoping unit for BSUID. Each portfolio has its own numeric ID and its own set of BSUIDs for the customers who message it.

The knock-on effects:

• CRMs keyed only on phone number will start creating duplicate records when a customer whose number they previously had shows up with a username-only message.
• Ticketing systems will lose the conversation thread if they were merging conversations by phone.
• AI assistants that identify customers by phone number will greet returning customers as brand new.
• Analytics that segment by phone will double-count when the same person messages you with and without their number visible.

The fix is the same in every case: treat BSUID as the primary key, treat phone number as a nice-to-have secondary attribute. Full technical walkthrough is in our WhatsApp Usernames Explained guide.

When you will still see a phone number

The BSUID is always in the webhook. The phone number only appears in three specific cases, none of which are guaranteed to keep happening as username adoption grows.

The three cases where the phone number still comes through, plus the one rule that saves your integration from breaking: never assume it will be there.

Even after a customer sets a username, they get to decide who can reach them by handle. The Contact me by username control in their WhatsApp settings has two states, and the choice affects whether their number stays visible to the businesses they interact with.

The customer-side privacy control that determines how they can be reached by username, and by extension how visible their phone number stays.

Once a customer sets a username, their phone number (wa_id) only appears in webhooks under specific conditions:

• The customer has not enabled the username feature yet. Their phone number comes through as before.
• The customer explicitly shared their number via WhatsApp's contact sharing.
• The customer is calling from a saved contact of yours already.
• The customer tapped the new "request phone number" CTA and consented to share. In this case the phone number gets added to your contact book and comes through in webhooks. Meta added this button so businesses can still ask for the number when they need it, with the user in control of whether to share.

Outside those conditions, expect BSUID and no phone number.

Edge case: the BSUID can change

If a customer's phone number changes (they got a new SIM, ported their number, or otherwise re-authenticated with a different phone), their BSUID changes too. Meta ships a dedicated system webhook to notify you when this happens. If your integration doesn't subscribe and update, messages sent to the old BSUID will fail.

For most SMBs on a managed WhatsApp platform, this is handled behind the scenes by your provider. If you built a custom integration, add the BSUID-change webhook subscription to your setup checklist.

Migration checklist: from phone-first to hybrid

For teams that were built around phone numbers, here is the two-week migration:

Week 1: claim and audit

• [ ] Reserve your WhatsApp business username (Settings → Account → Username in the app).
• [ ] Audit every place your business phone number appears publicly. Add the handle next to it, do not replace it.
• [ ] Confirm your WhatsApp integration reads the user_id (BSUID) field from every incoming webhook.

Week 2: CRM and automations

• [ ] Add a BSUID field on the customer record in your CRM.
• [ ] Update dedup logic to merge by BSUID first, phone second.
• [ ] Confirm your ticketing system, AI assistant, and analytics all read BSUID.
• [ ] Backfill BSUID onto existing customer records where you have both identifiers.

Ongoing

• [ ] Add the handle to new marketing materials by default.
• [ ] Leave existing phone-number links alone. They still work.
• [ ] When Google Business Profile / Instagram / Meta ad manager offer a WhatsApp field, populate both formats where allowed.

Common mistakes to avoid

• Removing your phone number entirely. Existing customers and integrations will break. Add the username, keep the number.
• Rewriting every existing click-to-WhatsApp link. Not necessary and often breaks tracking. Update new links; leave old ones alone.
• Assuming your CRM handles BSUID because "they say they support WhatsApp." Ask specifically. The webhook change is recent.
• Building your AI assistant to greet customers by phone number. Migrate to BSUID-based identity now.
• Treating username adoption as optional. Meta has flagged BSUID as a required field for business messaging. The direction is clear.

What we're building at Invent

At Invent, we treat every WhatsApp customer as a single identity regardless of whether they reach out with their phone number visible or hidden. Our webhook integration reads BSUIDs from day one, the unified inbox merges every touchpoint into one thread, and the persistent customer memory travels with the customer across their entire history with your business. That means your AI assistant recognizes returning customers, your human team sees the full history, and your CRM stays clean as more of your customers move to a username-first WhatsApp experience.

Both. Always both.

A WhatsApp business username and a WhatsApp business phone number do different jobs. The phone number is your account's identity inside WhatsApp's system. The username is your identity to your customers. Use both, add the handle everywhere you list the number, and update your systems to identify customers by BSUID so nothing breaks as more people hide their numbers. The businesses that get this right will look effortlessly modern. The ones that don't will spend the second half of 2026 answering "why doesn't your bot remember me?"

FAQs

Is a WhatsApp username the same as a WhatsApp business number?

No. They are two different things that work together. Your business phone number identifies your account inside WhatsApp's platform. Your username is a public handle customers use to find you. On business accounts, both show side by side.

Do I have to choose between a WhatsApp username and a phone number?

No. Every business account has a phone number. A username is an optional additional handle. Adding a username does not remove or replace your number.

Will customers still see my WhatsApp business phone number if I have a username?

Yes. On business accounts, the phone number always shows in the chat details, next to the username. Only personal WhatsApp accounts hide the phone number behind the username.

Which is better for marketing, a WhatsApp username or a phone number?

For new marketing materials, a username is usually better because it is shorter, more memorable, and works internationally without country-code friction. For existing materials, leave the phone number in place and add the username alongside it.

What happens to my old wa.me/[phone] links if I add a WhatsApp username?

Nothing. Existing phone-number links keep working exactly as before. Adding a username does not deprecate the phone-number format.

Can my CRM identify customers by WhatsApp username?

Not directly, but it can identify them by their BSUID (Business-Scoped User ID), which every message webhook carries whether or not the customer has a username. See our WhatsApp Usernames Explained guide for the technical walkthrough.

Related

• WhatsApp Usernames Explained: What Businesses Need to Know
• WhatsApp Business Username: Setup Guide

Use both. Migrate your identity model to BSUID. Update materials as they get refreshed anyway.