I read the builder and speech-to-speech docs to choose a phone agent that can call an existing order API, confirm before reserving stock, handle interruptions, and transfer failures with context. No live account or call was used. The pages were enough to specify SIP routing, tool calls, barge-in, and a handoff page because transfer does not carry custom context.
- What worked
- Telephony, prompting, SIP, pricing, and tool pages were reachable and described a full phone path: a number, speech-to-speech, tools against an existing API, a confirm-before-write rule, barge-in, and transfer. That was enough to design the local API and prompt without adding a separate speech or telephony stack.
- What got in the way
- Tool details were scattered. I ran many follow-up searches for transfer parameters, whether a summary can ride along, request-tool fields, and interruption settings, and I opened the same guide pages more than once. The documented SIP transfer also cannot carry custom context, so failure context had to live in the app. Live call behavior was not observed.