Twilio Changelog

We're excited to announce the new Bundle Clone API, allowing developers to quickly duplicate approved regulatory bundles between accounts without the need to be re-approved.

With the Bundle Clone resource, developers can reuse compliance information across Twilio accounts. The resource creates a copy of a twilio-approved regulatory bundle against another account within the same organization. The new regulatory bundle is automatically set to the twilio-approved status, enabling you to start provisioning phone numbers in the new account immediately.

This is particularly useful for ISV customers that want to more quickly assign numbers to themselves, or customers that want to move resources between their accounts.

To enhance account security and prevent unauthorized hosting of phone numbers, Twilio now requires phone number ownership verification.

Between November 1, 2024, and January 5, 2025, Twilio will enter a Heightened Awareness Period (HAP) to help ensure reliable message delivery during peak traffic times, such as the U.S. presidential election, Black Friday and Cyber Monday.

Twilio will announce the End of Life (EOL) for Capability Tokens next year (2025). Please refer to our Capability Tokens Migration documentation on how to update your applications.

Upcoming EIN Requirement for US Short Code Campaigns

Starting October 15, 2024, the CTIA and US Short Code Registry will implement an enhanced vetting process for all new US Short Code campaigns. As part of this process, businesses will be required to submit a valid Employer Identification Number (EIN) during the onboarding phase. This change is designed to increase trust and security across the messaging ecosystem by ensuring a direct relationship between the brand and the short code campaign.

Additionally, starting January 15, 2025, the EIN requirement will apply to all short code renewals. Failure to provide the EIN within 60 days of renewal could result in short code suspension until the required information is submitted.

Key Dates to Note:

• October 15, 2024: EIN submission required for all new short code campaigns.

• January 15, 2025: EIN submission required for all short code renewals.

What You Need to Do:

• For new short code campaigns: Ensure you have a valid EIN ready to submit during onboarding after October 15, 2024.

• For existing short codes: Be prepared to provide your EIN when your short code comes up for renewal starting January 15, 2025.

For further details, please review the official CTIA guidelines and Twilio Short Code Onboarding Requirements.

We are excited to announce that Flex UI 2.9.0 is now available. This release features the following additions and updates:

• We have certified that Flex UI works on Chromebooks, expanding your device options. 

• In Unified Profiles, your agents can now view customer interactions history information before any of your customer data sources are connected, immediately enabling them to provide more customized, efficient service.

Throughout Flex UI, you'll find a broad range of feature and UI enhancements, bug fixes, and more. 

For complete details, see the Flex UI release notes for 2.9.0.

The Twilio Programmable Voice SDKs now offer the new Call Message Events: User-Defined Messages and User-Defined Message Subscription resources for application developers. This release, available now in GA on the latest major versions of Voice JS, iOS, Android, and React Native SDKs, supports relaying custom events to and from your backend to a registered Voice SDK Client on any active call - all within the Twilio platform. By leveraging the existing signaling connection, you no longer need to set up your own communication channel between your client-side and server-side applications. This unlocks a host of advanced use cases, including:

• Relaying (and taking action on) call progress events

• In-line text transcriptions

• Upgrading 2-party call to multi-party via Voice Conference

• Presenting valuable context in your application at the right time

Check out the docs for more information on how to use the new functionality in your application. We can’t wait to see what you build!

The Twilio STUN-TURN service, also known as the Network Traversal Service, charges according to the megabytes relayed by the Twilio TURN servers. This release introduces a more accurate approach for measuring the relayed megabytes of a TURN session. For additional details on how we calculate relayed megabytes, see our FAQ page here. 

In addition, effective 1 October 2024, the legacy volume based discounting model for pay-as-you-go Twilio STUN-TURN customers is being retired. There is no change to the list prices, which are documented here. Customers who have not already done so should reach out to their Twilio Account Executive or contact our sales team here to discuss available discounts. With this change we are providing increased transparency into how we charge for the Twilio STUN-TURN service.

We are adding the SHAKEN/STIR bundle by default upon approval of a Primary Customer Profile (PCP). This is being done for all the new PCPs. We will also backfill SHAKEN/STIR for all existing PCPs without SHAKEN/STIR bundles.

What is SHAKEN/STIR?

SHAKEN/STIR is a caller authentication framework meant to help restore trust by reducing fraudulent robocalls and illegal phone number spoofing. 

Why is this happening?

In a SHAKEN/STIR call the originating carrier (Twilio in this case) signs calls with different attestation levels based on knowing the caller and the caller's right to use a phone number. The three attestation level are Full Attestation (A), Partial Attestation (B), and Gateway Attestation (C):

• A means the Identity of the caller is known, and they have the right to use the callerId in the outgoing call to the PSTN.

• B means the Identity of the caller is known but Twilio does not know if they have the right to use the callerId.

• C means all others, including international calls

Carriers take this into consideration so the better your attestation, the better chance of your calls being answered.

What should you do?

A SHAKEN/STIR will now be in your account by default. However, you still should complete the SHAKEN/STIR process by assigning phone numbers in your account to the approved Primary Customer Profile. This associates a single identity with the phone number. Please review the SHAKEN/STIR documentation for more information.