> For the complete documentation index, see [llms.txt](https://docs.omnichat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnichat.ai/en/announcements/whatsapp-username-and-bsuid.md).

# WhatsApp Username & BSUID

What's Changing and How Omnichat Has You Covered

### What's changing

From July 2026, WhatsApp users can gradually create an optional @username. When a customer adopts one, their phone number is no longer automatically shared with businesses. 

To keep customer identification intact, WhatsApp is introducing the Business-Scoped User ID (BSUID), a stable, privacy-safe identifier unique to your business. Username rollout begins in selected markets (including Singapore and Malaysia) from late July 2026, with full global rollout including Hong Kong from September 2026. 

You can read more about WhatsApp Username & BSUID at our blog : [WhatsApp Usernames & BSUID: The Essential Guide for Your Business 2026](https://blog.omnichat.ai/meta-whatsapp-usernames-bsuid-tutorial/)

### **What this means for your business**

* Customers who adopt a username may message you without sharing their phone number
* Without preparation, this could create duplicate contacts and break flows that rely on phone numbers
* With BSUID captured and linked to a phone number, username adoption has zero impact on that contact, so messaging, contact records, and conversation history all continue as normal

### What Omnichat is doing about it

*Already live*

* Capturing BSUIDs automatically from all inbound interactions (since 8 April 2026) and all successfully delivered outbound messages (since 17 June 2026), no setup required
* BSUID visible in your contact profiles and audience lists today
* BSUID field included in all webhook and Open API responses alongside phone number
* Automatic contact matching: when a customer with a username messages you, Omnichat uses the captured BSUID to match them to their existing contact, preventing duplicate
* Send messages via BSUID across all flows (conversations, OMO, broadcasts, journeys, automations, API (excluding broadcast api)
* QR code loyalty point redemption for BSUID-only contacts
* One-way BSUID sync from Omnichat to Salesforce / HubSpot
* Search contacts by BSUID in Channel Contacts
* Get Contact Info card, a native share button in chatbot flows so customers can share their phone number in one tap

### Share Contact Info

#### A. New chatbot card "Share Contact Info"

{% hint style="info" %}
Supports the new chatbot card "Share Contact Info", allowing merchants to add this card to chatbots to build contact collection flows.

Location: Advanced Automation > Chatbot > Add/Edit WhatsApp Chatbot > Add Block > Add Cards
{% endhint %}

**Feature Spec**

* Card format
  * Body
    * Compulsory
    * Maximum of 1024 characters.
  * Titles and headers are not supported.
  * Button actions are not supported.
    * WhatsApp system will automatically convert and translate the corresponding official standard translation based on the user's phone's current language settings.\
      Example: 
      * English: Share Contact Info
      * Traditional Chinese: 分享聯絡資訊
  * Additional Actions cannot be set because clicking the button does not immediately trigger the Meta Webhook; the user needs to click "send" separately.
    * Additional Actions:
      * Tagging
      * Set custom attributions

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FmncnMavsYrF2bO8sfF1g%2Fimage.png?alt=media&amp;token=36b77128-d6a4-4ac0-8d87-8a70d7fe470e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FGCny1Ah2YiLQ8rlKVjU5%2Fimage.png?alt=media&amp;token=b1cdfbf8-3f0b-41b1-a2bd-611a026a0833" alt=""><figcaption></figcaption></figure>

* Card format
  * The text displayed on the buttons will be determined based on the console's language.
    * English: Share Contact Info
    * Traditional Chinese: 分享聯絡資訊
    * Simplified Chinese: 分享联系信息
    * Japanese: 連絡先を共有する
* Processing older version of chatbots
  * Existing "Get Contact Information Cards" templates can be edited and resubmitted, but there are limitations on the number of fields:
    * Editable:&#x20;
      * Basic Settings: Display Name, Applicable Users, Category
      * Content Settings: Template Subcategory (Standard or Flow), Text
    * Non-editable:
      * Basic Settings: Applicable Accounts
      * Content Settings: Template Name, Template Category, Language
      * Template subcategories cannot be switched to "Media Carousel Cards"
  * When the card has been created in the newer version of chatbot, the following functions are supported:
    * View "Get Contact Information Card" (excluding settings)
    * Dragging card order
    * Delete card&#x20;

**Supports sending "Share Contact Information Card" related function pages**

* Conversation (Inbox)
  * Sending chatbot via saved reply
  * Keyword-triggered chatbot
* Group message
  * Group messaging - saved reply&#x20;
* Journey
  * Chatbot
* Supported dialogue types:
  * WhatsApp conversation
  * WhatsApp Coexistence conversation

**Supports JSON Copying**

Supports generating editable JSON for copying (editable content is the body text, specifications are the same as in the content above).

**Known limitations**

* The chat function only supports the new version of chat; it is not supported in the older version 1.0
* The "Share Contact" button cannot coexist with other buttons.
* Button text cannot be customized; it must use the official WhatsApp translation.
* Not applicable to the "System Notifications" option (chat to order).

#### Contact Webhook Related Processing

Condition: When a user shares contact information a contact webhook will be triggered.

* Upon receiving the webhook, the contact information (customer name, phone number) will be updated immediately.
* Contact information within the conversation will also be updated in real time, including in the following locations:
  * Customer's name in chatroom
  * Customer's phone number in chatroom
  * Customer information on the right side of the chatroom

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FDdUx7Ac1obrIDVVchTOw%2Fimage.png?alt=media&amp;token=2b2a8f22-8757-445c-84bd-7d7f6541cbae" alt=""><figcaption></figcaption></figure>

#### B. New Template format "Share Contact Template"&#x20;

#### Feature Spec

* Added "Share Contact Template" to the template type
* Applicable template categories: Marketing, Utility
* This button cannot coexist with other buttons (quick reply, make a call, and open a website cannot be included).
* Not applicable to "System Notification" type objects.

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FsDQ5AvXXSAPJSH9jPX3B%2Fimage.png?alt=media&amp;token=cb9134ec-46ea-417f-b0e9-31d1ade864d0" alt=""><figcaption></figcaption></figure>

**Supported Sending Scenarios**&#x20;

Supports selecting and sending 'Share Contact' templates in the following features:

* Live Chat
* Customer Journey
* Broadcast
* Mass Messages

**Editing and Re-submission**&#x20;

Created 'Share Contact' templates can be edited and re-submitted for approval, with the following field restrictions:

(1) Editable:

* Basic Settings: Display Name, Target Audience, Category
* Content Settings: Template Subcategory (Standard or Flow), Body Text

(2) Non-editable:

* Basic Settings: Applicable Accounts
* Content Settings: Template Name, Template Category, Language
* Template Subcategory cannot be switched to 'Media Carousel'

**Supports JSON Copy**&#x20;

Supports generating updated JSON for copying (editable content is restricted to the body text, following the same specs as above).

**Known Limitations**

* Live Chat support is limited to the new Live Chat interface; legacy version 1.0 is not supported.
* The 'Share Contact' button cannot coexist with other buttons.
* Button text cannot be customized and will strictly use WhatsApp official default translations.
* Not applicable to the 'System Notification' option (chat to order).

### **Need help?**

If you have questions about this update or need assistance reviewing your integration, please contact our support team. You can also refer to our Open API Documentation for full API details.