Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
Programmable Voice

Voice Insights Tagging Changes for SDK calls GA

Voice Insights has updated the jitter and packet loss thresholds for Voice SDK calls to reduce the number of false positives and improve the diagnostic capability of Voice Insights data. 

Previously tags were applied to Voice SDK calls in response to network and audio warning events fired by the SDK. We have updated the tagging scheme for these calls to use the same thresholds as our gateway metrics for jitter and packet loss, and to use the cumulative metrics for the entire call instead of samples.

As a result of these changes consumers of the Voice Insights Call Summary API should expect to see a significant reduction in the number of calls tagged with SDK edge tags.

Note: the SDK events will continue to fire at the previously defined thresholds, and the events will continue to be sent to Voice Insights Event stream. This allows application developers to continue to provide the same level of proactive notification and prescriptive instruction in their applications to ensure optimal call quality.


Programmable Voice

Voice Insights Events and Metrics API Beta

Voice Insights Events and Metrics are now available via API allowing near-real time access to call quality data for all call types. 

Voice Insights Events include call progress events like ringing and completed for carrier and SIP calls, and quality events like network quality warnings and audio level alerts for Voice SDK calls. 

Voice Insights Metrics provide a time series view of key performance indicators like jitter and packet loss to help identify the precise timing and severity of quality issues on calls. 

Voice Insights Events and Metrics API access is included as part of Voice Insights Advanced Features which can be enabled in Voice Insights Settings.


SendGrid Email API

Pro Plan Price and Feature Updates GA

The Twilio SendGrid Pro, Silver, Gold, Platinum and Legacy Premier 2.5M plans have changed. These changes include a new price and new features. To see updated pricing visit our pricing page.

Some plans also have new names. Silver, Gold, and Platinum plans are now Pro 100K, Pro 300K, and Pro 700K respectively.

We’ve also extended Email Activity history from 3 to 7 days included with all Pro plans, and launched Email Testing for Dynamic Templates. We are committed to continued investment in our infrastructure and innovation to provide the best-in-class features you need to build exceptional experiences with email. You can review past invoices and update your Plan and Billing Details in the SendGrid application. If you have any questions please reach out to our knowledgeable support team.


Programmable Video

Video Javascript SDK 2.0 GA GA

Twilio Video Javascript SDK 2.0 is now GA! Thank you to all our beta users and for all the feedback you sent us during the beta period.

Twilio Video Javascript SDK 2.0 introduces the Track Priority API, Network Bandwidth Profile API, Reconnection States and Events, and the Region Selection API.

Track Priority and Network Bandwidth Profile API gives developers the ability to specify how bandwidth should be allocated between video tracks. Furthermore, the three profiles, (“grid”, “collaboration”, and “presentation”), specify when tracks should be switched off (or not) to conserve bandwidth for the highest priority tracks.

The Reconnection States and Events will automatically attempt to reconnect when a transient network error is encountered.

With Region Selection API, the SDK will automatically connect to the lowest latency data center. This API can also be configured to connect to a specific data center for cases where compliance might be required.

If migrating from a 1.x version, please refer to our migration guide.

To get started with Twilio Video JS, check our Getting Started Guide


The path of the executing Function is now available in the context object at runtime, allowing you to reconstruct the full Function URL for use in your application.

Example:

exports.handler = function(context, event, callback) {
    callback(null, 'https://' + context.DOMAIN_NAME + context.PATH);
};

Full structure available from the context:

{
  "PATH":"/contextpath",
  "ENVIRONMENT_VARIABLE":"ENVIRONMENT_VALUE",
  "ACCOUNT_SID":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "DOMAIN_NAME":"funny-name-1234.twil.io"
}

The context path is available in both Console-created Functions and those created via the API.

For more information about Twilio Functions, check the Runtime documentation.


API Keys now supported for Media upload Beta

The most common way to access Twilio REST API is by using your primary Account SID and token. However, you may want to implement a separate access policy for different developers or subparts of your application by utilizing API Keys instead. This allows you to revoke access easily and at the right granularity.

Now, you are able to use the very same API Keys method for authenticating with Media Content Service (mcs.us1.twilio.com) to upload any attachments you would like to be sent over Programmable Chat.

Read more about API Keys support in the documentation.


Twilio SendGrid Platform

Designs API GA

We’ve added a brand new Designs API, allowing you to easily create, edit, download, or delete Email Designs without relying on the SendGrid app UI. You can use the Designs you’ve created across all of your Twilio SendGrid Email—from Automations, to Single Sends, and Dynamic Templates. For more about working with the API, see our API Reference.


Twilio SendGrid Platform

Email Content Testing for Dynamic Templates GA

Test your email content against spam filters, validate hyperlinks, and preview HTML rendering across browsers and devices with Email Testing for Dynamic Templates. Monthly testing credits included for Trial, Pro and Premier plans, with additional credits available for purchase. See our Email Testing documentation for more details.

