Skip to main content

Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
Programmable Voice

Upcoming changes to withheld caller ID behavior for <Dial> calls GA

Twilio is changing how we persist caller ID information for <Dial> calls where the inbound caller ID is withheld; e.g. ANONYMOUS, RESTRICTED, etc. Today Programmable Voice translates the alpha string into digits. This behavior will change and we will begin to persist the alpha string from the inbound call to the outbound <Dial> leg for calls where the caller ID is withheld by the calling party.

This represents a significant change in the behavior of our APIs and developers will need to ensure that their systems can gracefully handle alpha characters in the To and From fields for requests and responses to the /Calls API, in TwiML,webhooks, and in status callbacks.

If the callerId parameter is used with the <Dial> verb, the outbound caller ID will reflect what was provided with callerId, regardless of the caller ID on the inbound call.

Twilio SendGrid Platform

Twilio SendGrid is Updating our Mailbox Provider Stats Features GA

Twilio SendGrid has always grouped your email statistics by mailbox provider in our console. This allows you to easily see how your email is performing at Yahoo compared to Microsoft, for example. Our system also helps clean up this data by grouping mailbox providers together. On November 16, 2022, Twilio SendGrid will release an update to our current Mailbox Provider groupings that will make this part of our application even more powerful. Specifically, we will be adding more mailbox providers to our list, increasing from 50 to almost 250. This will result in far less data being lumped into the “Other” bucket when you review your mailbox provider statistics.  Check out our blog post to learn more about the change and see examples for more information.

We are launching a new attribute `requireMatchingInputs` within <Prompt> verb which is used in conjunction with the `for` attribute to prompt the caller to enter a specific payment detail twice. The first <Prompt> verb prompts the user to enter a given payment information. 

The second <Prompt> which contains `requireMatchingInputs` set to `true` will give the caller a different prompt asking the caller to enter the information again. Once the customer enters the information, both inputs are validated against each other and if they match, they will be sent to the downstream payment gateway for processing. 

This attribute works for ACH-debit <pay> transactions of type purchase/tokenization that require users to enter a bank account number or routing number. This enhancement was introduced to catch any user input errors upfront, reducing the error rates reported by payment gateways to meet the error thresholds defined by NACHA.

For more information about this feature, check out the API Docs.

CSV Download for Super SIM Usage Insights in Console Beta

Super SIM Usage Insights now lets you export a CSV file containing your SIMs’ usage record data. With just the click on a button, you can download an extract of the table currently being displayed in the browser. Having this data in the form of a CSV allows you the flexibility to perform subsequent analysis using any application of your choice – a database, spreadsheet, or data visualization tool.

All of the Usage Insights tabs support the CSV Download feature:

  • Usage by Time
  • Usage by SIM
  • Usage by Fleet
  • Usage by Country
  • Usage by Network

Access CSV Download for Super SIM Usage Insights in Console by navigating to Monitor > Insights > Super SIM and clicking on the button labeled “Export CSV”.



Conversations API Chat channel now available in Ireland GA

We are excited to announce that the Conversations API is now generally available in Ireland (chat only). The availability of Conversations API in Ireland gives you control over where you data is processed and stored. It also offers data processing that is closer to your applications, therefore reducing latency and improving performance.

Click here to learn more on how to get started with Conversations API in Ireland.


Twilio Microvisor now in Public Beta Beta

Twilio Microvisor is now in Public Beta. Microvisor provides managed connectivity as well as managed security for the lifetime of IoT devices. With Microvisor, you can continuously debug and improve a connected hardware product after it has been mass-manufactured and deployed to the field – by offering unbrickable over-the-air firmware updates and secure remote line-by-line debugging live on deployed devices. Microvisor leverages Arm TrustZone to achieve security and failsafe connectivity through hardware-level separation of communications and application and a hypervisor architecture.


The Public Beta release includes:

For a peek into how Microvisor works in action, watch this video. For more background on the Microvisor architecture and feature set, read our blog post. For pricing, please review this page.

