06 Translate the flowchart into Dialogflow ES agent

I made some updates to the flowchart from the last part

• added (Yes)(No) suggestion chips when bot asks a question (this is a Dialogflow Messenger bot)
• added an additional training phrase “Start Over” into intent 1
• changed the name of context 4

Let us translate the first intent – 1 identify.vertebrate

You copy the intent name, obviously.

Then check the input and output contextsContexts are used in Dialogflow ES to manage the state of th... More. This intent has no input contexts, and it has an output context called await_has_fur. The user training phrase will be “identify vertebrate” and the bot’s response will be “Does it have fur?”

This is how we define the intent

Let us translate intent 2 – hasfur.YES

This intent does have an input context – await_has_fur, but has no output context.

Here is the intent definition.

In the case of intent 3, we have both an input and an output context.

Here is the intent definition

You can do the same for the rest of the intentsBoth Dialogflow ES and Dialogflow CX have the concept of int... More and fully translate the flowchart into a Dialogflow agent.

Demo

Here is what the bot looks like in actionYou define an action in Dialogflow ES intents to tell your w... More

As you can see, if you are fairly rigorous about the flowchart definition, you can translate it into a Dialogflow ES agent pretty quickly.

About this website

I created this website to provide training and tools for non-programmers who are building Dialogflow chatbots. 

I have now changed my focus to Vertex AI Search, which I think is a natural evolution from chatbots. 

Note 

BotFlo was previously called MiningBusinessData. That is why you see that watermark in many of my previous videos.