Twilio Changelog

In TaskRouter, timestamps for TaskQueueEnteredDate will now provide millisecond precision. Although TaskQueueEnteredDate was already in the ISO8601 format yyyy-mm-ddThh:mm:ss.mmm, milliseconds were previously rounded to 000 in the event data.

To learn more about the TaskRouter Events resource, please refer to our documentation.

Voice Insights API responses have been updated to include edge location naming for Twilio's media and signaling edge.

Responses from the /Summary endpoint will include edge_location as part of the properties object; e.g. {carrier|client|sip}_edge.properties.edge_location. For Voice SDK calls it has also been added to {to.callee|from.caller}.sdk.edge_location.

Responses from the /Events and /Metrics endpoints will include edge_location as part of the edge metadata; e.g. {carrier|client|sip}_edge.metadata.edge_location. For Voice SDK Events it has also been added to sdk_edge.metadata.sdk.edge_location.

This information augments the deprecated region naming convention. For more information, see our docs.

Now you can easily search large Flows and jump to a specific widget in Studio. No more dragging and panning the canvas to find a widget!

To launch the search bar, click the magnifying glass or use the keyboard shortcut CMD + k for Mac and CTRL + k for Windows.

Type a partial name and select the widget from the search results to jump instantly to that widget.

Try it now in Studio!

Trunking Termination Calls per Second (CPS) refers to how many new SIP Trunking call setups are allowed in one second for Trunking Termination calls (outgoing traffic from your communications infrastructure to the PSTN). Twilio, by default, provides the ability for you to place 1 CPS per Trunk per Region (see limits).

With this release you are now able to set the Trunk CPS between 1 and 15 per region. This release will show the pricing changes as well. In addition, it is possible to schedule the effective date in advance when decreasing your Trunk CPS.

For details, please check our Trunk CPS documentation.

Verify’s push-based verification (authentication) channel has advanced from the Private Beta to the Public Beta release stage. With this release, the Push API and SDKs are now publicly available and ready to support production-scale workloads. Learn more about how Verify Push allows you to add a secure, cost-effective, and low-friction user verification feature into your Android or iOS mobile app, without requiring a phone number or email from your users.

Voice Insights Dashboard now allows users to filter based on whether Twilio detected silence on one of the streams in a call. This can be useful in diagnosing reports of dropped calls and one-way audio.

Twilio's media gateways can detect missing RTP streams or streams which contain only silence, and we will tag those calls as having contained silence in the Call Summary. Note that depending on your use case silent calls may be expected. For example, users receiving a one-time password frequently don't verbally respond, which Twilio may (appropriately) detect as silence.


For additional information, see our docs.

Twilio Verify and Lookup can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

As your messaging volumes grow, you can now monitor the latency introduced in sending messages using the Latency Report in Messaging Insights. This can be particularly helpful in high-traffic times like promotions for Black-Friday, or emergency notification situations. The Latency Report is available to all Messaging Customers at no cost via the Messaging Insights console.

As part of the effort to increase transparency on Messaging Latency, there is now a new guide for scaling and two new filters available as part of Insights - latency buckets and time-ranges of 5-minutes and 4 hours. The blog with this announcement is available here.

Twilio Elastic SIP Trunking now allows you to record two distinct channels, one per party in the conversation. Visualize and focus on one party at a time while you analyze customer conversations and evaluate agent performance. These will be saved to the same Recordings Log as your other recordings. You can enable this feature on each of your individual trunks.

For more details, visit our Elastic SIP Trunking documentation guide.

Voice Insights call summaries now include the Application Name and Application Version provided by your app starting in Twilio Client JS SDK 1.11.0, Voice iOS SDK 5.1.1, and Android SDK 5.0.2. This information can be used to correlate Insights events with the application that is generating them which is useful for debugging purposes in cases where multiple versions are deployed, or when performing A/B testing.

See the Voice Insights Call Summary API docs for more information.