Default Start Flow
The Default Start Flow is created automatically when you first create a new Dialogflow CX agent.
Default Welcome Intent
This is the intent which is automatically added into the Start page of your Dialogflow CX chatbot.
Entity
Both Dialogflow ES and Dialogflow CX support entities and they also behave similarly. An entity represents a predefined categoy of objects and the basic idea is borrowed from the field of Natural Language Processing. Named entity recognition (NER)—also called entity chunking or entity extraction—is a component of natural language processing (NLP) that identifies predefined categories…
Event
Events are used in both Dialogflow ES and Dialogflow CX as triggers – they trigger something like an intent or an intent transition route – which fire without any user utterance. The best example is the WELCOME event in ES which has a very specific role – it will automatically fire the intent which contains…
Intent
Both Dialogflow ES and Dialogflow CX have the concept of intents, but they don’t have the same behavior. An intent represents what the user wants. “Switch on the lights” “Order a pizza” etc. In the case of Dialogflow ES, the bot’s response is added into the intent itself. But in Dialogflow CX, an intent only…
Parameter
Both ES and CX support the concept of parameters. If entities are the categories or types of proper nouns, parameters are the actual values. For example, “city” would be an entity type, and Dallas would be the parameter (entity value). Dialogflow ES and CX allow you to extract parameter values from a user utterance. For…
Scope
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…
Simulator
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…
Start Page
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.
State machine
A state machine is a concept from computer science which can be used to describe how Dialogflow CX works.
System functions
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.
Utterance
An utterance is simply what the user says to the bot. Both ES and CX uses the phrase “training phrases” to specify user utterances. Here is what it looks like in ES: