Twilio WhatsApp Webhook Updates
As Meta rolls out WhatsApp Usernames in 2026, Twilio is updating its Programmable Messaging API to support Business Scoped User IDs (BSUIDs). This migration affects every Twilio customer using the WhatsApp channel for customer communication.
What Is Changing?
Historically, Twilio webhooks would pass the user's phone number in the From field (e.g., whatsapp:+1234567890). With BSUIDs, if a user contacts you via a username, the From field will contain their unique scoped identity instead — an opaque alphanumeric string that cannot be reverse-mapped to a phone number.
Webhook Payload Comparison
Legacy payload: {"From":"whatsapp:+1234567890","Body":"Hello"}
New BSUID payload: {"From":"whatsapp:BSUID.a1b2c3d4e5f6","Body":"Hello"}
How to Prepare Your Twilio Integration
- Update your webhook handler to detect the
BSUID.prefix in theFromfield - Add a
bsuidcolumn to your CRM's contact records alongside the existingwa_id - Implement a mapping table to associate BSUIDs with your internal customer IDs during the dual-mode period
- Test your updated webhook using Meta's Webhook Debugger or the RezervSpot BSUID Audit Tool
Dual-Mode Period
During Q3 2026, Twilio will pass both formats. After Q4 2026, all new username-initiated conversations will use BSUIDs exclusively. Existing conversations retain their original wa_id.