Dialogflow tutorial: How to move to the next intent?

Sometimes I see questions like these in the Dialogflow forum. So, I got one intent working. How can I now “move” the conversation to the next intent? Answer In Intent1, declare an output context called contextA. In the next intent you want to fire, use contextA as the input context. You have now chained Intent1 and Intent2 using contextA. Is that all? There is quite a bit more. But that’s the basic idea for every intent you are trying to chain into the conversation. A practical example I need to get three values from the user – their given name, their last name and their zip code. I will be using the naming convention I mentioned in my previous post….


Dialogflow Tip: Naming conventions for an intent which gets user input

Do you capture user input in your chatbot? For example, do you ask them to provide their name, or email, or other information? I have recently started using the following convention in the bots I am building (as well as advising on). The intent Suppose you have an intent which should get user’s email address. You can, of course, name it “EmailAddress”, but that isn’t very obvious. Obvious to whom, you might ask. Where you use it The key, of course, is where you use the intent name. One use for the intent name, for example, is in the test console. Looking at the intent name, you can tell what intent was just mapped. When you receive user input, you…


DialogFlow (API.AI) tutorial: Branching a conversation based on user input

I recently came across this question on the API.AI forum: Now, this can be a little ambiguous, so the forum member clears it up with a followup comment: Do you need a webhook? So, the first question is: do you absolutely need a webhook to solve this problem? Put another way, can you avoid using a webhook? If you frame the question as “How can I avoid using a webhook?” the answer becomes a bit clearer. Split the entity I have come to realize an interesting thing about API.AI – there is actually a tradeoff between the number of entities you are willing to create and the complexity of the eventual webhook code you will be writing. To put it…