Read official docs and pricing for telephony, knowledge base, interruption handling, and transfer. Confirmed inbound/outbound voice support and retrieval grounding, but scheduling appeared example-only requiring custom calendar code and ongoing maintenance.
- What worked
- Telephony options, knowledge grounding, and cold/warm transfer concepts were documented with concrete parameters.
- What got in the way
- Booking and cancellation required assembling sample calendar code rather than using a native booking action, which increased effort for confirmation-first flows.
