Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
Serverless

Runtime Handler version 1.1.0 is now available

Runtime Handler version 1.1.0 leverages lazy-loading to improve the cold start time and latency of Functions that use the Twilio SDK. This version is backward compatible and is available on the Serverless API and the New UI Editor. This handler version is not compatible with Functions(Classic).

To use the new handler version, go to the Dependencies tab, update @twilio/runtime-handler to 1.1.0, and create a new deployment. This handler version requires the Twilio SDK version 3.50.0 or later.

Documentation for Runtime Handler and detailed instructions on how to use the Runtime Handler with the Serverless Toolkit can be found in our docs.


CSV Download for Super SIM in Console Beta

You can now download information about your Super SIMs from the Console in the form of a CSV file. This file will include information regarding each of your Super SIM’s ICCID, status, and Fleet configuration properties. You will be able to limit which SIMs are included in the CSV file by applying a filter (by Status, by Fleet, by Order) before initiating the download. 

You can find the download button on the upper right corner of the Super SIM list view.

Super SIM CSV Download


Twilio SendGrid Platform

New Twilio SendGrid Docs Site! GA

Access Twilio SendGrid documentation through a new, streamlined Twilio docs experience, offering enhanced discoverability and new features such as auto-generated code samples. Links will be redirected to the appropriate location in the new Twilio docs site.


Quick reply and call to action buttons can now be added to WhatsApp message templates when they are created in the Twilio Console. Buttons make it easy for businesses to streamline customer responses and guide their customers through conversational interactions, or drive them towards desired outcomes to improve engagement. Quick reply buttons let businesses define standard responses that users can tap to send. Call to action buttons trigger a phone call or direct users to a website when tapped.

To learn more about this exciting feature, check out our blog post or try it out for yourself today!


We have updated all Flex projects that use Automatic Updates to Flex UI 1.26.

This release of Flex UI and WebChat UI upgrades Browser Notifications and Markdown to Generally Available. These features improve agent efficiency and customer experience for messaging interactions.

Markdown support allows agents to format Web Chat messages. This can improve the readability of longer messages. Using bold text, italics, or bulleted lists can create structure and emphasis in your agents' messages, and ensure that customers read and understand the message correctly.

Browser notifications help agents respond to tasks that require their attention in a timely manner and not miss any customer interaction when they are not focused on Flex.

Visit the Flex settings to enable these features on your account.

Other notable changes in Flex UI 1.26: 

  • Error reporting - Flex now reports on errors that are generated within the UI. This will help us continuously improve the quality of the application and get more insights into issues that need troubleshooting. To read more about ways to troubleshoot Flex UI, including how you can opt out of error reporting, visit our Flex docs.
  • Transfer directory hidden filters - Now you can programmatically pre-filter the list of agents or queues in the transfer directory. Agents accessing the directory to initiate a call transfer will view and search only within the prefiltered subset. For example, you can choose to only display agents who are available. To learn more about Transfer directory hidden filters, visit our Flex docs.

For a full changelog, visit the release notes for our client libraries:

Flex UI 1.26

Flex Webchat 2.9

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.


On 8 July 2021 we will change the billing behavior for completed outbound calls.

Programmable Voice calls are charged based on the status of the call and its duration. For some Programmable Voice outbound call flows Twilio has not been billing for completed calls that had a duration of less than one second. In these cases, calls have been connecting and completing with sub-second durations and our systems has not had the precision to bill for these sub-second increments. 

Effective 8 July 2021 Twilio will be updating our systems to round the duration of any completed sub-second call up to 1 second and emit a billing event for those calls.


Twilio has completed validation of the integration between Flex and Spoke Phone. Spoke Phone is a Unified Communications (UC) / Private Branch Exchange (PBX) built on Twilio and fully integrated into Flex. Spoke provides features such as a directory list with presence for back-office workers, the ability to transfer calls between Spoke users and Flex users, as well as business continuity options for Flex users.


To learn more about Spoke Phone's capabilities and how to enable it for your application, visit our integration documentation.


Twilio SendGrid Platform

Retiring Email Previews for outdated devices Deprecated

In preparation for the arrival of iOS 15 and other email device testing options, we will be retiring some out-of-date devices. The following Apple devices will be retired and no longer available:

  • iPhone 11 iOS13
  • iPhone 11 Pro iOS 13
  • iPhone 11 Pro Max iOS 13
  • iPhone XR iOS13
  • iPhone XR Dark Mode iOS13
  • iPhone XS Max iOS13
  • iPhone 7 iOS12
  • iPhone 8 iOS12
  • iPhone 8 iOS13
  • iPhone 8 Plus iOS12
  • iPhone 8 Plus iOS13
  • iPhone 7 Plus iOS12
  • iPhone SE iOS12
  • iPhone X iOS12
  • iPhone XS iOS13

On 1 July 2021 Twilio will stop sending HTTP request parameters to <Play> files contained with a <Gather> using speech recognition.

For some call flows using <Gather> with speech recognition Twilio has been passing HTTP parameters when fetching <Play> files. This behavior was not deliberate and can cause issues with pre-signed URLs. An upcoming release will change this behavior and Twilio will no longer pass these parameters. 

If your application has been designed in a manner that the HTTP parameters passed in the request to <Play> files is driving your application logic, you will need to update your code by 1 July 2021.


Programmable Voice

Upcoming changes to <Dial> verb URL parameter behavior GA

On 1 July 2021 we will make a change to the list of TwiML verbs that are allowed to be returned in the url parameter of <Dial> nouns. 

The TwiML <Number>, <Client>, <Queue>, and <Sip> nouns allow developers to provide a url parameter that will execute when the called party answers. The url parameter is typically used as a call screening option to <Play> or <Say> notifications to callers about the incoming call, or <Gather> is used to retrieve input from the called party before bridging the calls.

