Conversation Orchestrator is now generally available
Conversation Orchestrator is now generally available, providing a unified view of customer conversations across Voice, SMS, WhatsApp, RCS, and Chat channels. The release includes omnichannel support, intelligent conversation grouping, customer-centric identity management, and backwards compatibility with the Conversations classic API.
Conversation Orchestrator is now generally available, unlocking Twilio's Conversation Layer for customer interactions across channels. Conversation Orchestrator creates a unified view of customer conversations, whether they happen over Voice, SMS, WhatsApp, RCS, or Chat (via Conversations (classic) API). Conversation Orchestrator natively resolves Customer Particiapant addresses (e.g. phone numbers) to an Identity on the Profile in Conversation Memory. This foundation powers Conversation Intelligence, Conversation Memory, and Twilio Agent Connect with a complete picture of every customer interaction.
This release includes:
- Core conversation primitives: Conversations, Communications, and Participants resources provide the building blocks for representing any customer interaction, with full API support for creating, reading, updating, and managing conversation state
- Omnichannel support: One unified conversation model works across Voice, SMS, WhatsApp, RCS, and Chat, eliminating the need to stitch together data from separate channel silos
- Passive and Active ingestion: Choose how Conversations form and Communications flow into them. Ingest existing Twilio messaging and voice traffic automatically, or create conversations explicitly via API/TwiML when your application needs full control
- Intelligent conversation grouping: Configure how traffic groups into conversations, by:
- Customer Profile: Recognize the same Customer Participant across channels and devices. This is the default grouping.
- Participant Addresses: Omnichannel on same number/ address (ie sms and voice)
- Address and Channel: Every new channel makes a new Conversation
- Customer-centric identity: Customer Participants are automatically linked to persistent identities that follow them across channels. When adding Participants, they may be added using addresses or Profiles
- Conversations (classic) API compatibility: Bridge existing Conversations (classic) API services to Conversation Orchestrator, gaining access to Memory and Intelligence features while your application continues to work unchanged
Read the announcement blog post for the full story, or get started with the Conversation Orchestrator documentation.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Insights now tags HD audio calls
Voice Insights now automatically tags calls as HD Audio when they use AMR-WB or Opus codecs, helping you confirm endpoint configuration and correlate HD audio usage with transcription accuracy and customer satisfaction. The system also tags calls as Downsampled when HD audio is converted to narrowband, visible in Console, REST API, and Event Streams.
RCS messaging now supported on all major Canadian carriers
Twilio now supports sending RCS messages to Rogers phone numbers, completing RCS coverage across Canada's major carriers. Existing RCS Senders approved by other Canadian carriers are automatically submitted to Rogers for approval.
RCS messaging now supported on all major Canadian carriers
RCS messaging is now available to Rogers phone numbers in Canada, completing coverage across all major Canadian carriers. Previously approved RCS Senders will automatically be submitted to Rogers for review with no action required.