User Input dependencies

Each user input is embedded in the conversation path. These paths together create a logic tree that describes what action could be performed at each stage of the path.

Dependency Rules

1. At the very beginning the system tries to match the user input with one of the primary User Inputs.

2. Children User Inputs have always preference to be matched.

3. If any of the children can’t be matched, the system searches available User Inputs within the reached interactions in the branch.

4. The system searches all previously reached User Inputs from all branches.

5. If any of the interaction can’t be matched, the bot will trigger Fallback interaction.

Good to know:

• Primary interactions can be matched from any party of the story.

• You can view the story structure to analyze its dependencies in the story view.

• If any of the interaction can’t be matched, the bot will trigger Fallback interaction.

Stories don’t need to be followed linearly. Users can return to interactions and jump to other primary branches. There are many ways to manipulate or limit the path. Read about filters.

Stories don’t need to be followed linearly. Users can return to interactions and jump to other primary branches. There are many ways to manipulate or limit the path. Read about filters.