# Gupshup, BSUID, and usernames: what BSPs like Gupshup are doing

> Gupshup built an identity layer for Meta's move to BSUID and usernames on WhatsApp Business. See how the feature toggle, Identity Graph and parked messages work, and what to check with your provider.

- **HTML version:** https://tolky.to/en/blog/gupshup-bsuid-usernames-whatsapp-business-2026
- **Author:** [Marlos Carmo](https://tolky.to/en/author/marlos), Co-founder of Tolky
- **Published:** July 1, 2026
- **Reviewed:** November 17, 2026
- **Language:** en

## Summary

Gupshup, a WhatsApp API provider, offered a compatibility layer for Meta's identity change: the BSUID can be enabled through a feature toggle, and the platform tries to keep the phone number whenever it can resolve it. Meta has delivered the BSUID in webhooks since April 2026 and opened business usernames on 06/29/2026; what matters now is checking with your provider what is active and preparing your CRM, bots, and campaigns for contacts without a phone number.

This is a review of an announcement from a third party, **Gupshup**, about the WhatsApp Business transition to the **BSUID** and **usernames**. It describes what providers like Gupshup are offering and works as a checklist for any company that reaches the API through an intermediary. It does not describe Tolky's infrastructure.

Since the topic has moved past the roadmap stage, here is Meta's timeline ([official documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids)): the BSUID has appeared in webhooks since April 2026; on **June 29, 2026** businesses could reserve and adopt corporate usernames; in July, sending by BSUID and the button to request a phone number became available; on 08/11 BSUID changes began arriving as system messages (`user_changed_user_id`); and on 10/23 a limit of 2 username changes per 14 days took effect.

The starting point is the post on [BSUID and usernames](https://tolky.to/en/blog/bsuid-whatsapp-usernames-what-changes-2026): the BSUID is the business-scoped user identifier and lets you reply to someone even without their phone number. Here the focus is what changes when a provider sits in the middle.

*Updated on November 17, 2026.*

**In short:**

- **The BSUID is the business-scoped user identifier** and lets you reply without the person's phone number.
- **The phone is not going away, but it is no longer a guarantee.** If a send has both phone and BSUID, the phone takes precedence; store both.
- **Gupshup offers an identity layer** (BSUID feature toggle and Identity Graph); some details come from its announcement, with no confirmation in public documentation.
- **Prepare your CRM, bots and reports** for hybrid identity: phone, BSUID, username and a canonical key.
- **Ask your provider in writing** for the toggle state and the policy for parked messages.

## What did Gupshup promise for the BSUID transition?

According to the announcement, the proposal is operational continuity: an identity layer that resolves **BSUID, phone, and username** whenever possible, with two paths:

1. enable BSUID support and start receiving the new identifier;
2. keep operating with phone numbers while the platform resolves identity behind the scenes.

So the change does not have to be a big-bang migration. But time is not a license to ignore it: it is a window to prepare data, reports, automations, and human service for a world where the phone is conditional.

## What is the BSUID feature toggle?

In public sources, Gupshup's partner documentation indicates that, **by default, the platform delivers only the phone number** and omits the `user_id` fields in the v2 and v3 subscriptions; to enable it there is a per-app partner API ([API to enable the BSUID flag](https://partner-docs.gupshup.io/docs/api-to-enable-bsuid-flag-for-an-app)). With BSUID enabled, Gupshup sends the BSUID alongside the phone while it is available; as usernames spread, the combination can become BSUID plus username, or BSUID only.

The decision has architectural impact:

- Enabling early helps enrich the CRM and test deduplication before volume grows.
- Leaving it off reduces immediate change but can hide dangerous phone dependencies.
- A mature operation enables it in a controlled environment, measures, and only then releases to production.

The mistake is treating the toggle as a "switch on later" button. The sooner your base captures BSUIDs, the lower the chance of duplicating contacts when conversations arrive without a phone. Gupshup's support page on [Username / Business-Scoped User ID](https://support.gupshup.io/hc/en-us/articles/55873677826713-Username-Business-Scoped-User-ID) may block automated access; if it does not open, try it in a browser.

## What are the Identity Graph and parked messages?

The announcement to partners describes an **Identity Graph**: a repository mapping BSUID to phone, fed by inbound and outbound interactions. On each message, the platform would ask "do I know the phone behind this BSUID?" If so, it preserves the experience of legacy integrations; if not, the message may arrive with only a BSUID or be held.

This mechanism also provides for "parked" messages: held for up to 30 days when the phone is unavailable, with a recovery API described as future. **These details come from Gupshup's announcement and have not been confirmed in public documentation**; treat them as provider information and ask for it in writing.

It is also important to separate two things: **BSUID generated for all users** (Meta already does this in webhooks) and **username adoption**, which is gradual. If your provider says BSUID generation already covers all users, that is consistent with Meta; it does not mean everyone already uses a username.

## Example: the ad lead with a username

Picture a Click-to-WhatsApp ad lead who uses a username and has never talked to the company. The message arrives without a phone. If the provider holds it as "parked", the lead sits idle, the sales SLA is blown, and the deal cools. A prepared flow creates the contact with the BSUID, replies within the service window, asks for the phone with context if needed, and merges with the existing record. Holding is a safety net, not a service strategy.

## What are business usernames?

The announcement covers **business usernames**: exploring Meta's suggestions, reserving or requesting a name, tracking approval, and setting the username. It improves brand discovery; the BSUID resolves the user's identity in the relationship with the business. They are parts of the same movement:

- business username: how customers find the brand;
- end-user username: how customers talk without revealing their phone;
- BSUID: the stable technical identity of that relationship.

## How do you send campaigns to a BSUID?

The announcement indicates that, even when sending to a BSUID is possible, the Identity Graph will try to use the phone whenever it exists. This is consistent with Meta: sending accepts `to` (phone) or `recipient` (BSUID), and with both, **the phone takes precedence**. Three areas need attention:

**Consent.** BSUID does not remove opt-in, the service window, and templates. Outside the 24-hour window only an approved template works, and every message is charged; see [the new WhatsApp Business pricing](https://tolky.to/en/blog/whatsapp-business-pricing-october-1-brazil).

**Attribution.** Ads that cross WhatsApp and CRM must accept the BSUID as a primary identifier.

**Reports.** Dashboards keyed by phone can duplicate contacts. Ideally, report by canonical contact, with phone and BSUID linked. See why this matters in [WhatsApp is not a CRM](https://tolky.to/en/blog/whatsapp-is-not-crm).

## How do you ask for a phone number proactively?

When the phone is needed (authentication, delivery, billing, legacy system), Meta offers the **`REQUEST_CONTACT_INFO`** button in utility or marketing templates, and the `request_contact_info` interactive message. The label is fixed ("Share Contact Info") and the phone arrives by webhook when the user taps. In ordinary service, the BSUID may be enough; demanding a phone in every flow lowers conversion and goes against Meta's own privacy direction.

## What does your company need to do now?

If your operation uses Gupshup or another provider that abstracts Meta's API:

1. **Confirm the BSUID toggle state:** enabled, in which environment, which fields show up in webhooks, and how v2 and v3 payloads change.
2. **Integrate the business username APIs:** reserve or request the name and track approval.
3. **Update the CRM for hybrid identity:** `phone`, `bsuid`, `username`, and a canonical internal key.
4. **Review bots and automations** that assume `from` is a phone number.
5. **Define a policy for parked messages:** who monitors, under what SLA, and what happens to paid-media leads.
6. **Train human agents:** a contact without a phone is not suspicious, it may simply be a customer with a username.

## What is Tolky's role?

The risk is not just in the webhook: it is in the whole chain of CRM, queues, AI agents, reports, campaigns, and data governance. For Tolky, the goal is to keep the customer's history unified, with the AI and human agents seeing the same contact whether the conversation arrives with a phone, BSUID, or username, and to ask for additional data only when the process requires it. To learn how this works in your operation, talk to the team.

**Want to review your base and flows for contacts without a phone number?** [Talk to the Tolky team](https://tolky.to/en/contact).

## Frequently asked questions

### What is the WhatsApp BSUID?

The BSUID is the business-scoped user identifier. It lets you reply to someone even without that person's phone number. See the post on [BSUID and usernames](https://tolky.to/en/blog/bsuid-whatsapp-usernames-what-changes-2026).

### Does the BSUID replace the phone number?

No. When sending, if a message has both a phone number and a BSUID, the phone number takes precedence. What changes is that the phone is no longer a universal guarantee, so your records need to store both.

### What are parked messages?

According to Gupshup's announcement, they are messages held for up to 30 days when the phone behind a BSUID is not available. This detail was not confirmed in public documentation, so ask your provider for it in writing.

### Do I need to turn on the BSUID feature toggle?

In Gupshup's partner documentation, the platform delivers only the phone number by default. Turning it on early in a controlled environment helps capture BSUIDs and avoid duplicate contacts when conversations arrive without a phone.

### How should the CRM store contacts with a BSUID and a username?

With a hybrid identity: phone, BSUID, username and a canonical internal key that ties the three together. That prevents duplicate contacts and lets you report by person, not by identifier. See the [Tolky CRM solution](https://tolky.to/en/solutions/crm).

### How do I ask for the phone of a contact who only has a username?

Meta offers the REQUEST_CONTACT_INFO button in utility or marketing templates and the request_contact_info interactive message. The phone arrives by webhook when the person taps. In regular support, the BSUID may be enough.

### Does the BSUID remove opt-in and templates?

No. Outside the 24-hour window, only approved templates are allowed, and each message is charged. See [WhatsApp Business new pricing](https://tolky.to/en/blog/whatsapp-business-pricing-october-1-brazil).

### What does Tolky do with contacts without a phone number?

Tolky's goal is to keep the customer's history unified, with the AI and human agents seeing the same contact whatever the identifier. To learn how this works in your operation, see the [plans](https://tolky.to/en/pricing) or talk to the team.

---

The phone has not disappeared, but it is no longer a universal guarantee. Mature operations treat identity as a set: phone, BSUID, username, consent, and history. Teams that wait for the first lead without a phone to find the problem will end up with real conversations stuck on an old premise.

---

This is the Markdown version of the page. The full version, with images and navigation, is at https://tolky.to/en/blog/gupshup-bsuid-usernames-whatsapp-business-2026

Tolky: https://tolky.to
