WhatsApp usernames and BSUID for business: RateUp readiness checklist cover for loyalty programs

WhatsApp Usernames and BSUID: What They Mean for Your Loyalty Program

AS
Abhilash Sathyan
November 6, 2026

WhatsApp usernames let customers chat with a business without showing their phone number. To make that work, Meta now gives every customer a business-scoped user ID (BSUID): a code that identifies them to your business alone. For most brands, the risk isn't marketing reach. It's identity. If your loyalty points, order history and feedback are all keyed to a phone number, a new customer who messages you by username can arrive as a stranger your systems can't match.

This guide explains what changed, why it matters most for loyalty and retention, and what D2C brands and retailers in India, the UAE, Malaysia and Singapore should do before usernames reach their country.

What changed: usernames and BSUIDs in plain English

According to Meta's developer documentation on business-scoped user IDs, the rollout has come in stages through 2026:

  • April 2026: Meta started including BSUIDs in the message data (webhooks) businesses receive on the WhatsApp Business Platform.
  • 29 June 2026: Businesses could start reserving a business username in WhatsApp Manager, Meta Business Suite or through the API. Consumers could start reserving theirs too, as TechCrunch reported.
  • July 2026: Meta's APIs began supporting messages sent to a BSUID, not only to a phone number.
  • Rest of 2026 and beyond: Usernames are being switched on gradually, country by country. Meta hasn't published a country-by-country date list, and usernames first appeared with a limited group of beta users in April, per 9to5Google.

Three details matter most for businesses:

  1. The 30-day phone number rule. When a customer has turned on a username, Meta only includes their phone number in your message data if you messaged or called them in the last 30 days, they messaged or called you in the last 30 days, or they're in your WhatsApp contact book. This is checked separately for each of your business phone numbers.
  2. BSUIDs are scoped to your business. The same customer gets a different BSUID with every business portfolio. If they change their phone number, they get a new BSUID. If they only change their username, the BSUID stays the same.
  3. Some messages still need a phone number. One-tap, zero-tap and copy-code authentication templates (the usual OTP formats) can't be sent to a BSUID.

Meta also added two tools to help you get the number back with the customer's permission. The first is a REQUEST_CONTACT_INFO button you can add to utility and marketing templates or send as an interactive message. When the customer taps it, they share their number. The second is a Meta-hosted contact book that remembers numbers and BSUIDs from interactions after it was switched on. Meta's documentation states the contact book does not capture interactions from before launch.

Your own business username doesn't hide your business phone number. Meta says business usernames are meant for discovery, not privacy.

Why this matters most for loyalty programs

Most WhatsApp marketing coverage of this change focuses on campaign delivery. We think the bigger issue for D2C brands and retailers is that the phone number is the glue holding your customer data together:

  • Shopify and WooCommerce orders store a phone number at checkout.
  • In-store POS systems look customers up by phone number at the billing counter.
  • Loyalty points, stamps and tiers are usually tied to that same number.
  • Feedback, reviews and support history sit against it too.

If a customer messages you by username and Meta doesn't share their number, your WhatsApp conversation has a BSUID but your store and loyalty records have a phone number. Nothing links them. The customer asks "how many points do I have?" and your system can't answer.

Where the gap actually shows up

Here's our contrarian view: for your existing customers, the impact will probably be small. If you've chatted with someone in the last 30 days, or they're in your contact book, Meta still shares the number. Usernames mainly protect privacy in new chats: people who already have a customer's number, or share an existing chat with them, can still see it.

The gap concentrates in three places:

  1. New customers from click-to-WhatsApp ads, QR codes and social links. They're messaging you for the first time and may only show a username.
  2. Lapsed customers. A loyalty member who hasn't chatted with a given business number for more than 30 days, and wasn't saved to the contact book, may come back as a username only. Win-back flows are where this bites.
  3. Multiple business numbers. The 30-day rule applies per business number. If your support number and your marketing number are different, one may see the customer's number while the other doesn't.

The stakes are real because the first conversation is where you earn the second purchase. Baymard Institute puts the average documented cart abandonment rate at 70.22%. If you can't connect a WhatsApp chat to a cart or a loyalty profile, your recovery and rewards messages have nothing to work with.

A simple identity framework: number-known, number-requested, BSUID-only

Rather than rebuilding everything, sort every incoming WhatsApp customer into one of three states and give each state a job:

StateWhat you haveWhat to do
Number-knownPhone number + BSUIDMatch to orders and loyalty as normal. Save both IDs to the customer profile.
Number-requestedBSUID, with a contact request sentOffer a clear reason to share: "Share your number to see your points and claim your welcome reward."
BSUID-onlyBSUID onlyServe them fully in chat (answers, catalogue, support), but don't promise rewards you can't attach to an account yet.

The key change is storing the BSUID next to the phone number on every customer profile from now on. Once a customer has shared both, you can recognise them later even if Meta only sends the BSUID.

Practical steps by market

The steps below are the same core plan. The details differ because checkout habits, data laws and acquisition channels differ.

India: protect COD confirmations and OTP flows

India is a phone-first market. DataReportal counts 1.03 billion internet users in India as of October 2025, and for most D2C brands the phone number is the customer ID across checkout, delivery and returns.

  • Keep phone number mandatory at checkout. COD confirmation and delivery updates depend on it, and authentication templates still need a number.
  • Add a "Share number" step to your welcome flow for chats that start from Instagram or click-to-WhatsApp ads, with a clear benefit (welcome points, order tracking).
  • Record consent when the customer shares their number. India's DPDP Act puts weight on clear, purpose-specific consent, so say what you'll use the number for.

