Your WhatsApp enquiries are about to stop coming with phone numbers

Every WhatsApp enquiry you receive today arrives with a phone number attached. That is changing, and not at some point in the future — the mechanism is already live.

On WhatsApp accounts that have adopted a username, the phone number is left out of what your system receives. An enquiry from somebody who has never messaged you before is the exact case where nothing fills the gap — whether they came from an advertisement, the chat button on your website, or a QR code on a display.

What actually changed?

WhatsApp is introducing optional usernames, so people can be reached without handing over a mobile number. Alongside it, Meta introduced a second thing that got far less attention and matters far more to anyone running campaigns: the business-scoped user ID.

A business-scoped user ID, or BSUID, is an identifier for one person as seen by one business. It looks like IN.13491208655302741918 — a country code, a full stop, and a long number. Each business gets a different ID for the same person, so it cannot be passed around or matched across companies.

When somebody who has adopted a username messages you, this is what you get instead of their number. The fields your system has always read — wa_id, from, recipient_id — may simply not be there.

The dates are already behind us. BSUIDs began appearing in webhooks in early April 2026. Businesses could reserve usernames from 29 June 2026. Sending to a BSUID through the API arrived in July 2026. This is documented by Meta in its business-scoped user ID guidance for developers.

Which enquiries does this affect?

Click-to-WhatsApp advertising is where this is usually noticed first, because that is where the money is and where somebody is watching a cost per lead. But the advertisement is only the most expensive example. It is not a campaign problem. It is an every-entry-point problem.

What matters is whether the person has interacted with you recently, not how the conversation started. So the same thing happens to an enquiry from:

• The chat button on your website, and any wa.me link anywhere on it
• A QR code on a display, a carton, a hoarding or printed literature
• A link in an email signature, a proposal or an invoice
• Your Google Business Profile, a marketplace listing or a directory entry
• A social media bio or a post with a WhatsApp link in it
• A number shared by one customer with another — the referral that arrives out of nowhere

Every one of those is a first message from somebody you have no recent history with. The advertisement at least tells you which campaign it came from. The QR code on a display and the button on your website tell you nothing beyond the message itself, which makes the missing number matter more, not less.

If you have spent the last few years moving every route to your business onto WhatsApp — and most have — then this touches all of them at once.

What do you actually lose?

This is worth getting right, because the panicked version of it is wrong.

You do not lose the lead. The conversation is still yours, and you can keep messaging that person through their BSUID for as long as the relationship lasts. If your entire follow-up happens inside WhatsApp, very little changes for you.

What you lose is everything that depends on a phone number:

• The phone call. In most Indian lead-generation, the follow-up is a call. No number, no call.
• The CRM record. If your system keys customers on mobile number, there is nothing to key on.
• The match against history. A returning buyer looks like a stranger, because the thing that used to connect them to their past orders is missing.
• The campaign list. The number never reaches the database you build audiences from.

So the accurate version is narrower than “you lose your leads” — and considerably more expensive, because it removes the step your sales team actually performs.

Why will this look fine for a while?

Because of a rule that quietly disguises the problem.

The phone number is still included if you have messaged or called that person in the last 30 days, if they have messaged or called you in the last 30 days, or if they are in your business portfolio’s contact book. The check is made per business phone number, so a customer known to one of your numbers can be anonymous to another.

Read that again with your own data in mind. Your active customers keep showing a number, so everything looks normal. The people who arrive without one are the cold ones: the new lead from today’s advertisement, and the buyer who last spoke to you five months ago. Those are the two groups the whole campaign exists to reach.

What can be done about it?

Ask for the number — but only when it is missing, and only once.

When somebody clicks your advertisement and messages you, they have opened a conversation, and you can reply freely for the next 24 hours without an approved template. That is enough room to ask a question and get an answer. Meta publishes guidance on requesting a phone number, so this is the intended route rather than a loophole.

Done as an automation rather than by hand, the sequence is:

