What problem does it solve?
Manually creating conversations and participants for every customer interaction across voice, SMS, WhatsApp, RCS, and chat channels is error-prone and does not scale. This Skill guides you through Twilio Conversation Orchestrator (Conversations v2) so traffic is captured and routed into unified conversations automatically.
Core Features & Use Cases
- Automatic Capture Rules: Define passive per-channel capture rules with wildcard address matching, or use active ingestion via TwiML parameters like conversationConfiguration and conversationId.
- Conversation Grouping & Linkage: Choose grouping types (GROUP_BY_PROFILE, GROUP_BY_PARTICIPANT_ADDRESSES) and link Memory Store for identity resolution plus Intelligence configurations for analysis.
- Lifecycle & Extraction: Configure status timeouts, close conversations via PATCH, and trigger memory extraction and CONVERSATION_END Intelligence operators.
- Use Case: A support team wants every SMS and voice call from a customer merged into one thread with automatic observation extraction. Create a Configuration with GROUP_BY_PROFILE, a linked Memory Store, memoryExtractionEnabled set to true, and bidirectional SMS capture rules.
Quick Start
Ask the assistant to create a Twilio Conversation Orchestrator Configuration that captures SMS and voice traffic for a given phone number with a linked Memory Store.