When to use Dialogflow CX

I recommend reading my other article When to use Dialogflow ES first before reading this one.

If you are deciding between Dialogflow ES and Dialogflow CX, here are some rules of thumb you can use.

I recommend using Dialogflow CX in the following cases.

You need to build complex multi-turn conversations

If you use the slot filling and follow up intent features in Dialogflow ES, you will almost certainly benefit from migrating your bot to CX.

You are not building a large FAQ chatbot

While Dialogflow CX is suited for building large FAQ bots, I would say it is not necessary.

That’s because Dialogflow ES is usually sufficient for building such large FAQ bots which answer one off questions, and ES is more affordable.

You are not on a tight budget

Dialogflow CX allows you to build bots which are quite a bit more complex than ES. On the other hand, I would say CX is also quite pricey, especially in comparison with ES.

You don’t require automatic integration with external apps

If you are using Dialogflow ES, you have a lot more integrations with existing apps and external services simply because it has been around for much longer.

This situation will certainly change over time, but it is an important consideration at the moment.

However, you can usually build these integrations yourself by using Dialogflow’s REST API.

<— End of article —>

This website contains affiliate links. See the disclosure page for more details. 
"The magic key I needed as a non-programmer"

The custom payload generator was the magic key I needed (as a non-programmer) to build a good demo with rich responses in DialogFlow Messenger. I've only used it for 30 minutes and am thrilled. I've spent hours trying to figure out some of the intricacies of DialogFlow on my own. Over and over, I kept coming back to Aravind's tutorials available on-line. I trust the other functionalities I learn to use in the app will save me additional time and heartburn.

- Kathleen R
Cofounder, gathrHealth