Twilio Conversations | Sep. 27, 2026
On-demand rule execution and Conversation Metadata now generally available with Twilio Conversations
Today, we are launching two new capabilities with Twilio Conversations– On-demand rule execution for Conversation Intelligence and Conversation metadata for Conversation Orchestrator
On Demand Rule Execution for Conversation Intelligence
On-demand rule execution gives developers direct, programmatic control over when Conversation Intelligence analysis runs. Rather than relying solely on conversation lifecycle events, your application can trigger rule execution at any moment — at agent handoffs, after specific conversation signals, or selectively on conversations that warrant further analysis.
This capability also supports parameter overrides. Operator parameters — such as classification prompts, confidence thresholds, or domain-specific terms — can be overridden at runtime on a per-execution basis, without modifying the stored rule. This means a single rule configuration can dynamically adapt to the context of each conversation — serving a range of scenarios that differ only in one or two parameters, without maintaining separate rules per variation. To learn more, see On-demand rule execution
Conversation metadata for Twilio Conversations
Conversation metadata introduces a native key-value store on the Conversation resource, enabling your application to attach and update structured context alongside the conversation record. Store external identifiers, derived state from one step of a workflow to the next, or per-conversation configuration toggles — all encrypted at rest and returned as part of the standard Conversation resource response, with no separate datastore required. To learn more, see Conversation metadata.
Combining on-demand rule execution with conversation metadata
Used together, on-demand rule execution and conversation metadata enable workflows where context from earlier in a conversation informs what analysis runs next — all within the Twilio Conversations record. A common pattern– your application runs a lightweight rule via the API, stores the result in metadata, then uses that signal to decide whether deeper analysis is warranted — keeping heavier rules conditional on earlier signals
To learn more about building tiered intelligence workflows using both capabilities together, see Build on-demand workflows with Conversation Intelligence