Pre-requisites
- AI Phone configured and receiving calls — see AI Phone Support.
- Twilio Flex credentials saved — see Connect Twilio Flex.
- Both webhooks registered (TaskRouter + Conversations service).
How calls land in Flex
What the rep sees
- A voice task in the Flex UI with the call already connected on accept.
- The call transcript so far, rendered in the conversation thread attached to the task.
- The handoff note above the transcript with summary, sentiment, and reason.
- The six
handoff*attributes on the task panel. - Caller number, any
flex_*custom data set during routing.
Channel-specific details
Warm transfer vs cold handoff
Warm transfer vs cold handoff
OpenCX performs a cold handoff by default — the AI releases the call and your workflow routes it to a human queue. For warm transfers (AI introduces the rep on the line before dropping off), configure it inside your Flex workflow; OpenCX does not orchestrate warm-transfer TwiML on your behalf.
Transcript timing
Transcript timing
The transcript is appended to the conversation as the AI and caller speak. On handoff, the most recent turns are guaranteed to be present; occasional sub-second tail segments may land a moment after the task is assigned.
Call recording
Call recording
Call recordings follow whatever your Twilio Voice configuration sets — OpenCX does not add or strip recording. If you rely on Twilio recordings for QA, the recording SID is on the call, not on the task.
IVR skip-ahead
IVR skip-ahead
If your number routes through an IVR before reaching the AI, OpenCX only sees the portion of the call after it picks up. Earlier IVR selections are not in the transcript unless your IVR passes them as task attributes.
Related Documentation
AI Phone Support
The channel itself — numbers, IVR, voice model.
Connect Twilio Flex
Credentials, webhook, workflow filters.
Twilio Flex overview
What else Flex lights up across every channel.
Troubleshooting
Missing task, wrong queue, events routed to the wrong org.