Twilio Changelog

In Marketing Campaigns, you can now segment contacts from a particular list directly from the Contacts page. This reduces the steps to create list-specific segments.

You can now view WhatsApp template rejection reasons in console. When WhatsApp rejects a submitted template, they provide a reason:

• PROMOTIONAL: WhatsApp has deemed this to contain promotional or marketing content.
• TAG_CONTENT_MISMATCH: The language and/or template category selected don't match the template content.
• INVALID_FORMAT: Placeholders or other elementse formatted incorrectly.

Previously, this information was only available by opening a support ticket. For additional details on template rejection reasons from WhatsApp, please refer to our Guidance on Templates.

Happy building!

The Conference Create Participant API has been updated to ensure that any outbound call placed to a phone number uses a Twilio number or verified outgoing caller id in the From field. This change prevents malicious actors from using the API to spoof a phone call from an arbitrary phone number. Note that calls placed to a Twilio Client or a SIP address are not impacted by this change.

We are adding a new IP address block for the Media Server range in our Frankfurt, Germany (de1) region. This range will be used for the Programmable Video service and our Network Traversal Service. The new IP block is listed on the IP Addresses page in our Video documentation and on the Network Traversal Service Regions page.

If you have allowed the IP addresses of the de1 region in your Firewall, then your Firewall configuration will have to be updated to include the new IP block. This new block will go into rotation on April 16th, 2020.

Flex has supported only inbound voice flows natively so far. For outbound capability, either you had to build the Dialpad yourself, use the experimental dialpad, or use one of the community-supported plugins. With this update, Flex now offers native outbound dialing ability right from the Flex UI.

With the Flex Dialpad:

• Agents can call customers directly from Flex and associate it with a relevant queue for reporting.
• Agents can call customers while in an unavailable state, allowing them to remain uninterrupted from incoming tasks.
• While on an outbound call, agents can initiate either Warm
  Transfer or Cold Transfer to another agent or supervisor.
• Supervisors can monitor outbound calls.
• Outbound calls will be presented both in real-time and historical reporting in Flex.
• Developers can build click-to-dial use cases using the programmability offered through the new StartOutboundCall Action.

The Flex Dialpad is a part of the Flex UI and offers all of the theming and customizability features of a React component.

For more details, visit our announcement blog post and the Dialpad documentation.

You can get your hands on the Flex Dialpad now by upgrading your Flex Instance to v1.18 and then enabling Flex Dialpad in your Flex Settings in Twilio Console.

Emergency Calling is now available for Programmable Voice SIP Interfaces in the US and Canada. Customers are now able to make Emergency Calls from their IP communications infrastructure using Programmable Voice SIP Interfaces with the Twilio platform, which will route 911 calls to the appropriate Public Safety Answering Point (or PSAP) and programmatically pass along the corresponding emergency address.

Click here to learn more.

The following additions to the Video Recording service are now Generally Available:

• Recording Composition API: provides developers flexibility to mix the media files of a Room recording into a high-quality, custom layout that matches their specific use case.
• Composition Hooks API: allows developers to streamline the recording workflow by automating the creation of Recording Compositions for every Room.
• Public Key Encryption for Recordings & Compositions: for enhanced security we are offering Enterprise customers the ability to encrypt recordings and compositions with a customer provided public encryption key.
• External AWS S3 Storage: Enterprise customers can configure the Recording service to push Recordings or Compositions directly to their AWS S3 Bucket.

These Video recording features allow developers to create a recording workflow that matches their specific use case and security needs. For example, a customer in the Healthcare industry may decide to encrypt all recordings with their Public Key and have them automatically stored to their external storage, and a customer in the Education space may decide to compose the recording of a virtual classroom into a presentation layout for students.

To learn more check out the blog post or visit the documentation on Recording Composition API, Composition Hooks API, Encrypting your Stored Media and Storing to AWS S3.

You can now send and receive media messages that are up to 16MB in size on Twilio API for WhatsApp, an increase from a previous size limit of 5MB.

The Twilio API for WhatsApp supports sending and receiving images, audio, PDF files, and video. The following formats are currently supported:

• Images: JPG, JPEG, PNG
• Audio: MP3, OGG, AMR
• Documents: PDF
• Video: MP4

Please refer to our Guidance on WhatsApp Media Messages for additional details on media messages on Twilio API for WhatsApp.

Happy building!

Secure Real-time Transport Protocol (SRTP) provides encryption to ensure that the call media is private during transmission over a public network.

Pricing

SRTP Document

Programmable Voice SIP Document

To increase the capacity of chat applications, Actions Per Second (APS) limits for critical operations now apply on a per channel basis, rather than a per Chat Service basis. Until recently the number of messages you sent and number of channels you had were in a competition with each other.

The following operations are rate-limited per channel, with a default maximum set at 30 APS separately for each channel:

• Channel update
• Member create, update, delete
• Message create, update, delete
• Invite create, update, delete

The following operations will still be governed globally, with a single 30 APS limit applying to each Chat Service as a whole:

• Channel create, delete
• User create, update, delete
• Role create, update, delete
• Binding delete

This means users of your application can now communicate as much as they wish to without affecting the application.

Read more on the Programmable Chat Limits page.