Skip to content

WhatsApp usernames and Business-Scoped User IDs in StrataBlue Support

WhatsApp is rolling out usernames for people who want to chat with businesses without sharing their phone number. When this happens, a WhatsApp contact in StrataBlue Support may show a username, or may not show a phone number at all.

StrataBlue Support supports receiving and replying to BSUID-only WhatsApp conversations. Your team can continue receiving and replying to WhatsApp messages even when WhatsApp does not share the customer’s phone number.

For agents, day-to-day work stays the same. New WhatsApp conversations continue to arrive in StrataBlue Support, and agents can reply from the conversation as usual.

The only visible difference is that some contacts may not have a phone number. If WhatsApp provides a username, StrataBlue Support can show that username on the contact. If the customer had older conversations with your team using a phone number, those conversations may appear under Previous Conversations.

BSUID stands for Business-Scoped User ID. It is the WhatsApp identity that lets a business keep messaging a customer when their phone number is not available.

When replying from the StrataBlue Support dashboard, agents do not need to copy, store, or manage BSUIDs manually. StrataBlue Support uses the active WhatsApp identity associated with the conversation.

StrataBlue Support replies using the active WhatsApp identity on the conversation.
If WhatsApp provides a phone number, StrataBlue Support can use it. If WhatsApp does not provide a phone number, StrataBlue Support uses the BSUID provided by your WhatsApp provider. This keeps the current conversation replyable while preserving older conversation history.

For WhatsApp Cloud API inboxes (Quick setup or manual), StrataBlue Support supports contacts who only have a BSUID. Agents can receive and reply to these conversations from StrataBlue Support.

Supported WhatsApp message types can continue to work with BSUID-only contacts, including normal replies, supported templates, interactive messages, and attachments.

  • Templates: authentication templates (one-time codes) cannot be sent to a contact without a phone number.

  • Campaigns: StrataBlue Support sends to the contact’s phone number if it has one, and to their BSUID if it does not. A contact with neither, or with more than one BSUID in that inbox, is skipped.

For Twilio WhatsApp inboxes, StrataBlue Support supports the WhatsApp identity information sent by Twilio, including BSUID information when it is available on the Twilio account.

Twilio support can depend on Twilio’s own WhatsApp capabilities and rollout status. If a message does not deliver, check the exact Twilio delivery status or provider error.

On WhatsApp Cloud API inboxes, agents can ask a contact who has no phone number to share it. In the conversation, click Ask the customer to share their WhatsApp phone number in the reply box.

  • Within 24 hours of the customer’s last message, StrataBlue Support sends the request as a normal message. After that, you need an approved template with a button that asks for contact information.

  • You can have only one request waiting at a time. The button then shows Contact information request pending.

  • This is not available on Twilio inboxes.

The customer controls whether they share it. If they share their number, StrataBlue Support updates the contact when the response safely matches the current WhatsApp conversation. If the shared number appears to belong to another contact, StrataBlue Support marks it for review instead of merging it automatically. The request shows as Waiting for contact information, then Phone number shared, or Phone number needs review if the number belongs to another contact.

When sending another message in an existing conversation, use that conversation’s message endpoint. StrataBlue Support sends through the WhatsApp identity already associated with the conversation.

When creating a conversation through the API, source_id selects the contact’s messaging identity within the inbox. A contact may have both a phone-number identity and one or more BSUID identities. These should not be treated as interchangeable.

Selecting a different identity can create a separate conversation, even when Lock to single conversation is enabled. That setting reuses conversations within the selected identity; it does not combine conversations across identities.

Avoid choosing the first or last entry in contact_inboxes without checking its identity and inbox. To continue an existing exchange, retain its conversation ID rather than creating another conversation using a different source_id.

Existing conversations are not automatically merged when another identity is used.