Core Concepts: Conversations

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.x.x and supports async channels including:

  • WhatsApp
  • Chat
  • Facebook Messenger (Public Beta)
  • Google Business Messages (Public Beta)

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.

Conversations Core Concept.png

Twilio Conversations and Messaging Services

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.

You can manage your Messaging Services directly through the Console or through the REST API.

Conversations Address

A Conversations Address is a configuration for your Flex SMS or WhatsApp number, Facebook Messenger Sender, or Google Business Messages Sender. The address 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.

Interactions API

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

Interactions Object Model

Interaction Channels

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.


Webchat 3.0 is built on Flex Conversations and provides a simple, secure way to add a webchat widget to your website.

Flex Conversations also supports Chat applications built on top of Twilio Conversations, including mobile in-app chat. With custom chat, you can provide authenticated access to your users or build an anonymous webchat to embed into your website.

Chat Encryption

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).

Next Steps

To learn more about Conversations in Flex, check out the following topics:

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Thank you for your feedback!

Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

Sending your feedback...
🎉 Thank you for your feedback!
Something went wrong. Please try again.

Thanks for your feedback!