Twilio Conversations Classic API: Test a Multi-Channel Thread
Model participants, messages and history in a single Twilio Conversations classic thread with a local fixture before using the live API.
中文Setup for Codex
Codex in a scratch project. The exercise uses fake conversation and participant IDs. A live deployment requires Conversations classic access and configured channels.
- Use the pinned Twilio checkout linked below. Copy `skills/twilio/twilio-conversations-classic-api/` to the scratch project's `.agents/skills/twilio-conversations-classic-api/` and load the skill from a fresh Codex session.
- Confirm the guide targets Conversations classic v1. Map the relationship among the conversation, participant records and messages before adding integration code.
Example task
Make a local mock for conversation demo-01 with web participant web-1 and messaging participant msg-1. Have each add one message in order, then ask how the thread history differs from a pair of unrelated outbound messages.Expected result
Both messages are in demo-01 in fixture order with their respective participant IDs. No extra conversation is created when the second participant replies.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
What is the main distinction between Twilio Conversations classic and a one-off message?
A Conversations classic thread represents persistent participants and message history across the configured channels.