Pre-requisites
- AI SMS configured and receiving messages — see AI SMS Support.
- Twilio Flex credentials saved — see Connect Twilio Flex.
- Both webhooks registered (TaskRouter + Conversations service).
How messages land in Flex
What the rep sees
- A messaging task in the Flex UI with the contact’s phone number as the subject.
- The full AI-to-contact SMS transcript in the conversation thread.
- The handoff note above the transcript with summary, sentiment, and reason.
- The six
handoff*attributes on the task panel. - Any
flex_*custom data the workflow set during routing. - Replies typed in the Flex UI send as SMS to the contact’s number.
Channel-specific details
Opt-out keywords
Opt-out keywords
Twilio’s default opt-out keywords (
STOP, UNSUBSCRIBE, etc.) are handled upstream by your carrier — the OpenCX AI never sees a message from an opted-out number, and no Flex task is created.10DLC and toll-free rules still apply
10DLC and toll-free rules still apply
Flex SMS inherits the same or toll-free verification rules as any other Twilio SMS integration. OpenCX does not add or waive those — fix any registration issues with Twilio.
Session matching by phone number
Session matching by phone number
OpenCX matches an inbound SMS to an existing session by the contact’s phone number. A new number is a new session; an existing number continues the last session until it closes.
MMS behavior
MMS behavior
MMS attachments flow through to the Flex conversation as media attachments. Reps can view them inline and reply with their own attachments; MMS quotas and size limits follow your Twilio plan.
Related Documentation
AI SMS Support
The channel itself — numbers, routing, compliance.
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.