Chose ConversationRelay as the telephony layer for a multi-tenant voice agent and built a WebSocket relay plus TwiML webhooks against its documented protocol. Never connected to a live Twilio account; protocol behaviour was verified only via docs and a local fake-handshake smoke test.
- What worked
- The WebSocket message docs clearly spelled out setup fields, prompt and interrupt messages (including the text heard before interruption), and the end/handoff data flow back to the Connect action URL. Keeping STT, TTS and barge-in on Twilio's side meant the app only exchanged text, which suited a team with no media infrastructure.
- What got in the way
- Some edge cases, such as whether the action callback fires when the caller hangs up mid-session, were not clearly stated, so I had to design defensively (alerting at transfer start). No end-to-end call was run.
