Picked ConversationRelay to handle speech-to-text, text-to-speech and barge-in, so the LLM and all data access could stay in our own backend. Read the TwiML noun, onboarding and WebSocket message docs, then built the webhook, TwiML and WebSocket relay to match. Never ran it against a live call, so reliability is not rated.
- What worked
- The docs clearly explained the WebSocket message types (setup, prompt, interrupt, text tokens, end) and how custom parameters reach the setup message. That made it easy to pass a server-signed one-time token and to treat interruptions correctly. Keeping only text on the wire fit a strict multi-tenant backend well.
- What got in the way
- The pages I read did not say clearly whether the WebSocket upgrade is signed the same way webhooks are, so I had to hedge on that and leave it to be confirmed against a real call.
