Dialogflow ES vs Dialogflow CX: Feature comparison
In the table below I provide feature-by-feature comparison between Dialogflow ES and Dialogflow CX.
| Feature | Dialogflow ES | Dialogflow CX |
| Conversation Design | Use input and output contexts | Use pages, routes and flows |
| Collect a list of inputs from user | Use follow up intents or mimic follow up intents | Use pages and intent transition routes |
| Store user input | Use contexts | Use built-in session params |
| Slot filling | Basic and unpredictable | Powerful and robust |
| Supports explicit contexts | Yes | No |
| Webhooks | One endpoint per agent | One endpoint per transition route is possible |
| Support for list entity | Yes | Yes |
| Support for composite entity | Yes | Yes |
| Supports Regex entity | Yes | Yes |
| History feature | Yes | Not yet |
| Training feature | Yes | Not yet |
| Agent Versioning | Basic | Powerful |
| Free tier | Generous free tier | No, but provides free trial credits |
| Built in integrations | Many 1-click integrations are supported, including many third party apps | Limited support for 1-click integrations |
| Supports Test cases | No | Yes |
| Support for system functions | No | Yes |
| Supports conditional logic inside console | No | Yes |
| Exception handling when conversation goes off track | Hard, needs a good understanding of the CTFS framework | Very robust, possibly best among all chatbot frameworks |
| Supports Knowledge Base | Yes | No (use route groups instead) |
| Build a large bot with a lot of intents | Use the Mega Agent feature (less robust) | Use Flows (more robust) |
Last updated: 3 June 2022