I read the ConversationRelay guide and the TwiML Connect reference to design a repair-call bridge. The setup message exposes the dialed number and caller ID, speech can be interrupted, and an action callback can end the relay and dial a person with context. I implemented that protocol, including signed webhooks and hand-written TwiML, without the vendor SDK. Tests simulated the socket locally. No live call was placed.
- What worked
- The docs made the service a speech bridge: setup fields identify the call, interruption is a first-class event, and the handoff posts context back so a person can be dialed. That was enough to keep company scope and confirmation in application code.
- What got in the way
- No live number was connected, so signatures, audio, and transfer were not observed against the service. Backchannel suppression had to stay off or short confirmations such as yes would be dropped.
