WhatsApp Usernames Are Killing the Blasting Era

WhatsApp Usernames Are Killing the Blasting Era

WhatsApp changed the phone number to a username. Most businesses haven't noticed what actually happened.

This isn't a cosmetic update. This is Meta closing the blasting era: numbers auto-hide, third-party tools get banned fast, and everyone gets pushed toward the paid WhatsApp Business API.

This isn't a cosmetic update

For almost two decades, your phone number was your identity on WhatsApp. It's how your CRM knew who was messaging, how your bot routed conversations, how your campaigns matched a click to a person. The number was the key to everything.

On June 29, 2026 WhatsApp began letting users reserve unique usernames, and businesses could reserve their brand usernames from the same date. The feature itself rolls out gradually through 2026 — there is no published fixed wave schedule. Optional at first: users who don't adopt a username see no change. But the moment a user switches, their number stops appearing in new conversations. The handle replaces it.

That's the quiet part nobody read. The phone number now stays private and powers login, verification, and recovery in the background — but it no longer flows to businesses by default.

The phone number just became optional

For businesses the display behavior differs slightly: a verified business keeps its number visible and gains a searchable username on top, like @yourbrand. That's the marketing upside — a handle you can put on a billboard.

The real shift is on the consumer side. When a user adopts a username, they can message your business without their phone number ever appearing in the chat — unless they choose to share it. Your webhook gets a new opaque identifier instead: the Business-Scoped User ID, or BSUID.

BSUIDs began appearing in webhooks in early April 2026, and sending messages to a BSUID via the API is supported from July 2026. Meta's Contact Book — which pairs numbers with BSUIDs from prior interactions — launched in early April 2026.

What breaks when the number disappears

If your stack treats the phone number as the only source of truth, this is where it hurts:

• CRM matching goes dark. A new customer messages you and no number arrives. You can't match them to anything. They return a month later and get treated like a stranger — two conversations, zero continuity.
• Bot routing loses signal. Context, language, and priority were keyed on the number. Now there's a string of opaque alphanumerics instead.
• Campaign attribution dies. Ads that match a user by number can't connect anymore.
• OTP flows break. Authentication templates still require a phone number. BSUID alone can't send a verification code — you must explicitly ask the user to share their number in the chat, and they can say no.

The fix isn't hard, but it's real work: store BSUID as a first-class identity, make phone fields nullable, match by BSUID first, and ask for the number inside the conversation when you genuinely need it.

Blasting got expensive on purpose

Now the second shoe. Meta hasn't been subtle about pricing the channel.

Since July 1, 2025 billing is per delivered message, not per conversation. Marketing template rates vary by market — check Meta's rate card for the exact per-message price in each country. Volume tiers apply to utility and authentication messages, not marketing. New unverified portfolios start at just 250 unique users a day; verification and sustained quality scale that to 2,000, then 10,000 and up.

And the ceiling keeps tightening. Meta caps how many marketing templates a user can receive across all businesses combined — the cap is dynamic and engagement-based, with no fixed published number — and error 131049 is your message being blocked because the recipient hit it. US marketing templates to +1 numbers have been paused since April 1, 2025. And from October 1, 2026, even service replies inside the 24-hour window get charged per message — something that has been free since November 2024.

Unofficial blasters are a time bomb. Meta bans modified clients and unauthorized automation, torches your quality rating, and can restrict or permanently disable the offending numbers. And the free WhatsApp Business App is built for small-scale messaging, not bulk — so there's no cheap backdoor to bulk either. Everything that wants scale funnels toward the official Business API, and that API is metered on purpose.

Survive by selling value, not spam

So how do you play this? Stop blasting. It's not a channel strategy anymore, it's a liability.

• Lead with value. A cheap entry product, a free ebook, a quick consultation. Trade it for a name and a number — genuinely, with the customer's conscious choice.
• That first-party list is the asset. Numbers you earn with consent are worth more than any scraped list. Every broadcast to an opted-in contact is legal, cheap, and safe from bans.
• Relevance beats volume. With the cross-business cap on marketing templates tightening per user, the only messages that land are the ones the recipient actually wanted.
• Don't look desperate. Frame it as what the customer misses out on if they don't act now — value, not begging. A customer who feels they're losing something shares their details willingly.

Harvest the numbers while the window is open

The part nobody puts in writing is that the rollout isn't a light switch — it's progressive, and field reports split. Right now some people can't see or save the number of a customer who has a username; others still can. A number also stays visible if you messaged that person within the last 30 days or they're already in your Contact Book.

Don't count on that lasting. Everyone testing this ends at the same advice: while you can save the number, save it. Bank those contact details today, because tomorrow the window closes. Collect the name and number while they're still offered to you.

PDPA: consent is the law now

The part everyone misses. Storing a customer database without consent isn't an ethics risk anymore — it's a legal risk. In Malaysia, the PDPA is no longer a slide you nod at during compliance training; a data breach or a spammed database is exposure with real penalties attached.

And it cuts both ways. Your database is an asset while you guard it — the moment you treat it as something to sell or misuse, it becomes a liability around your own neck. The businesses that hold data with care win the long game; everyone else plays a numbers game that Meta is actively dismantling.

The bottom line

WhatsApp grew up on the phone number. The username is the end of that era — and the blasting model died with it. The businesses that treat this as a strategy shift, not a UI change, will be the ones still standing when the bans, the caps, and the bills finish reshaping the channel.

Build a list you can be proud of. Ask before you save. Send things people actually want. That's the whole game now.

Sources

• Meta for Developers: Business-scoped user IDs
• The Straits Times: WhatsApp opens username reservations to 3 billion users
• Meta for Developers: WhatsApp Business Platform pricing and rate cards
• WhatsApp: WhatsApp Business Platform Pricing
• Meta for Developers: Messaging Limits
• YCloud: Meta's Frequency Capping for WhatsApp Marketing Messages
• Klaviyo: Understanding WhatsApp per-user marketing limits
• Twilio: WhatsApp Marketing Messages to U.S. Numbers No Longer Supported
• Twilio: Notice - Changes to WhatsApp's Pricing (October 2026)
• Twilio: WhatsApp usernames - New Business Scoped User ID (BSUID) field required starting June 2026
• CM.com: WhatsApp's BSUID Update - What Businesses Need to Know
• WhatsApp: WhatsApp Business Messaging Policy
• PDPC Malaysia: Personal Data Protection (Amendment) Act 2024