Twilio Changelog

Twilio <Pay> now enables PCI-Compliant contact center payment use cases with the launch of Agent Assisted <Pay>. Developers can build payment flows that allow agents to securely capture caller payment information during a voice conversation using the Agent Assisted <Pay> API. This launch extends Twilio’s existing support for IVR payments via our PCI DSS compliant Voice platform, <Pay> TwiML, and integrations with <Pay> connectors to Agent Assisted payments.

When leveraging the Agent Assisted <Pay> feature within their contact center (including Flex), agents control the payment flow and guide callers by requesting payment information one at a time (e.g., payment card number, expiration date, security code). Agents can continue to converse with callers but will not hear their DTMF, ensuring the security of the payment information. For additional details visit the Agent Assisted <Pay> blog post.

Get started with Agent Assisted <Pay> APIs. Learn more about PCI Compliance, <Pay>, capturing IVR payments, and PCI Recordings.

All new Functions and Assets UI is now available. The new Functions Editor brings together Functions, Assets, Logs and Settings in single intuitive design for an effective development experience. This UI utilises Functions and Assets API and delivers a seamless experience between UI and API. Previous version of Functions Editor continues to be available under Functions (Classic).

Check out the docs or try it out now in Twilio Console!

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 immediately increase your Trunk CPS settings per region (up to 15cps) in the Console, under the specific Trunk, under Termination settings.

Twilio Conversations (Chat and SMS channels), Programmable Chat, and Twilio Sync 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.

Android AudioSwitch is now Generally Available. This Android library reduces the complexity of adding support for audio routing and device selection in an Android app. You can now integrate AudioSwitch into your app with just a few lines of code. It handles audio routing and selecting built-in, wired, or Bluetooth headsets seamlessly.

Learn more about AudioSwitch in our blog post and check out our open source repository here.

All Messaging Insights reports now contain 120 days of data. This data becomes visible upon choosing 120 days in the Date-Time picker dropdown within Messaging Insights available via the Programmable Messaging console.

This is an enhancement from the 30 days of data that we launched into General Availability in June and was one of the top three requests from early customers.

You can now create new segments by copying an existing segment and making minor modifications. The ability to duplicate a segment means you no longer have to start from scratch when creating new segments. For more information about creating segments, see Segmenting your Contacts.

You can now create new segments based on two additional date criteria: when a contact was added to Marketing Campaigns and the last time a contact was updated. The criteria are listed as "Date Added" and "Last Updated" in Marketing Campaigns. For more information about segments, see Segmenting your Contacts.

Download a CSV of your stats to view offline or share with teammates. Learn about each available statistic in our documentation.

Flex’s Messaging Channel Janitor is now on by default for any new Flex messaging configurations (Flex Flows) created within the Twilio Console, as well as the default Flex Flows created for new Flex accounts.

Channel Janitor cleans up the chat channel and Proxy sessions for completed tasks, keeping them in sync with TaskRouter and making sure that when an existing customer contacts again, a new conversation is started.

Flex Flows are the configuration entities mapping phone numbers to Flex (one Flex Flow per phone number). Channel Janitor is enabled/disabled per Flex Flow. To enable Channel Janitor for existing Flex Flows, you can use the Flex Flow API or the Flex Messaging page in the Twilio Console.

You can learn more about the Channel Janitor and long-lived channels in Flex messaging documentation.