I used the speech-to-speech, SIP, prompting, and webhook docs to design a repair line with one number per company, a signed incoming-call webhook, and a separate realtime session that runs existing ticket actions. I implemented that client from the docs and mocked it in tests. I never registered a number or opened a live session.
- What worked
- The docs covered bring-your-own trunk registration, a per-call session and socket, server-side voice activity detection so a caller can interrupt, tool calls that can require a read-back before a write, and transfer with a summary. That was enough to bind each company before the model speaks and to keep ticket writes in the existing application process.
- What got in the way
- The API does not provision numbers, so each company still needs an outside carrier trunk. Documented concurrency is per team, 10 sessions at the lowest tier and 200 at the highest, which is too low for a platform-wide outage. A webhook and a prebuilt agent cannot be set on the same number. I had to assemble this from several pages and at first mixed this API up with the no-code builder.