Twilio Changelog

In this release of Flex UI, we have introduced a Degraded mode for Flex UI - now Flex UI will initialize with limited capabilities, even if some of the components like SDK’s (TaskRouter, Conversations, Voice or Sync) are down. In case of disruptions in Twilio services, Flex User will be able to login to Flex and perform certain tasks that are still available. For example, in the case of Twilio Voice experiencing an incident, your agent will still be able to handle messaging tasks.

Users will see a notification informing them of a possible disruption in the normal operation of Flex UI and they will be able to download a thorough report with error details and logs.

For more on error handling and reporting, check out our Troubleshooting Flex UI guide.

Bounce Classifications are now included in the Twilio SendGrid Event Webhook. The event webhook is a powerful way for you to consume event level data to gather more insight to your email performance. Twilio SendGrid's Event Webhook will allow you to use a data aggregator of your choice and notify a URL via HTTP POST with information about events that occur as Twilio SendGrid processes your email. The addition of Bounce Classifications to the Bounce and Deferral event payloads will provide additional insight as to why an email was bounced, blocked, or deferred.

Twilio SendGrid started limiting category statistics for new customers only on March 16, 2022. Beginning May 16, 2022, Twilio SendGrid will limit category statistics for all customers on a seven-day rolling basis. This means all categories will be available for the first seven days. After seven days, the top 100 categories will be retained for free customers, and the top 1,000 will be retained for paying customers.

Customers who require access to all category statistics can use the Event Webhook to retrieve and retain the data on their own systems as long as they save it within seven days of first sending the event.

Twilio SendGrid accounts created before March 16, 2022 will temporarily retain access to all category statistics created before May 16, 2022. However, access to unlimited category data is transitory and should not be expected to persist.

For more information about how this change works, please see the "Limitations" section of our "Working with Categories" documentation.

Many customers find that Unique Arguments, which are not limited, are the best solution for their needs. See the "Categories vs Unique Arguments: Benefits & Limitations" blog post to better understand these two tracking tools.

The Marchex Transcription with Conversation Intent and Outcome is now available in Twilio’s Marketplace Add-ons catalog. This Marketplace Add-on identifies the most important attributes of your phone calls such as the primary intent of the caller and outcome of the conversation, using Marchex’s AI powered conversation intelligence capabilities. To learn more about this Add-on and how to enable it for your application, visit the Marketplace Marchex Add-on in the Twilo Console.

External storage for call recordings is now available for all voice customers. Call recordings will remain to be stored at Twilio by default. Alternatively, customers can enable external storage and automatically upload recording files directly to an AWS S3 bucket without additional charges.

To determine whether the recording’s media file is stored externally or at Twilio, a new property mediaUrl has been added to the call recording resource with the full URL location of the file; this will apply also to existing RecordingUrl property from the RecordingStatusCallback. When external storage is enabled, recording files from two-party calls get uploaded as dual-channel regardless if they are requested to be mono or dual-channel. Recording resource metadata is available at Twilio until explicit deletion.

Prior to this release, recording status callbacks could be used for automating recording file download and deletion but required additional software development and additional API requests by customers to set up this workflow.

Learn more.

You can now manage the configurations related to a unique address (i.e. a WhatsApp or SMS phone number) within Conversations. This resource allows you to specify which addresses should auto-create a Conversation upon receiving an inbound message.

With this feature, you can also automatically attach a Conversation-scoped Webhook to the auto-created conversation.

Explore the Address Configuration API documentation and give it a try!

You can now see how much you were charged for data usage on Super SIM when using Super SIM’s /UsageRecords API by using the new data_total_billed property. Previously, you could only view how many bytes you had used. Now, you can view your usage in bytes and the amount you were charged for it side by side. Use this combined information to build your own usage and spending reports by filtering and grouping your usage across the different dimensions using the /UsageRecords API.

Values for data_total_billed are available for usage occurring on or after February 1, 2022.

For more information, check out the docs.

On May 3rd, 2022 responses to API requests for CSV representation of Incoming Phone Number and Outgoing Caller ID resources for both list and instance will change; specifically the order of the columns may be different.

The order of the columns in the CSV is not defined and may change when new fields are added to the API response. Your application design should be resilient to changes in the order of the columns in the CSV response.

See our docs for more information about how to leverage CSVs with Twilio.

When Twilio receives termination traffic from your communications infrastructure to the PSTN, your SIP message can sometimes include SIP Diversion headers if the call was previously forwarded. Twilio will forward SIP Diversion headers it receives to the carriers.

To combat any malicious addition of Diversion headers, Twilio will now check all Diversion headers it receives that contain the Twilio domain. Twilio will verify that the phone number included in the header matches one associated with your Twilio account (either a Twilio number owned by the account or a verified Caller ID). If the header fails this check, Twilio will remove the header.

See the docs for more information.

As previously communicated, we are continuing to roll out Enhanced Programmable SIP Features to all accounts. This could represent a behavior change for some call flows, including calls that do not use Programmable SIP. For more information, see our docs page detailing the changes in Programmable Voice behavior.