Context

ChatBot gives you the full control over your bot responses and actions.

A story is a set of actions & interactions bonded together into a logical tree structure. The position in that tree defines when the interaction’s priority and availability. While the bot traverses the scenario, different bot answers become available.

The current position of the bot defines its possibilities and options called context. The context changes every time the bot moves along the story and opens newly possible interactions as well as closes the previous ones.

How does the context work

When you’re testing your story in the Testing Tool, triggered interactions are automatically highlighted what can help you to understand what exactly happens in your story.

In the above example we’ve got five different paths, A, B and C.

• A and C are root user inputs

• B is a child user input

So let’s try how it work in our Testing Tool.

1. We’ve tried to trigger User Input B but our user is not in this context and that’s why Fallback was triggered.

2. We’ve triggered A path firstly and then B path. It ended with success because after triggering A path, the user has access to a B context.

3. We’ve trigger A or C path at the beginning. As you can see the user has access to these interactions at the start. These User Intents are called roots.

Conclusion:

• The root user inputs A and C can always be reached from any point of the story.

• When A is currently triggered, the bot can match B user input.

What do we need the context for

The context gives us the control over what happens to the story. It defines the conversation flow and the next steps of the chat. You can decide what happens in every part of the story. Additionally, you can use the context fallback triggered when the query cannot be matched.