Meta is fundamentally shifting WhatsApp user identification from phone numbers to Business-Scoped User IDs (BSUIDs) for users who opt into Usernames, with regional testing commencing June 30th, 2026 and general availability by August 2026. This change will ripple through Zendesk implementations and the Sunshine Conversations API, creating a scenario where new or updated WhatsApp contacts may no longer carry phone number data—a field that has been foundational to contact management and routing logic for years. For most standard implementations, Zendesk will handle the transition automatically, but teams relying on phone numbers as a critical identifier face material work ahead.
The implications are substantial for CX operations already stretched thin managing omnichannel complexity. Any team with custom API integrations reading the externalId field, outbound messaging workflows, or contact creation logic tied to phone numbers must audit and remediate before June 30th. The question becomes whether this shift will expose architectural weaknesses in existing implementations—particularly for teams that have built customer journey logic around phone-based deduplication or compliance workflows that depend on phone number validation. Organisations should treat this not merely as a technical migration but as an opportunity to assess whether their contact identity strategy remains fit for purpose in an increasingly username-centric messaging ecosystem.
The timeline is tight but manageable for proactive teams. Zendesk has provided clear guidance on what requires action, and the six-month runway to general availability allows for proper testing and rollback planning. However, teams managing multiple WhatsApp Business API integrations across different platforms should begin auditing dependencies now rather than waiting for June, particularly if they operate in regions where WhatsApp Username adoption accelerates faster than expected.
Meta is making significant changes to how WhatsApp users are identified, which will start to take effect from June 30th, 2026 (regional testing), with General Availability planned for August 2026. This article explains what is changing, whether you need to act, and what to do if you do.What’s changi