This is a chapter summary from my Intro to Dialogflow course.
In this chapter, I explain how to build a yes/no branching bot. The webhook diagnostics bot is an example of a yes/no branching bot.
Here the chatbot guides the user through a series of yes or no questions and then provides an answer at the final step. In the example covered, I walk you through creating a chatbot which asks some yes/no questions to determine if the bot user has the prerequisites set up to install a custom chatbot on their PHP based site.
In the first lesson, I explain what we will be building:
Then we define the chatbot by using follow up intents first:
In the next lesson, I explain the challenges with using follow up intents.
And the final lesson discusses how to build the bot without using follow up intents.
You might be wondering what is the advantage of avoiding followup intents?
Sometimes, you need more fine grained control of your chatbot converstion. For example, in the YouTube video below, I show how to re-prompt the user for input from a fallback intent, but also keep control of the conversation.
When you use follow up intents, it can be challenging to have such fine grained control over your chatbot.
- Reader Question: What if a specific system entity isn’t available in all languages in a multi-lingual bot?
- How much can Machine Learning ACTUALLY help with answering free-form questions?
- Dialogflow Toolkit vs MBD Membership
- Dialogflow Knowledge Connector : Pros and Cons
- How to integrate Telegram with Dialogflow
- Why I avoid using slot filling (required parameters) in Dialogflow
- Free Tool: Convert your WordPress website into a Dialogflow FAQ chatbot
- Dialogflow Mega Agent Tutorial
- Reader Question: Will followup events work when an intent has an input context?
- How to learn Dialogflow in a week