> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp user IDs: phone numbers, BSUIDs and usernames

> How WhatsApp identifies customers by phone number, wa_id, BSUID and username, when Meta leaves out the phone number, and what Flowella needs.

WhatsApp now identifies each customer in up to four ways: their **phone number**, their **WhatsApp ID** (`wa_id`, usually the number without the plus sign), a **business-scoped user ID** (BSUID) that is unique to your business, and an optional **username**. As customers adopt usernames, Meta stops sending some customers' phone numbers to businesses. The BSUID is then the only identifier you get, so anything keyed on phone numbers has to cope without one.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella identifies every contact by phone number and sends only to phone numbers. If Meta sends a customer's message without a phone number, Flowella can't match it to a contact, and the message doesn't appear in Flowella or reach HubSpot. Most customers aren't affected yet: Meta still includes the number for anyone you've been in touch with recently.

## The four identifiers

| Identifier | Field in Meta's data | Scope | Notes |
| - | - | - | - |
| Phone number | `wa_id`, `from` | Global | Can be missing for customers with a username |
| Business-scoped user ID | `user_id` | One business portfolio | Always present on messages, for every customer, since April 2026 |
| Parent BSUID | `parent_user_id` | Several portfolios that Meta has enrolled together | Only for large businesses with several portfolios, on request |
| Username | `username` | Global | Optional. Customers can change it. Shown instead of the phone number in WhatsApp. |

### What a BSUID looks like

A BSUID starts with the customer's two-letter country code and a full stop, followed by up to 128 letters and numbers, for example `GB.13491208655302741918`. A parent BSUID has `ENT` after the country code, for example `GB.ENT.11815799212886844830`. Always use the whole value.

* It belongs to one **business portfolio**. Any of that portfolio's numbers can message it, but a number in another portfolio can't.
* It's created automatically, and doesn't change when the customer changes their username.
* It **changes** when the customer changes their phone number. Meta sends a system message when that happens.

## When Meta leaves out the phone number

A customer who adopts a username has their number hidden. Meta still includes it in your webhooks when any of these is true:

| Condition | Scope |
| - | - |
| That business number messaged or called the customer's number in the last 30 days | Each business number separately |
| That business number received a message or call from the customer's number in the last 30 days | Each business number separately |
| The customer is in your business portfolio's **contact book** | Every number in the portfolio |
| The customer shared their number with you, for example with a request contact info button | From then on, through the contact book |

Customers without a username always arrive with their phone number.

### The contact book

Meta keeps a contact book for each business portfolio. When any of your numbers messages or calls a customer's phone number, or hears from it, Meta records the number with the BSUID and keeps including the number in your webhooks. It only records contacts from the time the feature started, not earlier conversations. You can switch it off in Meta Business Suite under **Business settings** > **Business info**. Switching it off deletes everything it has stored, permanently.

## Sending to a BSUID

Since July 2026, you can send messages to a BSUID instead of a phone number. If a request has both, Meta uses the phone number. Authentication templates with copy code, one-tap or zero-tap buttons still need the phone number. Sends that don't support BSUIDs fail with error `131062`.

## Asking for the number

Meta offers a **request contact info** button, on utility and marketing templates or in an interactive message. When the customer taps it, their phone number is shared in the chat and added to your contact book. The button text can't be changed.

> [!NOTE]
>
> **In Flowella.** Flowella's template editor doesn't offer the request contact info button, and Flowella can't send to a BSUID. Where a process needs the number, such as a delivery or a callback, ask for it in a Flow or in the conversation.

## What to do now

* **Keep customers in touch.** Customers you've exchanged messages with in the last 30 days, or who are in your contact book, keep arriving with their number.
* **Leave the contact book switched on**, so numbers keep arriving after 30 days.
* **Collect the phone number in your forms and Flows** for processes that depend on it.
* **Check your own integrations.** Anything that receives Flowella's webhooks or reads Meta data directly should not assume every customer has a phone number.

## Related

> [card] [Business username](https://knowledge.flowella.io/whatsapp/accounts/business-username.md)
>
> Reserve your business's username.

> [card] [Message types](https://knowledge.flowella.io/whatsapp/messaging/message-types.md)
>
> What customers and businesses can send.

> [card] [Data privacy and residency](https://knowledge.flowella.io/whatsapp/messaging/data-privacy-and-residency.md)
>
> How Meta stores message data.

> [card] [Platform changes](https://knowledge.flowella.io/whatsapp/platform-changes.md)
>
> When usernames reach customers.

Checked against Meta's [Business-scoped user IDs](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids) documentation on 18 November 2026.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.