Dialogflow CX vs ES: separate flow
Posted: Thu Mar 27, 2025 10:51 am
It allows modularization of bot for ease of management. It provides separate teams with the ability to work on independent flows using the same bot. With flows, you can partition your agent into smaller conversation topics. Different team members can own different flows, which makes broad and complex agents easy to build. Also, it supports versioning, and you’ll have the ability to run A/B experiments and split traffic.
For example, a car rental agent may have a pickup location, confirm location, drop off location, etc. as distinct topics. Each topic requires multiple conversational turns for an agent to acquire the relevant information from the end-user.
Now that we have explored the newest physician data features of Dialogflow CX, let’s dive into the comparison between Dialogflow CX vs ES.
Comparison between Dialogflow CX vs ES
Intents
An intent categorizes the end-users intention for one conversation turn. For each agent, you define many intents, where your combined intents can handle a complete conversation.
The Dialogflow CX and ES version use intents, however in the Dialogflow CX version, it has been simplified to make it reusable. And intent is not used together with context to control conversation flow. Instead, it works with pages to navigate/route through the conversations.
Conversation control
Dialogflow ES used context to determine the control of the conversation flow. In Dialogflow CX, you can use the page to manage the states of a conversation session. You can use the page to collect information from the end-user related to the state designed on the page.
For example, a car rental agent may have a pickup location, confirm location, drop off location, etc. as distinct topics. Each topic requires multiple conversational turns for an agent to acquire the relevant information from the end-user.
Now that we have explored the newest physician data features of Dialogflow CX, let’s dive into the comparison between Dialogflow CX vs ES.
Comparison between Dialogflow CX vs ES
Intents
An intent categorizes the end-users intention for one conversation turn. For each agent, you define many intents, where your combined intents can handle a complete conversation.
The Dialogflow CX and ES version use intents, however in the Dialogflow CX version, it has been simplified to make it reusable. And intent is not used together with context to control conversation flow. Instead, it works with pages to navigate/route through the conversations.
Conversation control
Dialogflow ES used context to determine the control of the conversation flow. In Dialogflow CX, you can use the page to manage the states of a conversation session. You can use the page to collect information from the end-user related to the state designed on the page.