This Twilio product is currently available as a Beta release. Some features are not yet implemented and others may be changed before the product is declared as Generally Available. Use of this Beta release is subject to the relevant terms of the applicable license agreement. Beta products are not covered by a Twilio SLA. Learn more about beta product support.
Flex Conversations requires Flex UI 2.0. If you are on Flex UI 1.x, please refer to Chat and Messaging pages.
Flex Conversations requires Flex UI 2.0 and supports async channels including:
It uses Twilio Conversations and the Interactions API for managing inbound and outbound communication on your contact center. The following diagram illustrates how the various Twilio products connect together to make Flex Conversations possible.
Flex uses Twilio Conversations for all digital channels and provides the unique threads in which messages are exchanged between agents and customers. Each Conversation includes a list of current Participants and the Messages that they have sent amongst each other.
Messaging Services serve as a higher-level “bundling” of messaging functionality around a common set of senders, features, and configuration. The same settings and feature configuration apply to all of the senders (long code numbers, short codes, toll-free numbers, A2P 10DLC, etc.) in the Messaging Service’s pool.
A Conversations Address is a configuration for your Flex SMS or WhatsApp number that informs the Conversations Service to auto-create a new conversation for messages that do not belong to an existing conversation. You can configure your address to point to a Studio Flow or a webhook on your application for sending. Once a conversation is created, all new messages from the same source to the same destination will be routed to the newly created conversation.
For more information on handling inbound messages and enabling auto-creation for Conversations, see Inbound Message Handling & Autocreation.
The Interactions API allows you to manage the communication between end-customer and the business. It provides the primitives to connect and orchestrate adding and removing of participants in a given channel and utilizes Twilio TaskRouter for all contact center routing capabilities.
Interactions Object Model
An interaction channel gives you the ability to associate multiple tasks with the same conversation. With this model, you can build workflows which allow the conversation to stay open beyond the lifetime of a task. This facilitates use cases like transfer and preserving conversation history across tasks.
Flex Conversations supports Chat applications built on top of Twilio Conversations. These include:
- Mobile In-App chat
- Web-based Chat. See our WebChat React demo app as an example for starting with Chat
With Custom Chat, you can provide authenticated access to your users or build an anonymous webchat to embed into your website.
Twilio takes data security seriously. All customer assets—including text, media, and most metadata—are encrypted at rest. We also encrypt all data at the volume level.
Twilio's servers and Flex communicate using secure WebSockets. The Flex agent desktop connections are authenticated using the same JWT token security as the rest of Flex, meaning they are governed by the same Single Sign On (SSO).
To learn more about Conversations in Flex, check out the following topics: