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.
You could always have multiple SMS participants in the same conversation talking to each other. However, each of them received all of the messages through the one and only proxy address number bound to him and did not know how many people it 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!
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.
With this release developers can pass custom parameters when dialing Twilio Client using Twilio Voice REST API. You can build personalized application experiences for end users by displaying valuable contextual details about the incoming call. For example, you can pass the customer name, type, or product of interest when dialing Twilio Client, and display to the agent.
The custom parameters can be specified as a query string in the ‘To’ parameter of the Create Call Resource and delivered via the Twilio Voice Client.
We have updated TaskRouter’s error and warning messages to improve clarity and troubleshooting.
The following list of Error and Warning messages have been added:
|40139||ERROR||Failed to issue Dequeue instruction due to missing or invalid Activity Sid.|
|40147||ERROR||Failed to issue Supervise instruction due to missing or invalid ‘contact_uri’ property.|
|40149||ERROR||Failed to issue Conference instruction due to missing ‘conference_sid’.|
The following list of Error and Warning messages have been updated:
|40005||WARNING||Changed Type from Twilio to Application.|
|40140||ERROR||Updated message text and description for clarity.|
|40142||ERROR||Updated message text and description for clarity.|
|40148||ERROR||Updated message text and description for clarity.|
For Editions customers, we are introducing a more flexible way to view the Audit Event data in the Twilio Console. This allows viewing by user and filtering the event data.
The list of events now tracked by Audit Events includes new event types, such as console logins. The new event types are only visible in the Twilio console in Audit Event Insights are documented with the other Audit Event data: https://www.twilio.com/docs/usage/monitor-events.
These changes do not impact the Audit Event API. New event types are not available yet in the Audit Event/Monitor Event API
A new Deactivations API for US Messaging is now available. This API returns you a file that contains phone numbers that have been removed from the US Carriers on the specified date. This allows you to automatically keep your subscriber lists clean by removing deactivated phone numbers from your campaigns.
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.
CVE-2020-24655 - A race condition in the Twilio Authy 2-Factor Authentication Application allowed a user to potentially approve/deny an access request prior to unlocking the application with a pin on older Android devices, effectively bypassing the PIN requirement. This issue has been fixed as part of the 24.3.7 Release of the Twilio Authy App. Other operating systems (iOS, MacOS, Linux and Windows) are not affected by this vulnerability.
See 24.3.7 release details here.
Cloud calling solution provided by ZoomPhones 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.
With this SDK release the local network path is no longer automatically included as one of the connection candidates. This modification ensures that users will not see a change in application behavior when upgrading to iOS 14.0 or iPadOS 14.0. Developers can still opt to include the local network as a connection candidate by setting a parameter. We recommend developers upgrade their Peer-to-Peer application to ensure correct behavior with iOS 14.0 and avoid any adverse changes to the experience.
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
readyfor 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.
Learn more about all of the Super SIM states here.
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?
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 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.
Trunking Termination Calls per Second (CPS) refers to how many new SIP Trunking call setups are allowed in one second for Trunking Termination calls (outgoing traffic from your communications infrastructure to the PSTN). Twilio, by default, provides the ability for you to place 1 CPS per Trunk per Region (see limits).
With this release you are now able to immediately increase your Trunk CPS settings per region (up to 15cps) in the Console, under the specific Trunk, under Termination settings.