Plan Twilio Conversation Orchestrator in Codex with Demo Routing
Plan how Twilio groups synthetic support events and test a local conversation lifecycle without turning on message capture.
中文Setup for Codex (Twilio Developer Kit)
Use the Twilio Developer Kit in Codex. The fixture uses fake channel events and customer IDs. A real rollout needs an authorized test account and a reviewed data-handling plan.
- Open /plugins and add Twilio Developer Kit. The official package contains the related memory and routing guides used by the skill.
- Invoke $twilio-conversation-orchestrator in a blank practice project. Use the following fictional input for a dry run.
Example task
Ask for a routing plan using demo profile A, one fake chat event and one fake SMS event, plus a third event with no profile. Enable grouping by profile only in a local simulator and check the event-to-group mapping.Expected result
The first two events share one test group. The event with no profile stays unresolved and does not add a third real contact. The rollout plan names the desired capture channels and the ownership of retention and verification.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Can this exercise prove which live channels are captured?
It validates your grouping rules using artificial inputs. Use the current Twilio account configuration and a controlled test environment to verify live channel behavior.