Admins in Flex can now manage their plugins, view the history of plugin releases, and rollback to prior deployments. This provides visibility and control of your application's version outside of a developer's command line interface.
The Flex Plugins CLI (Command Line Interface) is the new interface for developing, testing, and releasing plugins. It accelerates your plugin development by automating the key workflows you'll use while customizing Flex for your users.
With the Flex Plugins CLI developers can:
- Build new plugins - Start with a blank slate, or build from a template. Access all of Flex’s frontend programmability to customize the UI.
- Deploy and release plugin versions - Define plugin versions to track incremental updates to your customer experience. Deploy updates for each of your plugins individually, or bundle all of your updates together in a single release.
- Manage your version and release history - All of the updates to your plugin versions are tracked as a history of releases. Use this history to quickly identify and track changes in your application, and select a prior configuration to re-release in the event of an issue with your users.
Twilio Programmable Voice and Elastic SIP Trunking sign outgoing calls under the SHAKEN/STIR call authentication framework to increase call answer rates. Direct customers can create a Business Profile and enable SHAKEN/STIR in the Twilio Trust Hub and assign their Twilio local and toll-free US phone numbers to receive full attestation so that a trust indicator, “Caller Verified”, can be displayed on devices on participating destination networks.
For more details, please visit here.
In TaskRouter, you can now evaluate a Worker’s Activity state by referencing
worker.activity_name in a Workflow’s target expressions. This allows you to target or exclude agents based on the Activity that they are in.
For example, with Activity-based routing you can:
- Route high-value Tasks to agents even when they are scheduled to not receive general Tasks.
- Transfer Tasks to agents who are in Activities that are excluded from routing.
- Designate an Activity that allows an agent to only accept a particular type of task.
To learn more about the new feature, please refer to our documentation on Activity-based routing.
Twilio Video WebRTC Go is a new product offering that allows developers to build and operate 1:1 WebRTC based applications for free. This developer package provides the infrastructure components (signaling, TURN, logging, & diagnostics) required to run WebRTC applications in production. Participant minutes are free and the 25 GB/month of TURN server usage ensures enough relay support for roughly 100K minutes. To learn more, visit the documentation here.
In addition, a new one-on-one UI layout has been added to the Twilio Video quick deploy apps to support the new WebRTC Go Rooms and provide developers with a clean, modern visual design. Developers can now specify the desired Room type (group, peer-to-peer, or go) when building the quick deploy video app via the Twilio CLI RTC plugin. All the source code for the apps is available here:
- Web - https://github.com/twilio/twilio-video-app-react
- iOS - https://github.com/twilio/twilio-video-app-ios
- Android - https://github.com/twilio/twilio-video-app-android
For additional information about WebRTC Go and details on the new Video troubleshooting tools visit our blog post.
To help developers troubleshoot their applications at scale we are releasing three new Video troubleshooting tools. The first is a console tool called the Video Log Analyzer. It provides detailed information about Video Rooms and Participants. This can be used to quickly investigate Room and Participant issues that occurred in the past 2 days for WebRTC Go Rooms and 7 days for all other Rooms types.
The second is the RTC Diagnostics SDK 1.0.0-beta2, which provides test functions to allow developers troubleshoot camera, microphone, speaker, and network issues. This SDK is a general purpose WebRTC SDK and does not rely on Twilio infrastructure. Developers can incorporate it into their applications for pre-call testing or troubleshooting user issues. The source code and information on using the SDK is available here.
As part of Twilio's support for WhatsApp Business API being made Generally Available, Twilio has redesigned the templates console experience and added support for translations. Here's what's new:
Message templates now have a dedicated page. Navigate to Programmable Messaging > Senders > WhatsApp Templates to submit and view your templates.
Support for translations. Each message template now supports multiple versions across different languages. Instead of submitting one new template for each language, you can now add multiple translations under a single template. WhatsApp limits each account to 250 templates by default, but each template can now contain multiple languages, so this significantly expands the number of messages available to sent as notifications.
Template naming. You can now name each template. This provides context to your template submission and can increase your chances of approval with WhatsApp.
For more info about WhatsApp message templates, please refer to this article.
Twilio's support for the WhatsApp Business API is now Generailly Available! In addition to meeting Twilio’s SLA standards for GA products, this change represents an improvement in the product experience, support and resilience, as well as a commitment to offer WhatsApp as a first-class citizen across Twilio products.
To try WhatsApp, head over to Twilio Sandbox for WhatsApp. To get your own number, follow the onboarding instructions to connect your WhatsApp number. Once you are live, you can send and receive WhatsApp messages using the Programmable Messaging API or the Conversations API.
We are excited to announce that the Twilio Conversations API is now Generally Available!
Twilio Conversations is a single API for scalable, multiparty conversations across channels. Regardless of whether your clients communicate via web or in-app chat, in WhatsApp conversations, or over native group texting, the Conversations API reduces development time and helps you to deliver a superior customer experience.
In addition to meeting Twilio’s SLA standards for GA products, there’s a ton of new functionality packed into this release. You can read about all of the new features on the Twilio Blog, including dedicated Conversations SDKs for all three platforms – JS, iOS and Android – with support for Delivery Receipts.
We’re also now able to support compliant healthcare use cases for chat and SMS channels that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA).
Head to the updated Docs and start integrating Conversations into your communication flow. We just cannot wait to see what you build!
Policy updated as of September 28, 2020
Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020until November 4, 2020.
Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.During this Heightened Awareness Period, the following limitations will apply:
- A maximum of 1,000,000 additional 10-digit long code phone numbers can be added to customers' existing accounts within the +1 country code. These numbers are available on a first-come, first-served basis, with inventory being added regularly.
For more information see this FAQ.
Policy updated as of September 28, 2020
Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020 until November 4, 2020. Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.
During this Heightened Awareness Period, the following limitations will apply:
Account-level long code SMS rate limits have been implemented based on the amount of phone numbers:
- Customers with 2,000 or more 10-digit long code numbers on their project can send up to
2,000 MPStoward the United States.
- Customers with 100,000 or more 10-digit long code numbersas of October 2, 2020 on their project can send up to
4,000 MPStoward the United States. Twilio reserves the right to move the effective date of October 2, 2020 to an earlier date if too much capacity is allocated to customers, putting the network at risk.
For more details, please refer to this FAQ.
Twilio now supports sending up to 25 messages per second through WhatsApp.
If messages are sent at a rate higher than 25 MPS, Twilio maintains a queue. For very high outbound message volumes, messages can remain queued for up to 4 hours.
To achieve higher MPS, you can use Messaging Services. This allows you to distribute high volume across many WhatsApp senderes within the Messaging Service.
Twilio Programmable Voice and Elastic SIP Trunking now perform SHAKEN/STIR verification on incoming calls to your Twilio local phone numbers. It can be used to display a trust indicator or to make a routing decision, such as bypassing a voice captcha or IVR and directing the call to an end user.
A verified call that has been given the highest attestation under SHAKEN/STIR means that the carrier that originated the call both (1) knows the identity of the caller, and (2) knows the caller has the right to use the phone number as the caller ID.
In Programmable Voice the request webhook presents the StirVerstat parameter, and in Elastic SIP Trunking there is a new header called X-Twilio-VerStat with the verification result. The new parameter and header are only present for incoming calls with SHAKEN PASSporT identity headers. Today, support for the SHAKEN/STIR call authentication framework is being deployed in the United States only.
This release of Twilio Voice SDK now uses Chromium WebRTC 83. With this release, users will hear audio much sooner after the Call.Listener#onConnected callback than in prior releases. This upgrade ensures that when Call.Listener#onConnected is raised to the developer the media connection has been fully established. Additionally, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of RTT values.
To learn more about this release on our changelog.
You could always have multiple SMS participants in the same conversation talking to each other. However, each participant was previously bound to a single proxy address number through which they received all of the messages in the Conversation. In this scenario, each participant had no way of knowing how many people the proxy number represented.
It is now possible to add your US or Canada based clients as Group participants, utilising a Group MMS protocol. As a result, your clients will observe an iMessage style experience and easily see who said what. This is especially valuable for use-cases which expect an active participation of all interested parties, like wealth management, personal shopping, or real-estate industry.
Explore the Group Texting documentation and give it a try!
This release of Flex UI and WebChat UI introduces the public beta version of chat attachments. Chat attachments now includes drag-n-drop for your files, and you can compose a single message with both text and an attachment. For a complete overview of the feature and developer guides to programmatically customize the experience, check out the chat attachment docs.
Other notable changes:
- Flex WebChat UI CDN bundle size has been reduced to 390kb.
- Real-time Queues View is now enabled for all accounts. For more details on this feature, visit our Real-time Queues View docs.
Twilio SendGrid now allows you to define multiple From addresses in personalizations objects. This allows you to override the default sender in each personalization as long as the default sending domain and personalizations sending domains match. For more information, visit our Personalizations documentation.
You can now disable any Verify v2 delivery channel (SMS, Call, Email) that you are not using to reduce your risk of potential abuse. Navigate to your Verify Service Settings page to use this feature.
This major release of Twilio Voice SDK now uses WebRTC 83. With this release users will hear audio much sooner after the [TVOCallDelegate callDidConnect:] callback than in prior releases. This upgrade ensures that when [TVOCallDelegate callDidConnect:] is raised to the developer the media connection has been fully established. Additionally this release improves the interoperability of the SDK with Swift. Lastly, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of rtt values.
To migrate from 5.X to 6.X please see the migration guide.
To learn more about this release on our changelog.
Introducing the API for Elastic SIP Trunking Call Transfer (SIP Refer) feature. This feature enables you to move an active call from one endpoint to another. Twilio's Elastic SIP Trunking product supports "blind" call transfers. This allows you to configure SIP Refer on a Trunk using the API.
For details, please check our Elastic SIP Trunking API for Call Transfer via SIP REFER documentation.
As a side note, you can also configure Elastic SIP Trunking Call Transfer (SIP Refer) feature through Twilio console. Details of console configuration can be found here.