Product changelog and announcements

In Segment, when building an audience based on audience membership, you can use existing audiences as criteria for creating new audiences. You can include or exclude profiles based on their membership in other audiences, allowing you to generate more specific audience segments. You can configure your conditions with:

• Import audience conditions: This copies the conditions from the referenced audience and generates a combined SQL query. The audience runs independently, even if you disable the original audience or update it later. Use this option when you need the freshest compute result, since this eliminates the Profile Sync delay (about 1 hour).

• Use audience membership traits: This references the original audience membership traits, so it may take extra time to update if that audience needs to recompute. Use this option if the base audience membership doesn’t need to be recomputed every time, in order to save on compute costs.

To learn more, see our Linked Audiences docs.

In Segment, Linked Audiences now supports data freshness detection for Identify events. When you configure an activation with the new "Profile enters or exits audience or entity values changed" trigger, Segment detects changes to entity context data between runs and emits an Identify event for affected profiles — even if their audience membership hasn't changed. This keeps enrichment values up to date in Braze, Customer.io, and AWS S3, making it easier to power time-sensitive journeys like past-due reminders, onboarding sequences, and abandoned cart campaigns.

To learn more, see our Linked Audiences docs.

In Segment, you can now choose to build entity-based Linked Audiences, explicitly scoped to entities such as accounts, businesses, or households. Once users select the activation target upfront, the builder dynamically adapts, ensuring conditions, operators, and validations match user expectations for that specific entity. When you preview your Linked Audience, you'll see the count of audience members who meet the criteria and a sample of matching entities.

To learn more, see our Linked Audiences docs.

Twilio Studio now natively supports RCS (rich communication services) for both outbound and incoming message flows. This means you can now build and automate rich, branded, and interactive messaging experiences directly within Studio, leveraging all the benefits of RCS—such as rich media, card crousels, and webviews—without the need for workarounds or custom integrations.

For configuration details and best practices, see our documentation:

• Get started with RCS messaging

• Use RCS messaging with Studio

Studio now includes the Start Conversation widget, which enables Studio flows to initiate a two-way Twilio Conversation without requiring custom code or direct API calls. This widget creates a Conversation with a single participant and configures Studio to continue the flow when inbound messages are received.

Note that this widget is only for outbound/REST API triggered flows. Inbound flows already support Twilio Conversations without the Start Conversation widget.

For more information, see our Start Conversation widget docs.

Starting March 18, 2026, MMS rate limits for Application-to-Person (A2P) U.S. 10-digit long code (10DLC) numbers are determined by Brand Trust Score and Campaign use case, replacing the previous fixed account-level cap of 1 message per second (MPS).

Twilio Programmable Messaging automatically unifies opt-out management across RCS, SMS, and MMS channels.

When an end-user replies with any opt-out keywords (such as STOP, CANCEL, or UNSUBSCRIBE etc) to an RCS message, Twilio automatically enforces that opt-out for all future SMS or MMS messages sent from that same Sender or Messaging Service. Conversely, opt outs on SMS or MMS will automatically block future RCS messages.

Any attempt to message an opted-out user across these unified channels will now fail and return Error 21610.

This cross-channel compliance is active by default to protect your sender reputation, prevent accidental messaging on fallback channels, and requires no code changes to implement.

For more information, read our documentation.

This new action supports async batch for SFMC destination extensions (Without observability)

Studio now includes a ConversationRelay widget that allows you to connect live voice calls directly to a WebSocket server (that you provide) using Twilio ConversationRelay.

This widget:

• Exposes ConversationRelay configuration options

• Supports custom parameters and voice controls

• Provides Success and Failed transitions for orchestrating session outcomes within Studio flows

For more information, see our ConversationRelay widget docs. 

Starting March 23, 2026, we’ll begin rolling out more specific and detailed error codes for US A2P 10DLC Campaign registrations.

These new codes are designed to give you clearer, more actionable feedback when a campaign is rejected or requires an edit - helping you resolve compliance issues faster and get your messaging live.

The existing error codes will still be supported, but these new granular codes provide the specific context needed for rapid troubleshooting.

What’s changing?
Currently, A2P 10DLC rejection messages can sometimes be broad, making it difficult to identify the exact compliance blocker. With this update, you’ll see granular error codes that pinpoint the specific reason. 

These new codes will appear in:

• API Responses
• Event Streams
• Twilio Console (Campaign Details Page)

What this means for you
If you have built custom logic or processes to handle A2P 10DLC registration errors, we recommend reviewing your error mapping.

Updating your tools to reflect these new, specific codes will allow your end-customers and operations teams to respond to rejections with much higher precision.

For a full list of the new codes and their meanings, please refer to the Support Article on Campaign Rejections.