Twilio Changelog

Twilio Monitor API, our API for programmatically accessing errors and warnings from the Twilio Debugger, now supports alerts from 7 more products. This makes it easier to gain more insights into how your Twilio applications are performing and how to resolve issues quickly. The additional Twilio products that now have alerts published to Monitor API include Autopilot, Fax, Flex, Functions, Programmable Video, Proxy, and Studio. These additional errors and warnings appear automatically in the Console Debugger, Monitor API, Debugger webhooks, and Alert Triggers.

The new version of Marketing Campaigns now features a Design Library, a new, top-level navigation item in the navigation on the left that houses all Email Designs for use within Marketing Campaigns. “Templates” remains as an option under the Marketing [New] navigation, and, if clicked, it will bring customers to the Design Library.

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

This Flex UI release introduces new notifications for call transfer failures, minor fixes to how we handle custom chat tasks, 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.

The new version of Marketing Campaigns now supports IP Pool Selection for users who have created IP Pools. This allows senders to choose which IP Pool to send a Single Send or Automation from, providing improved control over reputation and deliverability.

You can now configure Flex Flows message handling within the Twilio Console with two new behaviors:

• Direct to TaskRouter
• External Webhook

You can use these behaviors to setup outbound messaging use cases or to handle your messages outside of Studio. Learn more about managing your messaging configuration in our Flex Messaging Developer Guides.

Strong Customer Authentication (SCA), a new rule that came into effect on September 14, 2019, as part of PSD2 regulation in Europe, requires changes to how European businesses authenticate online payments. You can read more here: https://stripe.com/docs/strong-customer-authentication

As a result of this directive, we have made a change to tag all payments captured using <Pay> with Stripe or CardConnect connector as MOTO (Mail Order/Telephone Order) payments, MOTO payments are exempt from PSD2 regulation. This change does not affect how Twilio <Pay> is used or the responses it generates upon successful payment. Moreover, this change does not apply when Twilio <Pay> is used to tokenize payment card information.

The new version of Marketing Campaigns now supports sending a test email to as many as ten email addresses. A test email can be sent for a Single Send, an email within an Automation, or an email design, and allows users to preview email content prior to sending or request review from partners outside of the UI.

This release includes the following:

• Two new screenpop methods: Pass either specific SFDC URLs or SFDC Object Ids as custom task attributes to dictate the ScreenPop behaviour in your Engagement flows.
• Configurable interaction logging: You can now choose to configure your automated interaction logging - select which interactions ( task start, task complete, task switch) to log, or turn them all off completely.
• Phone Number and Taskrouter SIDs validation: Configuration screens for Flex Salesforce Integration in the Flex Admin panel now have validations for Phone Number, Workflow SID and Task Channel SID, so you'll see a warning if you make a configuration error.

Read more on Screenpop, Interaction Logging, or the full release notes here.

Do you remember a time, when you called customer service for assistance. You reached Agent A from department 1 who collects your call related information like name, account number, phone number, and so on. Then realizes that they have to transfer the call to agent B in department 2. Now agent B asks you to provide the same information before they could help. This experience is painful and without having the context of the call it takes longer than expected to solve the issues. With User-to-User Information (UUI) header, you as a customer will only need to provide the information once! With this new feature, agents will be able to send and receive contextual information of the call over SIP-Interface using UUI header.

UUI header can be used in other SIP call scenarios such as

• Regular call between UserA and UserB.
• When the call is redirected or forwarded.
• When the call is transferred from one agent to another.

For details please refer to our Sending-sip, Receiving-sip, Custom headers, Support page

Apple iOS 13 includes “Sign in with Apple” Oauth feature which provides an optional private relay email for users and sender authentication requirements for Apple app developers. In order to send email to Apple Oauth private relay email addresses (@privaterelay.appleid.com), you will need to update your Domain Authentication settings within your SendGrid account. Failure to properly complete and register your SendGrid Domain Authentication with Apple will result in email sent to “privaterelay.appleid.com” returning a bounce event with the reason “550 5.1.1 bad mailbox name.” Visit this blog post for step-by-step instructions.