WhatsApp Usernames now supported in Twilio Platform and Messaging APIs
Twilio now supports WhatsApp Usernames, which allow users to adopt optional usernames that mask their phone numbers and interact with businesses via Business Scoped User IDs (BSUID). This identifier is exposed in message webhooks and Event Streams.
WhatsApp Usernames is now supported on the Twilio Platform and Messaging APIs for WhatsApp. WhatsApp now allows users to adopt usernames. A username can optionally mask a user's personal phone number and allows them to interact with businesses through Business Scoped User IDs (BSUID). Twilio exposes this identifier in message webhooks and in Event Streams event data. Meta is releasing this functionality in multiple waves, starting on July 7, with additional countries to follow at later dates. Please check our documentation for the latest rollout schedule.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Insights now tags HD audio calls
Voice Insights now automatically tags calls as HD Audio when they use AMR-WB or Opus codecs, helping you confirm endpoint configuration and correlate HD audio usage with transcription accuracy and customer satisfaction. The system also tags calls as Downsampled when HD audio is converted to narrowband, visible in Console, REST API, and Event Streams.
RCS messaging now supported on all major Canadian carriers
Twilio now supports sending RCS messages to Rogers phone numbers, completing RCS coverage across Canada's major carriers. Existing RCS Senders approved by other Canadian carriers are automatically submitted to Rogers for approval.
RCS messaging now supported on all major Canadian carriers
RCS messaging is now available to Rogers phone numbers in Canada, completing coverage across all major Canadian carriers. Previously approved RCS Senders will automatically be submitted to Rogers for review with no action required.