The Virtual Agent for Google DialogFlow CX is now available in public beta. This connector supports integration with Google’s DialogFlow CX edition benefiting from its advanced functionalities such as detecting the welcome intent, barge-in, DTMF, support for multiple languages, custom voice models, status callbacks that contain sentiment scores, intents triggered, call status, etc. 

After this release, we have 2 connectors available for customers based on their needs - Virtual Agent connector for Google DialogFlow ES and Virtual Agent connector for Google DialogFlow CX/CCAI connector.

In order to access Google DialogFlow CX capabilities, create a new Dialogflow CX agent in your Google Cloud Platform (GCP) project, and grant Twilio service account permissions to execute the virtual agent through Google’s one-click integration feature which allows for easier onboarding of Dialogflow CX Connector containing agent details. You can then connect your Twilio phone number to the Studio widget or TwiML to invoke the Dialogflow CX Virtual Agent.

More information available here.

Learn more about this feature in our API docs.

When requesting a Super SIM eSIM Profile from the /ESimProfile API, you can now request that the eSIM profile be reserved with a matching ID by setting the new generate_matching_id request parameter to true. When you reserve a profile this way, you don’t need to provide the EID of the eSIM that will use the profile, which depending on your use case may be very difficult to know ahead of time or obtain. 

When you want to download and install the eSIM profile, you will need to provide the matching ID to your device along with the SM-DP+ URL, both of which can be read from the ESimProfile when your reserved profile is available. The combined SM-DP+ URL and matching ID is often referred to as an “activation code” and often provided to end users via a QR code that they scan with their device during the workflow to add a new eSIM profile. 

Refer to the docs to learn more about eSIM Profiles and different eSIM download methods.

Current Data Limit Usage for Super SIM in Console GA

If a SIM exceeds its data limit, it won’t be able to use any more data until the data limit resets at the end of its current billing period. Today, the Super SIM details page in Console now allows you to easily identify how close a particular SIM is to reaching its monthly data limit. There is a new section on the page which shows:

Use the data limit usage information to determine whether you need to take action such as:

  • Move some SIMs to another Fleet with a higher data limit
  • Update the data limit on the Fleet your SIMs are assigned to


Access the Super SIM details page in Console via Develop > Super SIM > SIMs and selecting one of the SIMs on the list page. Alternatively, you can also check how close a SIM is to hitting its data limit via the API by following these steps in the docs.

Programmable Voice

New Audit Events for Voice Recordings and Transcriptions GA

The following new Monitor Events have been created for Voice Recording and Transcriptions: recording.created, recording.updated, transcription.created and recording.bulk-delete.created to track bulk deletions from Twilio Console.  In addition, we have updated the recording.deleted event to track pci-recording automatic deletion after 72h. The transcription.deleted event has also been updated to track deletion from the transcription detail page in the Twilio Console. These new and updated events are available in the Twilio Console and in the Audit Event/Monitor Event API. Monitor Events are a Twilio platform feature that provides comprehensive event-logging and change-tracking for Twilio resources. 

With this release, developers can improve audit of their voice applications and have granular visibility on recordings and transcriptions to contribute to their security and compliance requirements. 

See full list of all supported resource-types and event-types for additional informatio

This solution enables organizations using Avaya Aura Contact Center solutions that include the Avaya Enterprise Session Border Controller (ESBC) to connect to the PSTN via Twilio Elastic SIP Trunking. You can learn more about this solution by referencing the blueprint guide here: Twilio Elastic SIP Trunking Solution Blueprints.

Programmable Messaging

Alerts for Rejected and Paused WhatsApp Templates now available GA

Twilio now supports new error codes for "Rejected" and "Paused" WhatsApp Templates. With Twilio Alarms, you can now get notified via webhook or email when these and other errors occur.

When a WhatsApp template gets rejected, Twilio surfaces a new error code of 63040 and will include the reason from WhatsApp. 

