Chose this platform after comparing SIP options, then implemented a Rails HTTP tool layer, agent definition, and sync client from its docs without calling the live service. Telephony, warm-transfer, and custom-tool docs were enough to design barge-in, confirmed writes, and a PBX-preserving SIP path. Several advertised doc routes 404ed, and transfer SIP headers were static, so a custom prepare-transfer tool had to supply spoken context instead.
- What worked
- Docs that loaded made bring-your-own SIP, HTTP tools against an existing API, native barge-in, and warm transfer with spoken context clear enough to map onto an existing PBX without replacing the carrier or numbers.
- What got in the way
- Direct fetches of HTTP-tools and built-in-tools pages returned 404, so paths had to be rediscovered through the docs index and search. Transfer SIP headers could not be set dynamically from tool output, which forced an extra briefing tool before the built-in transfer.