twilio-conversation-orchestrator

Configure automatic conversation capture and routing across Twilio voice, SMS, WhatsApp, and RCS channels.

5.3k|765|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill twilio-conversation-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twilio-conversation-orchestrator
Source: https://github.com/openai/plugins/tree/main/plugins/twilio-developer-kit/skills/twilio-conversation-orchestrator
Command: npx skills add https://github.com/openai/plugins --skill twilio-conversation-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about twilio-conversation-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically capture SMS and voice calls into Twilio conversations?

Create a Conversation Orchestrator Configuration with passive capture rules per channel, matching from and to addresses with wildcards. Traffic matching the rules is automatically captured into conversations without manual creation of conversations or participants.

What is the difference between passive capture rules and active TwiML ingestion?

Passive ingestion uses declarative capture rules that automatically capture matching traffic, while active ingestion passes conversationConfiguration or conversationId parameters in ConversationRelay or Transcription TwiML. You can mix modes per channel, but never combine both for voice on the same call.

Why am I being double-charged for speech-to-text on Twilio voice calls?

Double STT billing occurs when passive VOICE capture rules (which use Real-Time Transcription) run alongside active TwiML voice using ConversationRelay or Transcription. Omit VOICE captureRules from your Configuration when passing conversation parameters in TwiML.

Can I update a Twilio Conversation Orchestrator Configuration with PATCH?

No, Configurations only support PUT with full replacement, and omitted fields are silently deleted. Always re-fetch the current Configuration, modify the needed fields, and PUT the complete object back.

What are the limitations of Twilio Conversation Orchestrator?

There is a hard limit of 10 Configurations per account with up to 100 capture rules per channel, grouping type is immutable after creation, and a Memory Store is mandatory. CLIENT and SIP voice calls also require explicit callType metadata in capture rules.