The UAE has 12.5 million active social media user identities, equal to 110% of the population according to DataReportal, so many customers juggle several accounts and numbers. For mall retailers and cafés in Dubai and Abu Dhabi, loyalty often starts at the counter with a phone number.

  • When a customer joins at the POS, send the WhatsApp welcome message straight away. That opens the 30-day window and makes the number visible.
  • Make the contact-request message bilingual (English and Arabic) so customers understand why you're asking.
  • Review your consent wording against the UAE PDPL, especially for tourists and short-stay residents.

Malaysia: plan for sale-season spikes

11.11 and 12.12 bring a flood of first-time chats from ads and marketplace links: exactly the group most likely to arrive as BSUID-only.

  • Put the contact request inside your sale welcome flow, tied to a clear benefit like early access to the next drop or bonus points in RM.
  • Follow up within 30 days of a sale purchase so the number stays visible for after-sale reminders.
  • Keep consent records aligned with Malaysia's PDPA.

Singapore: keep PDPA and DNC checks clean

Singapore's Do Not Call rules are built around phone numbers. If you only hold a BSUID, you can't easily check a contact against the DNC Registry, so explicit consent captured in the chat becomes your safest basis for marketing. Our guide to WhatsApp marketing under Singapore's PDPA and DNC rules covers the details.

  • Ask for clear marketing consent in the same message as the contact request.
  • Don't add BSUID-only contacts to broadcast lists until you have consent recorded.

Your 7-step readiness checklist

  1. Reserve your business username in WhatsApp Manager for each customer-facing number. Usernames can only be changed twice in 14 days, so choose carefully.
  2. Ask your WhatsApp provider how they store BSUIDs. Meta says supporting BSUIDs is required for partners, directly integrated businesses and click-to-WhatsApp advertisers.
  3. Add a BSUID field to customer profiles in your CRM or loyalty platform, next to the phone number.
  4. Add the REQUEST_CONTACT_INFO button to your welcome, loyalty sign-up and order-tracking templates.
  5. Use as few business numbers as you can for customer chats, since the 30-day rule is applied per number.
  6. Keep a monthly touchpoint with loyalty members, such as a points balance or reward reminder, so the 30-day window stays open. Our WhatsApp loyalty message templates are a good starting point.
  7. Keep OTPs on phone numbers. Authentication templates still need them.

How RateUp helps

RateUp runs WhatsApp loyalty programs on the official WhatsApp Business API, with points, stamps, reminders and rewards handled inside the chat and no app for customers to download. That matters here, because a loyalty program that already talks to members regularly keeps more of them inside Meta's 30-day window.

  • The RateUp Shopify integration ties points to paid orders automatically, so every order is a reason to message the customer.
  • Unlimited broadcasts and automations, with zero markup on WhatsApp API fees, mean a monthly points reminder doesn't become a cost decision.
  • WhatsApp, Instagram, and Messenger in one inbox gives your team the full conversation history when a returning customer asks about their points.

If you want to go deeper on using loyalty data, read how to use WhatsApp loyalty data to understand your best customers and our guide to WhatsApp loyalty programs for D2C brands. Planning your budget for the year? Our UAE WhatsApp Business API pricing guide explains the October 2026 billing changes.

FAQ

What is a WhatsApp BSUID?

A business-scoped user ID (BSUID) is an identifier Meta assigns to each WhatsApp user for a specific business portfolio. It lets a business recognise and message a customer even when their phone number isn't shared. The same person has a different BSUID with each business, and gets a new one if they change their phone number.

Will WhatsApp usernames hide my customers' phone numbers from my business?

Sometimes. If a customer has turned on a username, Meta only shares their number if either side messaged or called within the last 30 days, or the customer is in your contact book. Existing chats keep showing numbers. New chats from customers you've never spoken to are where numbers are most likely to be missing.

Do I need to change my WhatsApp loyalty program?

You don't need to rebuild it, but you should store the BSUID alongside the phone number on each member profile, add a "share your number" step to sign-up flows, and keep in touch with members at least monthly so their numbers stay visible.

Can I still send OTPs on WhatsApp if a customer uses a username?

Yes, as long as you have their phone number. Meta's documentation says one-tap, zero-tap and copy-code authentication templates can't be sent to a BSUID, so OTP flows still depend on the phone number.

When will WhatsApp usernames launch in India, the UAE, Malaysia and Singapore?

Meta hasn't published country dates. Usernames are rolling out gradually, and reservations opened globally in late June 2026. Reserve your business username now and prepare your systems before it switches on in your market.

Does a business username hide my business phone number?

No. Business usernames help customers find and recognise you, but Meta says they don't hide the business number and aren't meant for privacy.

Get ready before usernames reach your market

WhatsApp usernames are good for customer privacy, and they don't have to be bad for your retention. Brands that store BSUIDs, ask for numbers with a clear reason and keep in regular touch with loyalty members will barely notice the switch. Brands that rely on a phone number appearing automatically will see more anonymous chats and lost loyalty matches.

Want to see how a WhatsApp loyalty program keeps members engaged month after month? Book a demo with the RateUp team, and ask us how we'd handle usernames and BSUIDs for your store.

AS

About Abhilash Sathyan

Hi, I’m Abhilash — co-founder & CEO of RateUp. I build tools that help brands grow with WhatsApp loyalty, referrals, feedback, and AI insights. Honored with the National e-Governance Gold Award & IBM x NASSCOM Climate Challenge

Get started free

Ready to improve your business reviews?

Join thousands of businesses using RateUp to enhance their online reputation.

Cookie Preferences

We use cookies to analyze website traffic and measure our ads. They stay off unless you accept.Learn more