Likewise, if a WhatsApp template is paused due to quality concerns from WhatsApp, Twilio will surface an error code of 63041. The message also contains when it will be unpaused. A template can be paused by WhatsApp when different users report messages sent using that template, or when users block the number after receiving those messages.

Verizon on Super SIM Beta

You can now allow your Super SIM connected devices to connect to Verizon. You can now connect to all 3 major US carriers – AT&T, T-Mobile, and Verizon. You can enable Verizon by adding it to the list of Networks allowed by your Network Access Profiles in Console or via the API. Check out our blog to learn more.

Add Verizon in Network Access Profile

Verizon is the first Super SIM supported network to have a Network Access Fee. Each SIM that connects to Verizon will be charged an additional monthly fee. To learn more about how Network Access Fees are charged, refer to the docs.

Marketing Campaigns

Marketing Campaigns Now a Segment Destination GA

The Marketing Campaigns team is excited to announce that we now have a Segment Action Destination! 

What is Marketing Campaigns: Action Destinations

  • Create an Action Destination for Sendgrid Marketing Campaigns in Segment’s Catalog. 
  • This destination will allow marketers to add and update contacts so that marketers can leverage the power of a CDP and the ease of Marketing Campaigns to create compelling and targeted campaigns.

Get started with our docs

In this version of Flex UI we have updated the Status Report, formerly known as the Debugger UI, to now include a summary of Flex UI's operation status for each user. The Status Report is now available in GA and includes debugger logs, Twilio service status information and whether Flex UI is running in degraded mode.

Find out more about the updated Status Report on the Troubleshooting Flex UI page.

This release also improves Flex UI’s resiliency by updating core functionality used in conferences, outbound calling and voice transfers to remove Sync as a dependency.


Mark a conversation unread in Frontline GA

You can now mark a previously read conversation as unread within Frontline on mobile (version 1.7.0 and above) and on web. On mobile, swipe left on a conversation to toggle the read/unread status. On mobile and web, within a conversation, access the manage conversation menu by clicking the three-dot icon in the top right to mark your conversation unread.

Frontline-Changelog-Mark Unread

Programmable Messaging

Notify API End of Life Notice Deprecated

Effective today (October 24, 2022), Twilio is ending the sale of Notify. New customers will be unable to use the product. 

We intend to end of life (deprecate) the Notify product on October 23, 2023. Existing customers will be supported up until this date, however, no new feature enhancements or rate limit increase requests will be granted. 

Other Twilio products that support push notification use cases such as Verify or Conversations are not impacted by this. 

We are sincerely sorry for any disruption this may cause and have prepared this Migration Guide to assist with the transition.


Verify Fraud Guard is now Generally Available GA

Verify’s Fraud Guard helps you combat fraud and improve your SMS OTP conversion rate at no additional cost. 

Enable it on your console today and read our documentation to learn more about it. Check out our blog to see how this has helped our customers already!

We are excited to announce that Twilio CLI is now Generally Available! Twilio CLI is a developer tool to help you build, test, deploy and manage twilio resources directly from the terminal.

Head over to our docs to get started .


Functions and Assets are now Generally Available GA

Today Functions and Assets as well as the Serverless API are moving into General Availability, meaning they are now covered under our guaranteed Service Level Agreement (SLA)  including a service level quality of 99.95% when building and invoking your Functions and Assets. It also means that in the rare eventuality you encounter a problem, you can raise a support ticket backed by the service agreement. Check out our announcement for more details.

Important: Functions (Classic) and Assets (Classic) are not covered by this SLA. If you are still using Classic, you are encouraged to start the transition over to Functions & Assets to take advantage of the SLA, a more powerful editor, and access to the Serverless API.

Additionally, the Serverless Toolkit will remain a Twilio Labs project for the time being. It's still backed by the same Serverless API but if you are encountering any issues, we cannot guarantee any SLA yet to resolve issues. Instead, please raise an issue on the project's GitHub.

Show more