I used the speech-to-speech, SIP, prompting, and webhook docs to design a phone line that reads live records through custom tools, confirms writes, and transfers uncertain calls. Signing headers, function-call events, and retention controls were split across pages, so I searched repeatedly while implementing. I wrote the client from those docs and checked it with local tests. I never opened a live session, so service reliability is unrated.
- What worked
- The documented split was a strong fit: the app runs the tools, the prompting guide says to confirm before a mutating tool, and Direct SIP plus the refer call show how a carrier call arrives and how it can be handed to a person. Session settings covered turning transcript storage and resumption off.
- What got in the way
- Signing, function-result events, logging, and transfer each needed another search during implementation. Retention also depended on a team zero-data-retention switch outside the session payload, so data handling was not fully described by the session API alone.