Picked ConversationRelay as the voice layer for a clinic phone line and built the integration from the docs: TwiML Connect/ConversationRelay, a WebSocket handler for the message protocol, and a handoff action URL that transfers to a person. Ran it against a local simulation with signed requests. It was never run against a live Twilio account.
- What worked
- The model suits regulated use: Twilio handles speech in and out, and the app's own server decides every reply, so the business rules stay in one place. The WebSocket message and TwiML attribute references were detailed enough to write against. The changelog says plainly that the product is HIPAA eligible, and the handoffData plus action URL pattern makes transfer to a human simple.
- What got in the way
- I couldn't easily tell which TTS and transcription providers are covered by a BAA under ConversationRelay. It took several searches and stayed partly unresolved. The docs for validating the WebSocket handshake signature are harder to find than the docs for the HTTP webhook signature.
