WhatsApp usernames are here: what it means for HubSpot

For years, the phone number has been the thread tying every WhatsApp conversation to a HubSpot contact. That thread has started to loosen.

What's changing

Meta is rolling out WhatsApp usernames gradually, country by country. People who adopt one can hide their phone number from the businesses they message. Instead, every message now carries a business-scoped user ID (BSUID): a unique identifier for that person, valid only within your business.

For HubSpot teams, that's the catch. Most integrations match a WhatsApp conversation to a contact by phone number. No number, no match: duplicate contacts, conversations logged nowhere, and workflows that never fire.

How big is the problem today?

Smaller than the headlines suggest. Across Polser customers, username adoption is under 1% in most EU countries, with only a few Latin American markets showing more. This is a "prepare now" change, not a "panic now" one. But adoption only moves in one direction, and the work is far easier before it matters.

Meta's safety nets

Your existing contacts won't vanish overnight. Meta still shares a person's phone number if you've exchanged messages with them in the last 30 days, or if they're in Meta's new contact book for your business. And a new "request contact info" button lets someone share their number with a single tap.

The real gap is new contacts: someone with a username messaging you for the first time.

Four things to do now

1. Add username and BSUID properties in HubSpot. Treat them as identifiers that sit next to the phone number, not replacements for it.

2. Link identities while you still can. While contacts share both their number and username, store them together. If they hide their number later, the connection is already on file.

3. Plan how you'll identify newcomers. Ask early in the conversation for an email or phone number, or use the request contact info button.

4. Audit anything keyed on phone numbers: deduplication rules, workflow triggers, reports.

How Polser handles it

We've been shipping username support since last August, and Polser covers the first two steps above for you:

• Conversations keep flowing. Messages from username-only contacts land in the inbox like any other, showing their @username, with the BSUID clearly marked in their profile.

• Your HubSpot sync knows both identities. Map username and BSUID to HubSpot properties right next to the phone number. For every contact we match by phone, both are written automatically.

• No duplicates. If a username contact's number becomes available later, Polser recognises them and merges the conversation.

• Newcomers get identified. Set up an automated message asking for an email or phone number to match or create the HubSpot record, or send the request contact info button.

Usernames are a moving target. Meta keeps adjusting the rules as adoption grows, and we'll keep shipping features to match. We'll share what we learn here along the way.

See the details in our release notes (Ready for usernames and Usernames, now in view), or book a demo to see it working with your HubSpot.