We are making a change to prohibit the execution of any <Dial> verbs returned by the noun url instruction. Returning a <Dial> verb in the noun url can result in costly call loops that result in significant billed usage on the account.

We are unaware of any valid use cases for this behavior, but we are publishing this changelog in the spirit of no shenanigans.


Flex projects upgraded after June 1 will no longer include Autopilot usage as part of the Flex Fair Usage Policy, and Video usage will be covered as a "premium product" with limits outlined in our published policy. Existing, upgraded Flex projects will not be impacted by these changes.


On 1 July 2021 responses to API requests for CSV representation of an individual Call and Call List resources 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.


Twilio SendGrid Platform

Support for undo and redo functionality in the Design and Code Editors GA

You can now undo or redo recent changes made in the Design and Code Editors. To undo an action, use the undo arrow in the top navigation above the editor, or use the Ctrl or Cmd + Z keyboard shortcut. To redo an action, use the redo arrow in the top navigation above the editor, or use the Ctrl or Cmd + Shift + Z keyboard shortcut. You cannot undo/redo changes once you have left the browser session.


Twilio Super SIM® is available for download as an eSIM profile. Until now Super SIMs were available as physical SIMs in various form factors (2FF/3FF/4FF and MFF2). With the eSIM support, you can now reserve a SIM profile via a new API and then download the reserved SIM profile from Twilio’s SM-DP+ server to your eSIM/eUICC-enabled IoT device. Here is the typical call flow that you will use for downloading a Super SIM profile:

Typical call flow for downloading a Super SIM Profile

Twilio currently supports Consumer Profile eUICC SIMs. In order to download a Super SIM profile, your device must have a Consumer Profile eUICC SIM (in any form factor) and the Local Profiles Assistant (LPA) software on the device. Please see Consumer Profile eSIMs for IoT devices for more details on device requirements. 

If you are interested in trying out Super SIM profiles or reviewing our API documentation, please sign up for the pilot.


You can now manage a Phone Number’s Messaging Service assignment from the Phone Number’s configuration page in Console.

If a Messaging Service assignment is important to the success of your Phone Numbers’ messaging use-case (such as A2P messaging with US local 10-digit long codes) and if the Messaging Service is configured to defer SMS handling to the Phone Numbers' configuration: you can now assign a Messaging Service while also configuring the Phone Number to handle messaging with Flex, Studio, Functions or TwiML App.

You can determine whether the Messaging Service is handling or deferring message handling with the Phone Number from the Phone Numbers’ instance page in Console.

Console Twilio dual-msg-number config


Programmable Messaging

Messaging Services Defer to Sender's Webhook Option now available GA

A new option for handling inbound messages on your Messaging Services has been launched. In addition to the previous options, you can now defer to the webhook set on the phone number, allowing each phone number to have a diferent configuration for incoming messages while they are part of the same messaging service. 

This lets you utilize the benefits of a messaging service for outbound messages, but have inbound messages routed differently to fit the needs of your business.

You can find this new option in the Integrations section of your Messaging Service and is also available on the Messaging Services API as the property "use_inbound_webhook_on_number": true


New SMS Commands API to Replace Commands API Beta

To improve discoverability, a new SMS Commands API has been introduced for exchanging machine-to-machine SMS between your applications and your Super SIMs.  This new API replaces the existing Commands API.  The functionality offered by the SMS Commands and Commands APIs is almost identical with some minor changes to property names.

The Commands API will be removed before Super SIM is released to General Availability in the near future.  Please plan to migrate your integrations to use the new SMS Commands API as soon as possible.


Super SIM Connection Events on Event Stream Beta

Super SIM Connection Events allow you to follow a Super SIM connected device’s journey from when Twilio first sees it trying to connect to our mobile core, to when it gets connected and starts to use data, to when it ends its data session. Once a device has successfully started a data session, update events will be published while the device stays connected to give you near real-time usage information for each Super SIM.

Super SIM connection events

Super SIM Connection Events are delivered via Twilio Event Stream, an API that allows you to tap into a unified stream of interactions across different Twilio products. You can stream your data to your existing systems by configuring a modern, persistent streaming technology like Amazon Kinesis, or to a webhook.

Please refer to the documentation for more details and guides on how to get started. 


A major version release of @twilio-labs/plugin-serverless and twilio-run is now available. With this release, we are saying goodbye to .twilio-functions in exchange for two files that should hopefully serve you all better

This release contains breaking changes that you can read about in the announcement blog post.

On top of bug fixes, new features, and improved experience, we now have a brand new Twilio CLI Plugin: @twilio-labs/plugin-assets. An easy way to upload public assets from your command line:

twilio plugins:install @twilio-labs/plugin-assets

twilio assets:init

twilio assets:upload YOUR_FILE_NAME

Behind the scenes, we also moved the entire project to a monorepo which should enable us to ship new improvements faster in the future.

As a reminder: this is a Twilio Labs project meaning this isn’t a formal “GA” launch and users are encouraged to file issues on our GitHub.

The Serverless Toolkit is a collection of tools to improve the development of Twilio Functions and Assets. Read the blog to learn more about what features we added in the latest major version of the Serverless Toolkit and what things changed.


Programmable Voice

Voice Insights Gateway TLS 1.0/1.1 Shutdown GA

On 1 June 2021 the Twilio Voice Insights gateway (eventgw.twilio.com) will no longer support TLS 1.0 or 1.1 protocols. The Voice Insights gateway is where Voice SDKs publish events and metrics gathered by the sensors. The Voice Insights gateway will stop offering TLS 1.0 or 1.1 protocols on this date, only the TLS 1.2 protocol will be supported.


Show more