I used the public voice docs to design an inbound repair line: direct SIP, a signed incoming-call webhook, a realtime socket pinned to a voice model, and client-side function tools so record reads and writes stay in the app. Tests used fakes. I never registered a number or joined a live session, so request shapes stayed unverified.
- What worked
- The docs describe client-side function tools, SIP refer and hangup, session configuration, and real-time audio that the service does not store. That matched a line which must use live records, confirm writes in the app, and keep codes and transcripts out of ordinary logs. Zero Data Retention is described as something the session can confirm before the agent starts.
- What got in the way
- Webhook signing, phone-number registration fields, tool confirmation, retention, and the prompting rules lived on separate pages. I fetched the realtime, SIP, prompting, security, and phone-number references more than once before the call path was clear. Spoken write confirmation is not a tool flag and had to be enforced in application code.