Dialogflow CX scope helps you decide what set of actions CX can do based on the current state of the conversation. For example, only intent transition routes in the current page can fire (be invoked), and that’s because intent transition routes in the other pages are not in scope. For a more detailed discussion, check…
You can use the Simulator in both Dialogflow ES and Dialogflow CX to test your conversation without incurring any charges. Here is what the simulator looks like in Dialogflow ES: And this is what the Simulator looks like in Dialogflow CX: Given that Dialogflow CX is based on state machines, it provides a lot more…
Each flow in Dialogflow CX will have a Start Page. As the name suggests, this is the page which is always active in each flow.
A state machine is a concept from computer science which can be used to describe how Dialogflow CX works.
System functions in Dialogflow CX allows the user to add custom logic. In Dialogflow ES, this was only possible by using webhooks. This is yet another reason why CX is more powerful than ES.