Product changelog and announcements

As of 1st April, 2024,  SMS Pumping Protection for Twilio Programmable Messaging is generally available to prevent fraudulent SMS traffic and lower its significant costs. This feature automatically detects messaging traffic driven by SMS pumping and blocks it from being sent.

SMS Pumping Protection requires no configuration. Enable it in the Twilio Console and Twilio will do the rest. 

The performance of the feature can be monitored via existing Messaging Insights & the newly launched SMS Pumping Insights.

To further customize your SMS pumping protection experience, we have also launched RiskCheck and the Global Safelist.

Source Volume alerting is now generally available for all Cloud Streaming Sources.

When viewing a source, access the Alert tab and provide a percentage threshold to alert against positive or negative changes in the event volume emitted from the source compared to the previous 24 hours.

For example, if you set a change percentage of 4%, Segment notifies you when your source ingests less than 96% or more than 104% of the typical event volume.

Additionally, for this new alert and the preexisting Destination Delivery alert, you can now specify a specific email address as the recipient for a triggered alert and/or a Slack channel of your choosing (in-app alerts also remain an option).

Delivery Overview is now generally available for all cloud-streaming destinations receiving events from cloud-streaming sources.

With Delivery Overview, you can verify that your source receives your events, that any filters and Tracking Plans work as expected, and that events successfully flow to your destination.

You can use Delivery Overview’s pipeline view to identify any event delivery errors or unexpected behavior, leading to quicker resolution of data quality issues.

For more information, see the Delivery Overview documentation.

Starting May 9, 2024, Twillio will remove any phone range blocks on your account that have been active for longer than 30 days.

In the past, some accounts received a notification that fraud was detected on those accounts and that Twilio enacted blocking for certain prefixes. These blocks were internally set using the messaging opt out functionality which is why outbound messages destined for these blocks fail with Twilio error code 21610. As there is no way for customers to control this functionality and since fraud activity tends to dissipate after blocking, we will be removing these blocks from those accounts.

What do you need to do? We recommend regularly reviewing your SMS geo permissions and only enabling countries where you intend to send messages and incur messaging costs. This is a more efficient method to prevent unwanted messages without the risk of blocking legitimate traffic. To enable or disable Geo Permissions, go to your Console’s Geo Permission settings.

Recently, a change was made to allow workers to change from one Available activity state to another while they have task reservations. Reserved tasks will remain with the worker until the worker accepts or rejects them, or until the reservation timeout is reached.

Previously, a worker with a task reservation could not change their status from one Available activity state to another while a task  was pending.

This means that when a worker changes from one Available activity state to another, they might still have reservations for their previous activity state. For example, if a worker’s activity state is High Value Tasks and they change their state to Low Value Tasks, that worker may still have pending High Value Tasks reservations. The worker would need to accept or reject those reservations. If the worker doesn’t take any action, the tasks will remain reserved until they reach the reservation timeout.

Recently, support for JitterBufferSize was added for conference instruction in the TaskRouter API. If you experience high call latency on conference calls, you can adjust this setting to improve call quality.

As of 1st April, 2024, the Global Safelist API is now generally available for Twilio Programmable Messaging. Twilio's Global Safelist API empowers you to manage trusted phone numbers that they are not blocked by Twilio’s algorithms for SMS Pumping Protection on Twilio Programmable Messaging.

We have begun enabling accounts for improved message creation API error visibility in  SMS logs and Messaging Insights in the Twilio Console as well as when you list messages via the Programmable Messaging API. Full details are available here. When your account is enabled, the banners on those console pages will update to reflect that your account is enabled. Note that accounts will be enabled on a per-account-sid basis over the coming weeks; thus certain sub-accounts may gain access before others.