We've made some improvements to Transactional Templates. We've renamed them to Dynamic Templates since they can be used to build the content for any type of email message sent over our Email API. They can be found in the app’s sidebar navigation under both the new “Email API” navigation item or the “Templates” navigation item. We've also eased ongoing template management by adding thumbnail images and allowing duplication of entire templates as well as the individual versions within a template.

For more, see our blog post about working with Dynamic Templates.


Autopilot

Collect Confirm GA

Collect's Confirm feature simplifies programming your bot to confirm the answers it receives from the user during a question answer sequence. Confirm can be enabled separately on each question using the confirm attribute. Learn more about using Collect Confirm in the docs.


Autopilot

Inbound Context

Inbound Context lets you add data to the Autopilot Memory before starting a dialogue with the bot. It can help you make the bot experience more personalized and contextual by making information like names, purchase histories, account numbers etc. stored in third-party systems available directly in the bot conversation.

Inbound Context is available on all channels supported by Autopilot:


Programmable Voice

G.711 A-Law (PCMA) Support for SIP Interfaces GA

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our SIP Interfaces documentation for more information


Elastic SIP Trunking

G.711 A-Law (PCMA) Support for SIP Trunking GA

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our Elastic SIP Trunking documentation for more information.


This release of Flex UI introduces Chat and Messaging Transcripts for Flex Insights. Supervisors can now open a historical chat or messaging conversation from Flex Insights and see its content. While viewing the content, it is also possible to comment and assess these conversations.

Other notable changes:

  • New Actions to programmatically send DTMF tones when there is an active voice connection.
  • Flex Insights screens are accessible from top-level Flex navigation.
  • Flex Insights Player opens directly within the dashboard instead of opening in a separate window. This significantly improves the speed with which you can scan through multiple calls or chats.
  • You can now attach references to 3rd-party web content related to conversations – such as CRM records – and open these directly in Flex Insights.

For a full changelog, visit the Flex UI release notes.


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

This Flex UI release introduces minor fixes for chat interaction, a new Action for updating agent activity, and UI performance improvements.

For a full changelog, visit the Flex UI release notes.

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


Interconnect

New Twilio Interconnect Exchange - Tokyo, Japan GA

Twilio Interconnect has been expanded with a new Interconnect Exchange Installation in Tokyo, Japan.

The new exchange provides customers with connectivity via cross connect, VPN, Bring-Your-Own-MPLS, and the Equinix Cloud Exchange with initial product support for Elastic SIP Trunking, SIP Interface and Voice WebRTC.

Twilio now has two Interconnect Exchanges in the APAC region, one in Singapore and one in Tokyo. This allows APAC customers to set up redundant interconnects from their networks to Twilio adding an additional layer or resiliency while benefiting from the security and consistency of a dedicated interconnect.

Click here for information about Twilio Interconnect and here for documentation.


Phone Numbers

Regulatory Compliance v2 moves to Public Beta Beta

The new v2 Regulatory Compliance suite, backed by programmatic public APIs and a Console workflow leveraging the intelligence of the Regulatory Rules Engine.

For additional details:

Regulatory Compliance APIs

Getting Started: using the Public API to create new Bundles

Console: Regulatory Compliance Report Getting Started

Getting Started: How to use the Compliance Report


Selective Push muting for messages and user events GA

Push notifications are critical for reaching your end users. But not every message or user event deserves a push.

Starting today, you can intercept any event using Chat’s Pre-Webhooks and choose to suppress the push by returning "mute_notification": "true". Now, system messages or user joined / left events don’t have to show up on the lock screen.

More flexibility and control over how you interact with your customers! Read more in the Chat Webhook documentation


In new TaskRouter projects and Flex projects, TaskRouter workspaces are now always multitasking and TaskRouter no longer supports switching the workspace from multitasking to single-tasking.

Existing projects with single-tasking workspaces are excluded from this change.

To learn more about multi-tasking in TaskRouter, refer to our documentation on multitasking.


User-level two-factor authentication setting

Previously, 2FA was implemented at the account-level for the console. This caused owners or admins to inadvertently turn on 2FA for every user with access to their account. 

With this change, users can add an extra layer of protection to secure themselves without enforcing 2FA on all other users on an account. You can view the new setting under User Settings in console. When enabled, this setting will take precedence at login. 

Owners and admins can still add 2FA as a security requirement for an account through General Settings. When both settings are enabled, we will give precedence to the stronger of the two settings. Moreover, users will never have to do 2FA more than once per login session. For more information, read our 2FA help article.


Previously, when a TaskQueue had been configured for multi-reservation of workers, TaskRouter would try to establish an audio connection for every worker that accepted the reservation request, before rescinding all but one reservation. In rare circumstances, that could lead to more than one worker being placed into conference with the customer.

Now, TaskRouter will only establish the audio connection for the first worker accepting the reservation, while all other worker reservations are immediately rescinded.

To learn more about multi-reservation in TaskRouter, refer to our documentation on multi-reservation in TaskQueues.


Show more