Hero - Build your bot

Sometimes your bot will not understand what the user says. It is thus important that your solution contains a fallback flow that deals with user inputs that are not understood. In Teneo, we call this flow a Safetynet flow.

## Matches anything and is tested last
The Safetynet flow consists of a trigger with a star (__*__) and __%$_QUESTION__ as a language condition. The reason for this is that the Safetynet flow needs to be true for any input. To work as intended, Teneo must test all other triggers before falling back to the Safetynet trigger. The Safetynet trigger must thus be placed at the bottom of the trigger [ordering](/studio/conversations/concepts/ordering).   

![safetynet-script](//images.ctfassets.net/2vbtnveccz5s/7cZGpZG0y4RozcTd34GdvM/ee0fcda280b7af93daf08c13cf9c3378/safetynet-script.png?classes=w40)

## A flow like any other flow
Apart from having a very generous language condition, a Safetynet flow is like any other flow. It may be triggered when there is no other active flow in process, or in the middle of some other flow as in the following example:

>**User**: I'd like to order a coffee.       
>**Bot**: Ok, what coffee would you like?   

>**User**: ajkfhh  (*the coffee order flow is interrupted and the Safetynet is triggered*)    
>**Bot**:  I'm sorry but I didn't get that. (*Safetynet response is given*)

>**Bot**: Let's continue with your order. Which coffee would you like? (*the coffee order flow is resumed*)  

The same Safetynet flow may thus cater to non-understood inputs in all sorts of different contexts!

## Build a Safetynet flow
The Safetynet fallback flow is crucial for every solution. This flow can be built using the following steps.

!!! The [Dialogue Resources](/studio/language-understanding/concepts/languages#dialogue-resources) come with a pre-built Safetynet flow. You can find it in the 'Safetynet' folder. For solutions in languages without available Dialogue Resources, it is useful to add your own Safetynet flow using the following instructions and localizing to the language in question.

### Create a Safetynet order group
The Safetynet is always located at the bottom of the [order](/studio/conversations/concepts/ordering#order-groups) groups. This is because the Safetynet is built to trigger on every single input, catching the inputs that are not covered inside the solution. In order for the Safetynet to not steal any of the inputs, it is important to create an order group specifically for the Safetynet and place it at the lowest level.

!!! More on how to create your own custom order group can be found here: [Create a custom order group](/studio/conversations/how-to/create-a-custom-order-group#create-the-order-group).

### Create a Safetynet Flow
To begin with, create your flow by doing the following:

1. Click on the 'Flow' icon in the top ribbon.
2. Name the flow `Safetynet`.
3. Click the arrow in the top left corner of the window to go to the main flow window.

#### Create a TLML Syntax Match
As mentioned above, the Safetynet flow uses one [TLML Syntax Match](/studio/flows/concepts/triggers#condition). You can now go ahead and create that:

1. Select the trigger and name it `Safetynet`.
2. Scroll down to the 'Match' section and click on the 'Add' button. This will toggle a dropdown list of different Match requirements to select.
3. Select 'TLML Syntax' and then paste in the following condition: `* / %$_QUESTION`.
4. Lastly, change the ordering by locating the Triggering section and selecting the Order Group we created in the steps above, __Safetynet__. This will change the flows trigger ordering.

#### Add answer texts to the output
As the Safetynet fallback flow is one of the most triggered flows, it is important to add a wide range of answer texts inside the output node. 

Output nodes can contain multiple answer variations to make the conversation more dynamic. 

Teneo will choose any of these answers randomly and return it to the user. User has also the option to 'Set order' for the outputs to show.
1. Select the output node and paste in the following answers:
* `I'm sorry but I didn't get that.`
* `I'm not sure I know what you mean?`
* `Can you help me understand that?`
* `Can you say that again using different words?`
* `I didn't get that.`
* `I'm afraid I have no answer for you.`
* `I don't have a good answer to that.`
* `Sorry, can you rephrase that for me?`
* `I don't think I got that.`
2. Save the flow.

## Create an area Safetynet flow
An area Safetynet captures ambiguous inputs, but instead of giving a standard answer it recognizes what topic the user mentioned and tries to redirect the conversation towards that goal. 

For example, if a user mentions the word 'coffee' without any other context, the bot might respond like this:

> **User**: coffees       
> **Bot**: I understand you would like to talk about coffee. Can you be more specific? Did you want to order a coffee or see our selection of coffees?       
>       
> **User**: your selection       
> **Bot**: We offer a variety of handcrafted coffee drinks - from espressos to macchiatos to flat whites and more.       

A practical example of how to build an area Safetynet can be found [here](/studio/conversations/how-to/handle-ambiguous-inputs).

Build - Safetynet fallback flow

Sometimes your bot will not understand what the user says. It is thus important that your solution contains a fallback flow that deals with user inputs that are not understood. In Teneo, we call this flow a Safetynet flow.

## Matches anything and is tested last
The Safetynet flow consists of a trigger with a star (__*__) and __%$_QUESTION__ as a language condition. The reason for this is that the Safetynet flow needs to be true for any input. To work as intended, Teneo must test all other triggers before falling back to the Safetynet trigger. The Safetynet trigger must thus be placed at the bottom of the trigger [ordering](/studio/conversations/concepts/ordering).   

![safetynet-script](//images.ctfassets.net/2vbtnveccz5s/7cZGpZG0y4RozcTd34GdvM/ee0fcda280b7af93daf08c13cf9c3378/safetynet-script.png?classes=w40)

## A flow like any other flow
Apart from having a very generous language condition, a Safetynet flow is like any other flow. It may be triggered when there is no other active flow in process, or in the middle of some other flow as in the following example:

>**User**: I'd like to order a coffee.       
>**Bot**: Ok, what coffee would you like?   

>**User**: ajkfhh  (*the coffee order flow is interrupted and the Safetynet is triggered*)    
>**Bot**:  I'm sorry but I didn't get that. (*Safetynet response is given*)

>**Bot**: Let's continue with your order. Which coffee would you like? (*the coffee order flow is resumed*)  

The same Safetynet flow may thus cater to non-understood inputs in all sorts of different contexts!

## Activate in Tryout
You can trigger the Safetynet flow in Tryout by following these steps:

1. Click on the Tryout to start a conversation.
2. Write something nonsensical, like: `ajkfhh`.

![1-trigger-safetynet](//videos.ctfassets.net/2vbtnveccz5s/6jycyaOit1aNPa9ppLQ1TJ/670b33e75e2bfc2c5bd3971ef9b981d9/1-trigger-safetynet.mp4)

Studio Web - Build - Safetynet fallback flow

Safetynet

Safetynet fallback flow

Analyze your bot

Analyze Log Data

Analyzing sessions

Augmenters

Concepts

Extract values with Augmenters

How To

Metadata

Running custom queries

Counting coffees with Metadata

Reference

Teneo Query Language Cookbook

Teneo Query Language Reference Guide

Teneo Query Language Syntax Overview

Teneo Query Language

Data hierarchy

Event

Property

Session

Transaction

How to

Explore session statistics

Find stuck flows

Generate session logs

Locate and view a session

Make use of skip constraints

Make use of sub queries

Query variables

Troubleshoot the Safetynet

Use relative dates in queries

Query Syntax

Command

Constraint

Meta-parameter

Selection

Transformer

Build your bot

Bot design

Best practices

Data footprint

Encrypting user data in sessions

Flow checklist

Plan your bot

Starting a new Teneo project

Writing good answers

Writing good examples

Conversations

Context restrictions

Flow stack

Greeting message

Listeners

Ordering

Create a custom order group

Handle ambiguous inputs

Make your bot pro-active

Share information between flows

Use listeners

Flows

Bulk Import

Entities

Junctions

Outputs

Sub-Flows

Transitions

Intent triggers

Variables

Add a script to your flow

Branch at the beginning of a flow

Use TLML Syntax Match

Use a Sub-Flow

Use Bulk Import

Language Understanding

Annotations

Attached scripts

Language conditions

Language objects

Languages

Lexical resources

Libraries

Localization

Match requirements

Used words

Combine Match requirements

Create a solution in your language

Create your own language objects

Find language objects and entities

Localize a bot

Normalize the user's spelling

Optimize language conditions

Recognize plural and singular

Store what the user said

Advanced Condition Coding

Annotations Reference

Condition Syntax Reference

DateTime Handler Reference

DateTime Handler

Engine Scripting API Reference

Input Processing Path

Language Object Reference

Prebuilt Entities

Scripting

Engine scripting API

Groovy basics

Integration manager

Resource file manager

Scripts

Add a Groovy class

Add an integration

Add files to your solution

Annotate user inputs

Anonymize user data

Define a scripted context

Populate output parameters

Store input parameters

Test your bot

Run automated tests

Test your bot with Botium

Dialog Tester

Deploy your bot

Engine API

Versioning and Publishing

Publish your bot

Version Flags

Work with Version Flags

SDK's

Android

JavaScript

Node.js

Getting started

After Match

Extract Entities

Class Manager

Introduction to transitions

Introduction to entities

Deal with Follow-ups

Dialogue and Context Model

Getting started with Teneo

Handle interruptions

Skip conditions

Teneo in 10 minutes

Flows and match requirements

Entities and After Match

Your First Flow

Your First Solution

Optimize your bot

Optimize classes

Improve the balance

Review Inputs

Refine your bot

Debug your bot in Tryout

Use data to improve your bot

Use Teneo's improvement tips

Troubleshooting

My flow doesn't trigger

My flow behaves unexpectedly

I see warnings in Tryout

Suggestions

root

Table of Contents