Twilio Changelog

Twilio customers sending messages via US A2P 10DLC can now log into Twilio Console - Trust Hub - A2P Messaging to check whether they have been incurring penalty fees from sending unregistered message segments.

The Twilio Programmable Voice <Connect> TwiML verb now supports the new TwiML noun <Conversation> as a resource target. This allows for fine-grained customization of Voice and Messaging workflows in Twilio Frontline. Frontline developers can inject custom actions into different stages of an active call. Example use cases include:

• Executing other Voice TwiML instructions before connecting a customer and a Frontline worker (e.g. customers are sent to an IVR before being connected to a Frontline worker)
• Configuring in-call behavior (e.g. to enable recording for all calls)
• Configuring call behavior after a participant leaves the call or when an error occurs (e.g. a customer is prompted to leave a voicemail message in the event no Frontline worker answers their call)

Check out the docs for more information on how to use the new <Connect><Conversation> TwiML functionality in your application.

You can now utilize the ampersand (&) character in Twilio Alphanumeric Sender IDs. This can help you send text messages from a sender that better represents your brand name: for example, Owl&Co. This feature is only available in Alphanumeric Sender ID-eligible countries. Please refer to this guide to learn how to use Alphanumeric Sender IDs with Twilio messaging services.

The Twilio Programmable Voice <Connect> TwiML verb now supports the new TwiML noun <Conversation> as a resource target. This allows for fine-grained customization of Voice and Messaging workflows in omnichannel applications. Twilio Frontline is a prime example of where this new capability is particularly useful - with today’s release, Frontline developers can inject custom actions into different stages of an active call. Example use cases include:

• Executing other Voice TwiML instructions before connecting a customer and a Frontline worker (e.g. customers are sent to an IVR before being connected to a Frontline worker)
• Configuring in-call behavior (e.g. to enable recording for all calls)
• Configuring call behavior after a participant leaves the call or when an error occurs (e.g. a customer is prompted to leave a voicemail message in the event no Frontline worker answers their call)

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

The Twilio Programmable Voice <Connect> TwiML verb now supports the new TwiML noun <Conversation> as a resource target. This allows for fine-grained customization of Voice and Messaging workflows in Twilio Frontline. Frontline developers can inject custom actions into different stages of an active call. Example use cases include:

• Executing other Voice TwiML instructions before connecting a customer and a Frontline worker (e.g. customers are sent to an IVR before being connected to a Frontline worker)
• Configuring in-call behavior (e.g. to enable recording for all calls)
• Configuring call behavior after a participant leaves the call or when an error occurs (e.g. a customer is prompted to leave a voicemail message in the event no Frontline worker answers their call)

Check out the docs for more information on how to use the new <Connect><Conversation> TwiML functionality in your application.

Twilio Flex can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

Lookup has introduced new mobile intelligence packages in its v2 API to help you power trusted interactions and build seamless onboarding experiences for your users. This includes:

• Line Type Intelligence, which returns the line type of a phone number, identifying everything from fixed VoIP and non-fixed VoIP numbers to landlines, toll-free and more. This is in Public Beta, supported worldwide and available self-service.
  
• SIM Swap, which detects recent changes between a mobile phone number and its associated SIM. This is in Private Beta, supported in key markets across Europe and North America.
• Call Forwarding, which returns the unconditional call forwarding status of a mobile phone number. This is in Private Beta and only supported in the UK.
• Lastly, the Lookup v2 API will also be supported by Twilio’s Ireland Region, which means you can call Lookup and ensure you remain data resident within the EU.

Read more about these features in our blog or check out our docs if you’re ready to start building.

When Twilio receives termination traffic to an inactive account, either due to the account being suspended or closed, Twilio will reply with a ‘603 Decline’ SIP Response. This will help trigger your infrastructure to failover to alternate trunks if your Twilio account is not active.

Included in the ‘603 Decline’ SIP response will be a X-Twilio-Error header referencing Error 10001: Account is not active. This will help your team to understand why your calls to Twilio are being declined so you can resolve the issue through adding funds if necessary or contacting Twilio Customer Support at help@twilio.com to inquire further.

See the docs for more information.

We are excited to release two new features to help you improve the resiliency of your Twilio Video workflows.

First, we have updated the congestion control used to measure available bandwidth for publisher and subscriber clients. The new congestion control will provide higher available bandwidth in extremely low bandwidth scenarios as well as faster bitrate recovery times in oscillating network conditions. This feature has been rolled out across all Twilio Video workflows and is automatically enabled on your Rooms.

Second, we released a new Media Warnings API. This API, which is only available for Javascript SDK users, will trigger a warning if you are recording a Participant but no media is being received by the media server. This alert enables you to know in advance if a recording track is going to be incomplete and empowers you to improve the situation by, for example, reconnecting the Participant. You can read more about the alert in our SDK changelog documentation.