A WhatsApp username is an optional, unique handle, like @yourbrand, that lets people start a chat without knowing your phone number. Businesses can reserve one for each number in WhatsApp Manager, or in the WhatsApp Business app. A username is 3 to 35 characters: English letters, digits, periods and underscores, with at least one letter. Usernames are rolling out country by country. In India, the government has asked Meta to hold the launch.
For a business, the username is the easy part. The bigger change is on the customer side. A customer who adopts a username can message you without sharing their number. When that happens, the WhatsApp Business API identifies them with a new ID called a BSUID. This guide covers both halves: claiming the right name, and getting your contact lists, CRM and automations ready for customers who arrive without a number.
Using ChatMitra? Your number sits in your own WhatsApp Business Account, so you reserve the username yourself in WhatsApp Manager, and nothing in ChatMitra needs to change for that. Jump to what this means for ChatMitra users for what works today and what to plan for.

What is a WhatsApp username?
A username is a second way to reach a WhatsApp account. It sits on top of the phone number and doesn’t replace it. Meta’s help centre describes four properties that matter for a business:
- It’s unique. No two accounts, personal or business, can hold the same username. Your display name (the name on your profile) doesn’t have to be unique; your username does.
- It’s optional. You can create, change or delete it at any time. A phone number is still required to register a WhatsApp account.
- It’s exact-match only. There’s no directory to browse and no suggestions. A customer has to type your exact username, or open a link or QR code you’ve shared, to start a chat.
- It can have a key. A username key is an optional code. If you turn it on, a new contact needs both your username and your key to message you for the first time. Customers who already have your phone number don’t need the key.
On WhatsApp, a username always shows with an @ in front, so people can tell it apart from a display name or a phone number.
Business usernames vs personal usernames
The feature works differently for the two sides of a conversation, and this table is the one to remember.
| Business username | Personal (customer) username | |
|---|---|---|
| Main purpose | Discovery: an easy handle to put on packaging, ads and your website | Privacy: chat without handing out a phone number |
| Phone number | Stays visible on your business profile | Hidden from anyone who doesn’t already have it saved |
| Who sees the username | Customers who haven’t saved your number see it in place of the number | Anyone the person chats with who hasn’t saved their number |
| Country | Not applicable | WhatsApp may show the other side the country code of the person’s number |
So a business username doesn’t make your business more private. It makes you easier to find. The privacy shift happens on the customer’s side, and it affects what data reaches you through the API.
WhatsApp username rules
These are the format rules from Meta’s developer documentation and help centre for business usernames. Check your preferred name against every row before you try to reserve it.
| Rule | What’s allowed | Example |
|---|---|---|
| Length | 3 to 35 characters | abc passes, ab fails |
| Characters | English letters (a–z), digits (0–9), periods and underscores | urban_threads passes; ürban fails (accented letters aren’t supported) |
| Letters | At least one English letter | store247 passes, 247247 fails |
| Periods | Can’t start or end with a period, or have two in a row | urban.threads passes, urban..threads fails |
| Web-style names | Can’t start with www | urbanthreads rather than www.urbanthreads |
| Upper and lower case | Ignored when comparing usernames | MyShop and myshop are the same name |
| Periods vs underscores | Not interchangeable | my.shop and my_shop are two different names |
| One per number | A username belongs to exactly one phone number | Sales and support numbers need two usernames |
Some names can’t be claimed by just anyone. WhatsApp’s own usernames FAQ says it holds existing Instagram and Facebook usernames for their owners, protects well-known public figures, celebrities and government entities, and blocks words such as “bank”, “government”, “police” and “verified”. A bank can’t simply register a handle containing “bank” and expect it to pass. Expect to verify ownership through Meta, or choose a name without the restricted word.
Is the WhatsApp username feature live?
It’s live in some countries and rolling out to others, so “yes” depends on where you are. Here’s the timeline from Meta’s own pages:
| When | What happened | Source |
|---|---|---|
| Early April 2026 | BSUIDs began appearing in messages webhooks on the WhatsApp Business Platform | Meta developer docs |
| 29 June 2026 | WhatsApp announced usernames. People and businesses could start reserving names | WhatsApp blog, Meta developer docs |
| July 2026 | The API began supporting messages sent to a BSUID instead of a phone number | Meta developer docs |
| Now | ”Rolling out gradually over the next few months.” WhatsApp sends an in-app notification when a reserved name becomes active | WhatsApp Help Center |
A reserved username isn’t visible or searchable yet. Customers can’t reach you through it, and a QR code for it won’t open a chat, until WhatsApp makes it active in your region. So don’t print a username on packaging until WhatsApp has told you it’s active.
WhatsApp username status in India
On 1 July 2026, India’s Ministry of Electronics and Information Technology (MeitY) sent Meta a notice. It told Meta not to launch usernames in India until consultations conclude to the government’s satisfaction. MeitY’s stated concern was that phone-number-free contact could make fraud, phishing, “digital arrest” scams and impersonation easier. Meta met ministry officials and filed its reply in early July, and MeitY said it was examining that reply.
As of 14 October 2026, we found no public announcement that usernames have gone live in India. For an Indian business, that means three things:
- Reserving a name early still costs you nothing. If the WhatsApp Manager or app option appears for your number, the name is held for you.
- Don’t build a launch campaign around “message us at @yourbrand” until WhatsApp activates usernames for Indian users.
- BSUIDs are already in your webhooks. They appear for every user, username or not, so API teams can prepare now, whatever the launch date.
If you serve customers outside India, from the Gulf, the UK or South-East Asia, some of them may get usernames before your Indian customers do. Your systems will meet phone-less customers first through those conversations.
How to reserve a WhatsApp username for your business
The steps depend on whether your number runs on the WhatsApp Business app or on the WhatsApp Business Platform (the API).
On the WhatsApp Business Platform (API numbers)
You need admin access to the Meta business portfolio that owns the WhatsApp Business Account (WABA).
- Sign in to Meta Business Suite and open WhatsApp Manager.
- Go to Phone numbers and select the number you want a username for.
- Find the Username section and click Create (or Edit if one is already set).
- Type your preferred username, or pick one Meta has reserved or suggested for your business.
- Save. The status shows as reserved until usernames are active for your number.
Meta Business Suite also has a second route: Settings → Accounts → WhatsApp accounts, select the WABA, then the Phone numbers tab. For developers, Meta’s API has an endpoint on the phone number (POST /{phone_number_id}/whatsapp_business_account/username) to set or change the username. Pending requests can’t be cancelled, so double-check the spelling before you submit.
If you aren’t sure where these screens are, our WhatsApp Manager guide walks through the layout, and Meta business portfolio basics explains who owns what.
On the WhatsApp Business app
- Update WhatsApp Business to the latest version and restart it.
- Open your profile settings and look for Username. Meta’s troubleshooting page says the option “appears in your profile when available”.
- Enter your username and confirm.
Creating, reserving or deleting a business username isn’t available on WhatsApp Web. Use the phone app.
Claiming your Instagram or Facebook handle
If the handle you want is already your Instagram or Facebook username, WhatsApp holds it for you, but only for a limited time. The two routes:
- App: go to Tools → Facebook and Instagram in WhatsApp Business and link your Facebook Page or Instagram business profile. WhatsApp’s help pages also describe adding WhatsApp to the same Accounts Center (being renamed Meta Account) as those profiles.
- API numbers: link the Facebook Page or Instagram account to the business phone number first, then claim the reserved name in WhatsApp Manager.
Meta doesn’t publish how long it holds these names. If your brand handle matters, claim it now rather than waiting for the launch in your country.
Choosing a username: a naming plan for one number or many
A username is short marketing copy that people have to type exactly. Before you reserve, settle three things.
1. Match your other handles. If customers know you as @urbanthreads on Instagram, use the same name on WhatsApp. One handle everywhere is easier to remember.
2. Plan for every number. One username covers one number. If you run separate numbers for sales, support and a second city, decide the pattern now:
| Number’s job | Pattern | Example |
|---|---|---|
| Main or sales number | Brand name alone | urbanthreads |
| Support | Brand + function | urbanthreads.support |
| A second region or store | Brand + place | urbanthreads.pune |
| A separate brand in the same portfolio | Its own brand name | threadsbyurban |
Pick periods or underscores and use the same one everywhere. Because my.shop and my_shop are different usernames, mixing them invites typos and lets someone else register the variant you didn’t use.
3. Make it easy to type.
- Avoid letter-and-digit look-alikes (
land1,oand0). - Avoid long hyphen-free strings like
thebestorganicspicesstore. - Avoid words your customers might spell two ways.
Say it out loud once. If you have to spell it for the person listening, simplify it.
Also reserve the obvious variant if you can. If urbanthreads is yours, someone else holding urban.threads could confuse customers. WhatsApp’s protections cover public figures and verified brands, not every small business, so a defensive reservation is cheap insurance.
Why your username request fails
WhatsApp’s troubleshooting page lists the common errors. Here’s what each one means and what to do.
| Message or symptom | Likely reason | What to do |
|---|---|---|
| No Username option | Your app is out of date, or usernames haven’t reached your region | Update and restart the app. If it’s still missing, the feature isn’t available to your number yet |
| ”This username is not available” | It’s held for the owner of an Instagram or Facebook account, or an earlier attempt was interrupted | If you own that profile, link it (see above). If a network drop interrupted you, wait a few minutes and retry |
| ”Username is taken” | Someone reserved it first | Use a clear variant from your naming plan, or tap Suggest a username |
| ”Try again later” | Too many attempts in a short time | Wait a few minutes before trying again |
| Customers can’t find you | The name is reserved but not yet active, or they mistyped it | Wait for WhatsApp’s “active” notification, and share a link or QR code instead of asking people to type the name |
| Old QR code stopped working | You changed your username | Share the new QR code. It updates to the new username automatically |
One warning from WhatsApp’s own help pages: if you change or delete a username, the old one “may become available for others to claim”, and deleting a username is permanent. Some providers’ guides mention a 60-day hold on old names. Meta’s help pages promise no such window, so treat any rename as a chance to lose the old name.
What usernames change for customers who message you
This is where usernames start to matter for API teams. When a customer adopts a username:
- They can message you without revealing their number. WhatsApp’s help centre says that if a person has a username the first time they chat with a business, “the business won’t see your phone number unless you choose to share it.”
- You still learn their country. WhatsApp shares the country based on the customer’s country code, and the BSUID itself starts with that country code (for example
IN.). - Existing relationships keep the number. If you already have their number from an earlier conversation, you continue to see it.
Meta’s developer documentation on BSUIDs is precise about when the API still includes a customer’s phone number in a webhook. It does if any of these is true:
- You messaged or called that user’s number within the last 30 days.
- You received a message or call from that number within the last 30 days.
- The user is in your business’s contact book.
The 30-day lookback is checked per business phone number. The contact book is a Meta-hosted store of WhatsApp users your business has talked to. It fills up automatically, with no integration work. You can turn it off in Meta Business Suite, under Business settings → Business info, but Meta warns that turning it off deletes what it has stored. For most businesses, that’s a reason to leave it on.
If you need a number for a delivery or a payment, ask for it. Meta has added a Request contact info button for utility and marketing templates and for interactive messages. When the customer taps it, their number is shared in the chat and a contacts webhook delivers it to you. In the app, WhatsApp suggests setting up a quick reply that asks the customer to share their contact card.

Username vs phone number vs BSUID
There are now three identifiers for the same customer. Each has a different job.
| Username | Phone number | BSUID | |
|---|---|---|---|
| What it is | A public handle the person chooses | The number registered on WhatsApp | An ID Meta generates for each user and business portfolio pair |
| Example | @riya.k | +91 98XXX XXXXX | IN.13491208655302741918 |
| Always in your webhooks? | No, only if the person has one | No, only under the 30-day or contact-book rules | Yes, as user_id, for every user |
| Can it change? | Yes, whenever the person changes it | Yes, if the person changes numbers | Only when the person changes their phone number |
| Can you message it? | No | Yes | Yes, from any number in the same portfolio |
| Best use in your systems | Showing who you’re talking to | Delivery, OTPs, payments, calls | The stable key for matching a customer across tools |
The practical rule: key your customer records on the BSUID, store the phone number when you have it, and treat the username as a display label, because it’s the identifier most likely to change. Changing a username doesn’t change the person’s BSUID or phone number.

What changes on the WhatsApp Business API
If you or your provider work directly with the API, these are the changes in Meta’s documentation that touch your code.
Webhook fields
| Field | Where | Behaviour |
|---|---|---|
from | Incoming message | Omitted when the phone number can’t be shared |
from_user_id | Incoming message | New. Always set to the user’s BSUID |
contacts[].wa_id | Incoming message | Omitted when the phone number can’t be shared |
contacts[].user_id | Incoming message | New. Always set to the user’s BSUID |
contacts[].profile.username | Incoming message | Set only if the user has a username |
recipient_id | Status update | Omitted if you messaged a BSUID and the number can’t be shared |
recipient_user_id | Status update | New. Always the BSUID, whether you sent to a number or a BSUID |
Here’s a simplified incoming message from a first-time customer with a username, using the field names above. The values are illustrative:
{
"contacts": [
{
"profile": { "name": "Riya", "username": "riya.k" },
"user_id": "IN.13491208655302741918"
}
],
"messages": [
{
"from_user_id": "IN.13491208655302741918",
"id": "wamid.HBgM...",
"timestamp": "1760438400",
"type": "text",
"text": { "body": "Hi, is the blue kurta in stock?" }
}
]
}Notice what’s missing: there’s no from and no wa_id. Any code that reads messages[0].from as the customer key will get nothing for this message. That’s the most common thing to fix.
Sending messages
- Send requests gain a
recipientfield that takes a BSUID or a parent BSUID. You can still usetofor a phone number. If you send both,towins. - You can send any message type to a BSUID except one-tap, zero-tap and copy-code authentication templates, which still need a phone number. Trying returns error 131062 (“Business-scoped User ID (BSUID) recipients are not supported for this message”). If you send login codes, see our authentication templates guide.
- A BSUID works from any phone number owned by the same business portfolio. Sending from a number in a different portfolio fails. Groups of portfolios enrolled under a parent account get a parent BSUID (it looks like
IN.ENT.…) that works across them.
Identity changes
- A new
user_id_updatewebhook fires when a user’s BSUID changes, which happens when they change their phone number. It carries the previous and the current BSUID. Use it to merge the old record into the new one rather than creating a duplicate customer. - If you delete a user through Meta’s Contact Book API, their phone number and BSUID stop appearing in webhooks.
What doesn’t change
Opt-in rules don’t change. You still need a customer’s permission before you send them template messages. A username doesn’t count as consent, and finding a customer’s BSUID doesn’t either. Our WhatsApp opt-in guide covers how to collect and record consent. None of Meta’s username or BSUID pages lists a fee for having a username. Templates are still billed per delivered message by category, as explained in our WhatsApp API pricing guide.
A preparation checklist for businesses
Work through this in order. The first four steps secure your name. The rest get your systems ready for customers who arrive without a number.
- Agree one handle that matches your Instagram and Facebook usernames.
- Link your Facebook Page and Instagram account to each business number that needs the same handle.
- Reserve a username for every number, following one naming pattern. Remember that pending requests can’t be cancelled, so check the spelling first.
- Wait for “active” before you print. Add the handle to packaging, your website and ads only after WhatsApp confirms it’s live in your region.
- Add a BSUID field to your CRM and make it the matching key. Keep the phone number as a separate field that can be empty. If you’re choosing a CRM, our WhatsApp CRM guide lists what to look for.
- Fix code that assumes
fromis a phone number. Check webhook handlers, lead forms, order lookups, and any automation step that searches by number. - Route OTPs around the gap. For login and verification, keep collecting the phone number on your own sign-up form, because BSUID-only customers can’t receive one-tap, zero-tap or copy-code templates.
- Leave Meta’s contact book on, so customers you already talk to keep arriving with their numbers.
- Handle
user_id_updateto merge records when a customer changes numbers. - Train your team. Tell agents that a chat showing an @handle and no number is normal, and give them a polite line for asking for a number when an order needs one.
Using ChatMitra with WhatsApp usernames
Reserving your username. ChatMitra connects your number through Meta’s Embedded Signup. The WhatsApp Business Account belongs to your own Meta business portfolio, so you reserve the username in WhatsApp Manager exactly as described above. You don’t need to change anything in ChatMitra, and your broadcasts, inbox, chatbot flows and API keys keep working while the request is pending.
Your display name still leads. Meta shows a business’s display name before its username in the profile, chat list and messages. Keep your display name consistent with your username so customers see one brand.
Helping customers find you. Until your username is active, keep using your phone-number chat link and QR code. Our free WhatsApp chat link generator and QR code generator both build links from your number, and they work everywhere today.
Good to know. ChatMitra identifies each chat by the customer’s WhatsApp phone number today. Under Meta’s rules, most conversations will keep arriving with a number: anyone you’ve messaged in the last 30 days, anyone who messaged you, and anyone in your Meta contact book. ChatMitra doesn’t yet support customers who reach you with a BSUID only, which can happen with a brand-new customer who uses a username. ChatMitra’s template builder doesn’t offer Meta’s Request contact info button yet either. Within an open chat, your agents can ask the customer to share their contact card, and ChatMitra’s inbox shows contact cards customers send. We’ll update this guide when BSUID-only contacts are supported. If you build on the ChatMitra API and webhooks, plan your own records around the BSUID now, so they’re ready either way.
If you’re new to the WhatsApp Business API and want to see how inbox, broadcasts and automation fit together, start with what the WhatsApp Business API is, then see ChatMitra’s plans.

