Product changelog and announcements

Any direct customers who do not already have access to WhatsApp Self Sign-up can now upgrade directly within the Twilio Console. This enables: 

• Faster onboarding register additional WhatsApp Senders in under 5 minutes—including Bring-Your-Own-Number (BYON) WhatsApp Senders (e.g., non-Twilio numbers).

• Access to Meta-provided insights within the Meta WhatsApp Business Manager.

• Ability to add your WhatsApp Sender as the Contact Button to a Facebook page or Instagram account.

• Meta advertising with Click to Whatsapp Ads.

• Self service ability to directly apply for a WhatsApp Official Business Account (blue checkmark) with Meta.

Twilio now offers rich messaging on RCS through the Content Template Builder. You can now create and send rich cards, media, and rich card carousels. Twilio will support more rich RCS functionality in the near future.

When you send a rich content message through Messaging Services, Twilio will automatically deliver RCS rich content to compatible devices. For devices that do not support RCS , Twilio will send the defined fallback via SMS or MMS. You can define a twilio/media or twilio/text type as a fallback within your rich content template. To learn more about how to create and send rich content on RCS see our docs here. If you want to learn more about RCS generally and request access, you can do so here. 

The Compliance Embeddable is a white-label React component designed to seamlessly integrate into an ISV's web application as an iframe. This product enables ISVs to securely collect compliance information from their customers and send it directly to Twilio, streamlining compliance and shortening customer’s time-to-market. For ISVs, the Compliance Embeddable serves as a great alternative to manually collecting information from customers, and requires less development work compared to integrating with the Twilio Toll-Free Verification APIs and building their own UI.

The Compliance Embeddable is offered for free and is now available in Public Beta. Please follow the instructions in Twilio Docs to get started.

We are excited to announce an enhancement to the Twilio Messaging Service that improves the delivery of multimedia content to destinations that do not support MMS. With the updated MMS Converter feature, Messaging Service can now select SMS-only capable senders when sending messages to destinations that convert MMS to SMS links.

Twilio is excited to announce support for TCR’s Campaign Connectivity Partner (CNP) Migration Tool. This enhancement allows Campaign Service Providers (CSPs) to seamlessly migrate directly registered TCR campaigns to Twilio from other messaging API providers without the need for re-registration.

Key Benefits:

• Reduced Disruptions: Campaigns remain active during the migration process, ensuring uninterrupted messaging.

• Simplified Transfers: A secondary CNP chain is created and transitions automatically to the primary chain once all approvals are finalized.

• Cost-Effective: Migration incurs only an $8 fee per campaign. 

For more information, visit our Help Article on Direct TCR Registration for Externally Registered Campaigns, and review our API documentation for the registration process.

RCS now offers the option to create visually engaging messages with images, video and audio content globally. When you send media messages through Messaging Services, Twilio will automatically deliver RCS media messages to compatible devices. Devices that cannot receive media via RCS will still receive MMS messages where supported or a link to the media. If you want to learn more about RCS and request access, you can do so here.

Starting January 6, 2025, Twilio phone numbers will automatically display all inbound messages in Messaging Logs and Insights, even without an inbound message URL configured. Additionally, all received inbound messages will be billed according to Twilio’s pricing list, even if no inbound message URL is configured.

Twilio is now selecting the “Secondary DCA Sharing Status” for all carriers in The Campaign Registry (TCR), including AT&T, Verizon, T-Mobile, US Cellular, Interop, and Clearsky.

What’s New for Customers:
Campaigns registered via TCR, externally registered campaigns, will now receive the CAMPAIGN_DCA_COMPLETE webhook from TCR. This webhook confirms that the campaign has been vetted and approved by all designated DCAs.

Starting December 3, 2024:
Twilio will backfill the Secondary DCA Sharing Status for existing campaigns registered for US Cellular, Interop, and Clearsky in TCR. This process will also trigger the CAMPAIGN_DCA_COMPLETE webhook for these campaigns.

As of November 21st, we have released a new messaging status update schema in Event Streams. Status update responses now include the number of message segments and the status update timestamp in ISO 8601 format.

Customers can now seamlessly add Over-The-Top (OTT) channel senders to their Messaging Service using our API.