1. A message arrives from an advertisement. The bot checks whether a phone number came with it.
2. If it did, nothing happens. The lead goes through as it always has.
3. If it did not, the bot looks up the BSUID. If this person has shared a number before, it is already on file and they are never asked again.
4. If the BSUID is new, the bot asks for the number, and asks separately for permission to message them.
5. The number, the consent and the BSUID are stored together, and the lead is passed to the sales team.

The third step is the one that matters most and the one most people will skip. Without it, your best returning customers are interrogated for a number you already hold, every single time they contact you.

The detail almost everyone will miss

A BSUID is stable, but it is not permanent. It is regenerated when the person changes their phone number, and the change arrives as a system message your platform has to be listening for.

If nothing handles that, the identity you were so carefully building silently breaks. The customer comes back, the new ID is unrecognised, and they are treated as a stranger — which is the exact problem the whole arrangement was built to prevent. It will not announce itself. It will just look like you have more new customers than you really do.

A number is not the same as permission

Collecting a number in a chat does not entitle you to put it in a campaign.

Opt-in has to be recorded, specific, and cover what the person will actually receive. Someone who gives their number so a salesperson can call about a quotation has not agreed to a promotional broadcast every Friday. Blocks and reports affect your quality rating, your quality rating governs how many people you may message at all, and accounts that message data people never agreed to hand over are suspended without warning.

So the bot should ask two things, not one. The number, and permission. It is one extra line, and it is the difference between a list you own and a problem you are building.

Should everyone be asking?

No, and this is worth saying plainly even though it argues against doing more work.

Every question you ask a fresh lead costs you some of them. If your sales process lives inside WhatsApp anyway — the enquiry, the catalogue, the quotation, the follow-up — then the BSUID is all you need, and asking for a number is friction bought for nothing.

Ask for it when you have a real use for it: your team phones people, your CRM is keyed on mobile number, or you build campaign audiences outside WhatsApp. If none of those are true, let it go.

And whichever route you take, be honest with yourself about the arithmetic. Some people will decline. An automation recovers much of what the change takes away. It does not recover all of it, and anyone promising otherwise has not thought about it.

Where does India stand?

The username rollout is on hold here. The Ministry of Electronics and Information Technology issued a notice to Meta after concerns were raised about fraud, phishing, impersonation and digital-arrest scams, and WhatsApp has said it will not launch usernames in India until those consultations conclude.

Two reasons that is not a reason to wait.

The identifiers are already arriving. BSUIDs have been in webhooks since April, so any system that assumes a phone number is present is already relying on luck. And if any of your customers are outside India — exporters, education, hospitality, anyone selling to the Gulf — the change applies to them today.

The hold is a delay, not a reprieve. The sensible position is to be ready before it lifts rather than to find out on the day it does.

Questions we are asked

Will my existing contact list stop working?

No. Numbers you already hold remain valid and you can keep messaging them. The change affects what arrives with new conversations, not what you have already stored.

Does this break OTP messages?

No. Authentication templates — one-tap, zero-tap and copy-code — still require a phone number and cannot be sent to a BSUID. If you use WhatsApp for one-time passcodes, nothing changes.

Can I look up someone’s number from their username?

No. There is no directory and no lookup. If the number is not supplied, the only way to get it is to ask the person for it.

Can I use the same ID across my group companies?

Not by default. A BSUID belongs to one business portfolio, and the same person has a different one with each business. Larger organisations running several portfolios can apply to receive a shared identifier across them.

How urgent is this for an Indian business?

Not an emergency, but not something to leave alone. The work is in your messaging platform rather than in your advertising, so it is worth confirming with whoever runs that platform that business-scoped user IDs are handled before adoption begins rather than after.

Concord WABA handles business-scoped user IDs. The platform stores the ID against the contact, recognises someone who has messaged before so they are not asked twice, and where the number is missing an automation asks for it along with permission to message. The number, the consent and the ID are kept together, and the lead can be passed into the CRM your team already uses.

Last verified: 19 October 2026. WhatsApp’s rules and the Indian position can both change — if you are reading this much later, check the current position before acting on it.