Action

You define an action in Dialogflow ES intents to tell your webhook which branch of the custom business logic it should execute.

Context

Contexts are used in Dialogflow ES to manage the state of the conversation as well as to guide the conversation along different paths even if the user says the same phrase. Dialogflow CX does not need/use contexts as it supports conversation state automatically There are two kinds of contexts in Dialogflow ES – input context…

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…

Follow up event

You can use follow up events in Dialogflow ES to trigger an intent from a webhook or from a REST API call. For example, it might be a good way to implement slot filling using webhooks. As you might imagine, this is a fairly complex feature and you need a programmer on your team to…

Follow up intent

You can use follow up intents in Dialogflow ES to chain intents together in a conversation. I recommend that people avoid using follow up intents and instead define their own input and output contexts to simulate the behavior of follow up intents. This makes your bot more flexible and will also help you debug issues…

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…

Parameter Default Value

In Dialogflow ES you can set the default value of a parameter. This can be especially helpful in situations where you wish the assign some value to a parameter but the value is not extracted from user utterance. For example, you might build a Quiz Bot and want to assign a score of 1 or…

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…