Twilio Changelog

When you send a verification attempt via SMS One-Time-Passcode, you can now view the SMS's Delivery Status & Error Codes in your Twilio Console. Navigate to Verify > Services > Logs as shown in the example screenshot below. This helps you to troubleshoot non-delivery of SMS.

Super SIMs can now be put into a new state called ready. Ready state lets your Super SIMs connect to cellular networks without incurring a monthly subscription fee until one of the following 3 conditions are met:

• The Super SIM has been in ready for 90 days
• The Super SIM has used 250 KB of data
• The Super SIM has sent or received 5 SMS Commands

Use ready state to enable and test your device’s connectivity, without incurring monthly fees, before it’s sent to your customer or deployed into the field.

Once any of those 3 conditions are met, the Super SIM’s status will automatically update to active, at which point, the monthly subscription fee will start being charged.

Super SIM Usage Records can now be filtered to show usage incurred on a single Super SIM, Fleet, Network (e.g. AT&T US, Telstra) or within a single country (e.g. United States, Australia). You can combine those filters with others to do complex filtering such as getting the usage for a single SIM on a single Network, or all SIMs within a Fleet.

You can also now group Usage Records around a resource type (e.g. Super SIMs, Fleets, Networks, or Countries) within the response data. For example, if you group your Usage Records by Super SIM, each record will contain the aggregated usage per Super SIM over the requested period. You can use this to efficiently pull usage for large fleets without having to make separate API calls for each resource. You can combine groupings with different filters to make complex requests like:

• How much data did each of my Super SIMs use within a particular Fleet yesterday?
• How much data did each of my Super SIMs use in France in the last 30 days?
• How much data did my Super SIMs use on each Network in Argentina last week?
• How much data did each of my Fleets use on AT&T in the United States in the last 3 days?

Cloud calling solution provided by Zoom Phones has support for “bring your own carrier” (BYOC) giving ZoomPhone customers access to a range of PSTN connectivity services to fit their business needs. You can leverage global SIP trunking services from third-party providers, including Twilio, and realize geographic coverage, pricing, flexibility and other advantages.

This release increases the security of the Zoom Phones BYOC to Twilio Elastic SIP Trunking Interconnection to use Secure Real-time Protocol (SRTP) to encrypt media and Transport Layer Security (TLS) to encrypt signaling.

If you're configuring your Elastic SIP Trunk to interconnect to Zoom Phones BYOC, please ensure you enable Secure Trunking. To learn more about how to configure your Elastic SIP Trunk please see here.

Flex-Salesforce integration v1.3.1 and Flex-Zendesk integration v1.2.0 introduce the use of Flex Native Outbound Dialing for its click-to-dial feature. Check our migration guides for Salesforce and Zendesk integrations to see how you can upgrade your integration.

Twilio SendGrid now offers the ability to segment contacts based on their engagement with your automated emails. For more information, visit our Knowledge Center.

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

This release of Flex UI introduces new filter options for the Teams View. With Hidden Filters, your developers can control which users each supervisor is able to view and manage. This is useful if you want a supervisor to only manage their team, instead of being able to view all agents by default.

Other notable changes:

• Flex UI API Reference now includes the list of component children for dynamic components (with information such as key, condition, type, alignment and description)

For a full Flex UI 1.21 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.

Starting October 14, Deleting a Message log will also automatically remove any Media objects associated with that message. This allows a more intuitive experience when customers issue delete requests on messages containing media. The change will apply to all messaging channels supporting media including MMS, WhatsApp and Facebook Messenger.

More details of the changes to coming message records and media availability are published here.

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!