Twilio Changelog

Twilio is committed to streamlining the A2P 10DLC campaign registration process and providing transparent feedback on issues that might arise during registration. To enhance this experience, we are rolling out three new error codes that will convey more specific reasons for registration setbacks, enabling you to quickly address and resolve these issues.

New Error Codes:

• Error 30907: Encountered when there is a validation issue with the website URL provided.
• Error 30908: Returned when a Campaign registration lacks a compliant privacy policy.
• Error 30909: Issued for unverifiable Calls to Action (CTA) within the Campaign registration.

To learn more about these error codes, please read the Twilio support article. For a detailed list of all error codes please visit Twilio Error and Warning Dictionary. 

We previously announced the Call Message Events feature for Twilio Programmable Voice JS and iOS SDKs earlier this year. This release extends support to the Android SDK.

The Twilio Programmable Voice SDKs now offer the new Call Message Events: User-Defined Messages and User-Defined Message Subscription resources for application developers on JS, iOS, and now Android SDKs. This release, available now in Public Beta on the latest major version of the Voice Android SDK, 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

In coming releases we’ll bring this functionality to our React Native SDK as well as explore options to provide “out-of-the-box” event subscriptions for common use cases. 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!

Effective November 8, 2023, Twilio requires all U.S.-bound messages from toll-free (TF) phone numbers to be fully verified or pending verification (meaning customers have submitted their numbers for verification).

Any blocked messages sent from an unverified toll-free number will return Error 30032 and filtered messages will return Error 30007. Twilio messaging rates still apply for blocked messages.

Please register your toll-free phone number as soon as possible to avoid impact to your messaging traffic. You may use our Twilio Console or API options to submit your verification information.

For more information, please check out our guide Toll-Free Message Verification for US/Canada.

The Warm Transfer feature is now generally available in Flex. 

With warm transfers, agents can:

• Call another agent or a queue for consultation about an ongoing customer call

• Start a conference call between another agent and a customer

• Transfer the customer to another agent

For more information, see: Warm Transfer - End User Guide.

Effective December 15, 2023, Twilio will End of Life (EOL) the API Explorer feature in Console used to explore the REST API. After this date, the API Explorer will be unavailable for all customers.

If you want to continue to explore our API, we recommend using our API Documentation or the Twilio OpenAPI Specification with third party vendors like Postman.

Twilio Content Template Builder, formerly known as the Content API and Content Editor is now generally available. 

The Content Template Builder enables you to create and manage rich messaging templates and utilize them across all supported messaging channels, including SMS, WhatsApp, Google’s Business Messages, and Facebook Messenger. Send engaging rich messages to users no matter where you reach them with the Content Template Builder.

Try out new features:

• Build rich conversational experiences with content templates in Studio
• Send personalized outbound campaigns and notifications at a future time using content templates sent with Message Scheduling
• Create content templates with dynamic header text for WhatsApp

Click here to learn more. 

Content Templates, Content Variables, and rich features from Content Template Builder are now supported in Studio.

Content Templates are currently available on WhatsApp, Facebook Messenger, SMS, MMS, and Google Business Messages. New channels will continually be added. 

Content Templates can be used for generating automated responses to your customers in Twilio supported channels. Content Templates enable the use of rich content and personalization via buttons, media, variables, and channel specific template types to drive greater engagement and streamlined messaging interactions.

Use Content Templates in Send and Send & Reply widgets. Use rich features in the Split widget. 

Variables in WhatsApp and other channels can now be specified using Content Variables via key-value pairs instead of body insertion in a simple deterministic structure.

See our public documentation to learn more.

ParticipantCallStatus and ReasonParticipantLeft are now being returned as attributes on the participant-leave Conference status callback event. 

Previously, discerning the reason for a given participant's departure from a conference could be challenging; for example, if a participant was added using the /Participants API but failed to answer the incoming call, the application would need to tie together the call’s status for its callbacks with the 'participant-leave' callback.

The participant-leave event callback now contains all of the information required to discern the underlying call status for a participant, as well as the cause of a participant's departure from the conference.

Developers can now provide a call token from an incoming Programmable Voice call when creating a new conference participant in order to reuse the caller ID from that incoming call.

Previously, call token support was only available for the /Calls API, and developers who wanted to use the /Participants API were limited to using Twilio phone numbers or verified caller IDs as the caller ID when doing a POST to /Participants. 

To reuse the caller ID from an inbound Programmable Voice call when creating a new conference participant simply pass the CallToken from the inbound call as a parameter to the /Participants API.

For more information, see our docs.