{"id":12585,"date":"2026-08-27T12:21:47","date_gmt":"2026-08-27T12:21:47","guid":{"rendered":"https:\/\/www.privyr.com\/blog\/?p=12585"},"modified":"2026-08-27T12:21:48","modified_gmt":"2026-08-27T12:21:48","slug":"which-sales-and-marketing-platforms-support-whatsapp-usernames","status":"publish","type":"post","link":"https:\/\/www.privyr.com\/blog\/which-sales-and-marketing-platforms-support-whatsapp-usernames\/","title":{"rendered":"Which sales and marketing platforms support WhatsApp Usernames "},"content":{"rendered":"\n

As of August 2026, a few platforms, including Privyr fully support WhatsApp Usernames and Business scoped user Ids (BSUIDs) and allow you to run campaigns and communications normally. <\/p>\n\n\n\n

WhatsApp is slowly rolling out WhatsApp usernames<\/a> for its 3.3 billion monthly active users after it recently announced username reservations<\/a>. Having a username means a WhatsApp user no longer needs to disclose their phone number to communicate on WhatsApp.\u00a0<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

So how does WhatsApp manage businesses that have been identifying users with their phone numbers? Well, if you\u2019re a business, WhatsApp will provide you with Business scoped user Ids (BSUIDs) instead of user numbers for identifying users. But BSUIDs will be unique to each business. <\/p>\n\n\n\n

This can change more than what appears at the top of the chat, especially if your business relies on WhatsApp for sales communications because many CRMs, WhatsApp marketing tools, and campaign platforms are originally built around contacting users on their WhatsApp through their phone number. <\/p>\n\n\n\n

As these changes happen gradually, many campaigns and integrations may face disruptions if your platform doesn\u2019t yet support WhatsApp usernames (or BSUIDs). This can have a huge impact on your sales if it depends on WhatsApp conversations. <\/p>\n\n\n\n

Now the question is: Does your sales platform support WhatsApp Usernames? And how to adopt your operations and tools to this change. Let us help you! <\/p>\n\n\n\n

Which sales and marketing platforms currently support WhatsApp Usernames?<\/h2>\n\n\n\n

As of August 2026, a few platforms including Privyr, Salesforce, Freshsales suite, SleekFlow, etc have documented support for WhatsApp’s new username model. How you deal with BSUID-only contacts can vary based on platforms.<\/p>\n\n\n\n

The table below details how major CRMs are adopting WhatsApp Usernames as of August 2026:  <\/p>\n\n\n\n

Platform<\/strong><\/td>Username \/ BSUID support<\/strong><\/td>Campaigns \/ broadcasts<\/strong><\/td>Automations \/ sequences<\/strong><\/td>Important limitations<\/strong><\/td><\/tr>
Privyr<\/td>\u2705 Yes<\/td>WhatsApp Campaigns, Broadcasts, BSUID contacts<\/td>Auto-Responder, Sequences, and WhatsApp Automations<\/td>Some workflows may depend on the phone number provided by the lead source<\/td><\/tr>
Salesforce<\/td>\u2705 Yes<\/td>Outbound WhatsApp campaigns to BSUID contacts<\/td>Marketing Cloud journeys and WhatsApp automations<\/td>As of 27 August 2026, Salesforce\u2019s documentation states that\u00a0 the features described \u201cdon’t become generally available<\/a> until the latest general availability date that Salesforce announces for this release\u201d<\/td><\/tr>
Freshsales Suite<\/td>\u2705Yes<\/td>WhatsApp campaigns, multi-step workflows. <\/td>Automated customer journeys, multi-step follow-ups<\/td>Authentication templates may still require a phone number. <\/td><\/tr>
SleekFlow<\/td>\u2705Yes<\/td>Messaging\/broadcast functionality supported<\/td>Existing Flow Builder automations continue<\/td>Sending to BSUID through its API isn’t currently supported<\/td><\/tr>
Zoho CRM<\/td>\u26a0\ufe0f Not clear<\/td>Marketing WhatsApp templates are supported, but BSUID-only broadcasts aren’t documented. <\/td>WhatsApp messages can be added to the workflows, but whether these work with BSUID-only contacts isn’t documented.<\/td>Zoho CRM’s current WhatsApp documentation still describes contacts and sending largely around phone numbers. As of 20 August, 2026 it hasn\u2019t released any documentation confirming BSUID support.<\/td><\/tr>
HubSpot<\/td>\u26a0\ufe0f Possibly phone-number dependent \/ not clear<\/td>WhatsApp templates can be sent through workflows, but BSUID-only sending isn’t documented.<\/td>WhatsApp messages can be automated through HubSpot Workflows, but HubSpot currently says the contact must have a valid WhatsApp Phone Number populated. <\/td>HubSpot\u2019s July 2026 documentation explicitly requires a valid WhatsApp phone number for workflow\/template sending, so BSUID-only automation is currently unclear.<\/td><\/tr>
Pipedrive<\/td>\u26a0\ufe0f Not clear<\/td>Its native WhatsApp integration supports conversations and template messages, but BSUID-only broadcasts isn\u2019t confirmed<\/td>Not clear. The native WhatsApp integration documents replies and template messages, but not WhatsApp automation or sequences. <\/td>As of August 20, 20226, Pipedrive is yet to release any official documentation announcing support for BSUID-only contacts <\/td><\/tr>
Monday CRM<\/td>\u26a0\ufe0f Not clear<\/td>Supports campaigns, but its documented campaign features are email-based rather than native WhatsApp broadcasts.<\/td>Sequences support automated\/manual emails, tasks and call tasks, but WhatsApp sequences aren’t documented.<\/td>As of August 20, 20226, Monday CRM hasn\u2019t released any official documentation announcing support for BSUID-only contacts<\/td><\/tr>
LeadSquared<\/td>\u26a0\ufe0f Not clear<\/td>WhatsApp marketing campaigns and bulk messages are supported, but BSUID-only campaign recipients are not documented.<\/td>WhatsApp notifications, reminders and automated messages are supported, but BSUID compatibility is unclear.<\/td>As of August 20, 20226, LeadSquared hasn\u2019t released any official documentation announcing BSUID-only contacts support<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Why should you have a platform that supports WhatsApp Usernames now?<\/h2>\n\n\n
\n
\"BSUID<\/figure><\/div>\n\n\n

As WhatsApp gradually rolls out WhatsApp Usernames, WhatsApp webhooks already include the Business-Scoped User ID (BSUID) even when the user has not enabled a username. Current webhook can contain the phone number plus the BSUID since the phone number is still mostly available. <\/p>\n\n\n\n

The advantage of having a platform that supports WhatsApp Usernames in the initial stages is that it stores the BSUID alongside existing customer identifiers, so future conversations can be mapped correctly when the phone number is no longer available.<\/p>\n\n\n\n

If your sales tool doesn\u2019t support BSUIDs, your future WhatsApp communication and workflows could be disrupted. As more people start using usernames instead of sharing their phone numbers, activities like managing leads, follow-ups, automations, and customer records may become much messier.<\/p>\n\n\n\n

A sales platform supporting WhatsApp Usernames in the early stages will allow you to: <\/p>\n\n\n\n