Twilio Conference Calls for Claude Code: Simulate a Warm Transfer

Explore the Twilio Conference participant states behind a warm transfer and validate the room's intended behavior with a local event sequence.

中文

Setup for Claude Code

Claude Code in a scratch workspace with three fictional participant IDs. The worked example uses no calls, live status callbacks or recordings.

In Claude Code add the Twilio marketplace with `/plugin marketplace add twilio/ai` and install `/plugin install twilio-developer-kit@twilio`. Invoke /twilio-conference-calls.
Review the source's participant hold and conference lifecycle rules. Write down which participant may leave without closing the room.

Example task

Use a local state table for caller C, agent A and agent B. Set C on hold, join B, brief B, release C from hold, and then remove A with the room configured to continue. Ask the agent to list the final members and caller state.

Expected result

The final room contains C and B, the caller is active again, and removing A does not end this fixture's room. The event log preserves the order of the warm transfer steps.

Upstream documentation

Original SKILL.md on GitHub · MIT license · Source reviewed 2026-11-15

Frequently asked question

What is the difference between hold and mute during a warm transfer?

Hold changes the participant's experience during the transfer. Mute controls that participant's own audio contribution without creating the same hold state.