Meta is rolling out Business-Scoped User IDs (BSUIDs) as the primary way to identify customers on the WhatsApp Business Platform, supporting WhatsApp's upcoming username functionality, where customers may interact with businesses without exposing their phone number. This has a genuine, practical implication for how Zoho SalesIQ handles some WhatsApp conversations, particularly template-based follow-ups after a conversation has gone quiet.
BSUID isn't something you request or configure. Meta generates a unique Business-Scoped User ID automatically for every customer-business relationship. When a customer messages your WhatsApp number, Meta includes the BSUID in the webhook payload, and SalesIQ receives and stores it automatically as the primary customer identifier for WhatsApp conversations.
Previously, Meta also included the customer's phone number in every webhook. With WhatsApp usernames, that's no longer guaranteed. A customer using a username may now arrive identified by BSUID only, with no phone number attached at all.
A phone number is still included if either of these applies:
If neither condition applies and the customer is using a username, the webhook contains the BSUID only.
If you genuinely need a customer's phone number during an active conversation, you can request it. The customer sees a prompt in WhatsApp asking whether they want to share their number, and can accept or decline. Accepting delivers the phone number via webhook and stores the mapping going forward; declining means the conversation continues on BSUID alone.
For most WhatsApp conversations, there's no change to the existing experience.
If a customer messages you and the conversation is within WhatsApp's 24-hour customer service window, you can continue it as usual. This flow is entirely unaffected by the BSUID change.
No impact here. WhatsApp Broadcasts sent using phone numbers continue to work exactly as before.
| Scenario | Current Status in SalesIQ |
|---|---|
| Customer identified with BSUID + phone number | Supported |
| Customer identified with BSUID only | Supported for active conversations |
| Continue/reopen conversation within the 24-hour window | Not affected |
| Template reopen after 24 hours, phone number available | Supported |
| Template reopen after 24 hours, BSUID only | Not currently supported |
| Broadcast using phone numbers | Not affected |
A retail customer in a region where Meta has enabled BSUID-only identification messages your WhatsApp number about a product return. An operator handles the conversation and initiates the return process, then the customer goes offline. Twenty-six hours later, the operator tries to send a WhatsApp template message to follow up on the return status. Because the customer arrived with a BSUID only, and no phone number was collected during the active conversation, the template send fails, and the conversation can't be reopened.