How can we help?

Impact of Usernames on Zenvia Customer Cloud Journeys
2 min
Created by Maria Malheiro on 8/5/2026 6:15 PM
Updated by Maria Malheiro on 9/23/2026 3:23 PM

The implementation of Meta’s Usernames feature — the new @ usernames — introduced a new way of identifying users in the WhatsApp Business ecosystem. As part of this evolution, Meta now provides the Business Scoped User ID (BSUID), a unique identifier associated with a user within the scope of a Business Account.

To learn more about what Usernames are and what changes in your operation, check our documentation.

⚠️ Attention: It is important to note that BSUID does not apply when a chatbot flow is transferred to a commercial or support service.

This change also impacts journeys within Zenvia Customer Cloud. See the details below.


Impacted journey — Contacts

1. Read-only BSUID field

To access this field, go to Contacts > Contact Database > Edit Contact.

When editing a contact, the system now displays a new section called WhatsApp Identifiers, which contains the BSUID (Business Scoped User ID) field.

Field display

The BSUID field is displayed in read-only mode, allowing only the viewing of the identifier assigned by Meta.

Because the BSUID is generated and managed exclusively by Meta, manual editing is not allowed.

The BSUID value is obtained exclusively from Meta through the WhatsApp Connector.

This identifier cannot be created, imported, or modified by the user through the Zenvia Customer Cloud interface or through manual contact update operations.

Whenever the system receives an event from Meta containing the BSUID, the Contact Manager is automatically updated to store this identifier in the corresponding contact record.



Did this article solve your doubts?
Recently viewed