Twilio Changelog

The Twilio Programmable Voice iOS and Android SDKs (mobile) now each have a suite of “Preflight” APIs. Previously supported only on the Voice JS SDK, these new mobile diagnostics tools provide pre-call assessments of network stability, bandwidth, latency, jitter, MOS scores, and packet loss. This enables customers to enhance user experience by showing network warnings, prioritizing mobile data, or preventing calls on unreliable networks, ensuring more successful connections.

Check out the docs for more information on how to use the new functionality in your application. We can’t wait to see what you build!

On December 9, 2024 some traffic will begin to use Umatilla (us2) for conference mixing if the majority of participants are joining from the Umatilla (us2) edge location. On January 7, 2025 all conferences where the majority of participants join from the Umatilla (us2) edge location will be mixed there; Umatilla (us2) will also become selectable as a Programmable Voice Conference mixer region in TwiML and via API.

We're launching the v3 Regulatory Compliance API Pilot, aimed at improving the Twilio onboarding API experience.  This pilot is opt-in, and we're inviting interested customers to express their interest.

Capabilities of the v3 Regulatory Compliance API Pilot:

• Fewer Calls to Create Bundles: The v3 API simplifies the process of creating Regulatory Compliance Bundles by reducing the number of requests needed. Unlike the v2 API, which requires multiple steps per requirement (ex: Authorized Individual, a Business Address, and a Business Name), the v3 API consolidates these into a single request. With more complex registrations, the benefits are greater.

• Single Call to Fetch Bundle Details: Getting bundle details is simplified into a single request.

• Improved Error Codes: Errors are now surfaced in the API and error dictionary allowing for a more programmatic approach to error handling and less time troubleshooting. 

• Common API schema across Programs: The v3 API introduces a unified schema, supporting multiple registration types across Twilio’s products/channels (ex: A2P, AlphaNumericSender), simplifying compliance management, and bringing consistency across channels.

**Important Note:  Pilot access is limited and the Twilio Product team will reach out to interested customers regarding access.

We’re excited to announce that Flex UI 2.10.0 is now available.

This release includes the public beta release of a new Teams view that enables you to organize agents into teams, allowing supervisors to view, filter, and interact with their agents more efficiently. You’ll also notice a public beta feature that enables agents to natively view Flex UI in Español (México) or Português (Brasil). 

In the next few weeks, you’ll receive upcoming enhancements that will only be available on Flex UI 2.10.0 and later. These enhancements include the ability to classify customer interactions by topic and subtopic in Agent Copilot, and Webchat 3.0 support for configurable pre-engagement forms and context as well as a new end chat button for customers. Watch the coming soon section of the release notes for details as these updates become available.

For complete details, see the Flex UI release notes for 2.10.0.

Starting December 16, 2024, Twilio’s Webhook service will expand the payload for deferred events to include two additional fields: “from” and “domain.” This change enhances data availability, enabling you to gain richer insights from your event data, specifically for deferred events.

What's New?

• “from”: Displays the sender’s email address, providing greater visibility into the source of messages.
• “domain”: Shows the domain portion of the recipient's email after the “@” symbol, supporting more granular tracking and analysis.

How Does This Affect You?

If your system processes deferred event payloads with a fixed set of fields, the addition of these new fields may cause integration issues.

What Actions Should You Take?

To ensure uninterrupted service:

• Review and Update Your Integration: Modify your webhook processing logic to accommodate the new from and domain fields in the deferred event payload.
• Test Your System: After making updates, thoroughly test your system to confirm it handles the enhanced payload correctly.

For more information, please review our Webhook Documentation.

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.

Starting March 3, 2025, Twilio will rotate the end-user certificate and will update the list of supported cipher suites in all Twilio REST APIs. 

End-user Certificate Rotation

Only the end-user certificate will be renewed, as well as the certificate serial number. The root and intermediate certificates will remain the same. Such updates are common practice and do not impact customers that are using Twilio's services unless you are pinning certificates or are managing them manually. Customers using the official Twilio Helper Libraries should not experience any impact as they are designed to handle certificate rotations.

We highly discourage customers from pinning certificates as it exposes them to potential security risks and can cause downtimes for their services. Twilio customers using pinned certificates have a high probability of failed API Requests. These customers are advised to add the new certificates by March 3, 2025. 

Updates on the Cipher List

All our REST API endpoints will only support the cipher suites listed below. Support for any other cipher suite will be removed from that time.

Supported TLSv1.3 ciphers:

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

Supported ECDSA ciphers (TLSv1.2):

• ECDHE-ECDSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES128-SHA256
• ECDHE-ECDSA-AES256-GCM-SHA384
• ECDHE-ECDSA-CHACHA20-POLY1305
• ECDHE-ECDSA-AES256-SHA384

Supported RSA ciphers (TLSv1.2):

• ECDHE-RSA-AES128-GCM-SHA256
• ECDHE-RSA-AES128-SHA256
• ECDHE-RSA-AES256-GCM-SHA384
• ECDHE-RSA-CHACHA20-POLY1305
• ECDHE-RSA-AES256-SHA384

Customers are advised to check that their infrastructure supports at least one of these cipher suites. Customers running older operating systems or legacy network software may need to upgrade their systems to be compatible with these changes.

Test your configuration

The new security configuration will be available on the testing domain ( https://tls-test.twilio.com ) on February 3, 2025. 

For more information on how to test the updated cipher list, we advise you to read Monitoring Updates to Twilio REST API Security Settings. 

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.

Flex Insights (Historical Reporting) now offers Agent Copilot-related metrics that capture the customer sentiment and disposition code of a Conversation. If you have Agent Copilot and Flex Insights, you can visualize this data on the new Agent Copilot dashboard in Insights. For more information, see the documentation for Agent Copilot metrics.