Dialogflow CX Beginner Tutorial – 8/14: No state transition

Course outline

[m0] like I pointed out in the previous lesson there is an important distinction between the two intent intense called what is my balance.

And add a quarter.

And the difference is that the intent called what is my balance does not have any page transition at the end while the intent called add a quarter does have a page transition at the end.

And it goes to this thing called State 25.

Now, if you were to represent that on the state flow diagram that we had seen before this is what it will look like now for a moment I want you to imagine that instead of saying balance zeros.

And this is the start State effectively they are similar but there’s just a small few differences.

And that’s why I had to create a new state for that we will see that later but for now.

Let’s just pretend that that’s what it is.

And here this is how we represent action which [m1] effectively doesn’t change State.

So when the user is asking what is my balance you will have to do you will have to provide a response that is the agent does provide some type of response which we saw in the Fulfillment but it’s not changing state.

So the way you represent that in a flow diagram is just having an arrow which starts from a given State.

And then it just Loops back into the same state now is one more thing that I want you to notice right imagine if you had to cram all these possible actions corresponding to all these possible States into a single diagram you will notice very quickly that it becomes so dense so information dense that you can’t make sense of anything right so that’s one more balanced that Dialogflow CX has to achieve in its – you know – the state diagram [m2] representation.

And I just want you to remember that because it’s quite easy to look at the agents which are provided in the pre-built they actually provide a set of three build agents.

And you can go.

And take a look at some of these I will do that I think in the forthcoming videos.

And you just take a look at the flow.

And it all looks like really really complex but there is a reason for that because the more States.

And the more actions that you want to handle for each state which is the same as saying that the more things that you want the user to be able to say.

And be able to handle it properly in your Dialogflow bot the more complex your flow diagram becomes just automatically so dynaflow CX is an attempt to somewhat restrict.

And I guess you can say that visualize that information present that information in such a way that it strikes that balance [m3].

And you will notice that sometimes it does sometimes it’s probably not so great but ultimately that’s more reason it’s more result of the actual complexity of your bot then because the way the CX visualization Works in any case this is something that I want you to remember if you want to have if you want to picturise the flow where no transition happens if you want to picture is the action where no transition happens you will have to imagine the arrow which actually starts from a given State.

And then Loops back to the same state.

And then you might want to add the corresponding text on that Arrow