Twilio Changelog

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.

We have increased the timeout for Twilio Functions from 5 seconds to 10 seconds. This allows more processing time for complex use cases. In order to have this change take affect on an existing Function, it must be redeployed. This change affects Functions deployed via the UI or API. For more information about Twilio Functions, check the Runtime documentation.

Voice iOS SDK 5.0 adds support to the new VoIP push notification requirements introduced in iOS 13 & Xcode 11. If you build your App with Xcode 11, you must upgrade to this version to avoid incoming call disruption to your iOS 13 users.

You can find our easy to follow migration guide here.

For more information about the new VoIP push notification policy and affected SDK versions, please refer to this advisory.

Here are the links for: [Dynamic Framework], [Static Library], [docs], [Quickstart Guide]

The Make Outgoing Call widget has been updated to include full support for Answering Machine Detection and advanced call recording options. Simply re-add the widget to an existing Flow to pick up the new features.

To learn more, visit the documentation on the Make Outgoing Call widget, or try it out in Studio.

We now provide an Authy app user’s multi-device toggle status in the Authy API. This data is a useful account-takeover risk signal for Authy customers.

The new version of Marketing Campaigns now supports sending a Single Send to a segment based on engagement data for more personalized sending. This includes whether they have or haven’t opened or clicked within a given timeframe as well as how they’ve engaged with a particular Single Send.

The new version of Marketing Campaigns now offers a Segmentation API to create and send to a segment that is based on engagement (opens/clicks) with any Single Send or a specific Single Send.

With this release, you are able to set the bitrate your Voice Client JS application should use. This allows you to better plan and estimate your bandwidth requirements.

Click here for more information about the Max average bitrate API.