Hero - Build your bot

In Teneo, we can use different kinds of [Match](/studio/flows/concepts/triggers#match-requirements) requirements in our flow triggers. We have already shown some [examples](/getting-started/build-a-slot-filling-flow) of different ones. Now we will show you how to create a conditional trigger.

Both triggers with TLML Syntax Match and those with Class Match can be built automatically from testing examples. The difference between the two is that with conditions, we have the ability to hand-tailor intent trigger using Teneo's [condition syntax](/studio/reference/condition-syntax) to either cover a broad use case or a very specific set of words and sentences.

We will now build a new flow for people that are interested in joining the Longberry Baristas' loyalty program, which will have a trigger with a [TLML Syntax Match](/studio/flows/concepts/triggers#condition) and allow dialogs like the following:

> **User:** How much does it cost to join the loyalty program?  
> **Bot:** You can join the loyalty program for free! Just ask your local barista for a club card and you're in!

The final result will look like this:

![flow layout](//images.ctfassets.net/2vbtnveccz5s/6E0TowK6VzgUSPyUnLIpvv/4240aa9535236842c06b7bc53e70bbdf/flow_layout.png)

## Create a new flow

Let's start by creating a new flow to cover this intent.

1.  Click on the 'Flow' icon in the top ribbon.
2.  Name the flow `User wants to know if loyalty program is free`.
3.  Click the arrow in the top left corner of the window to go to the main flow window.

![1-new flow](//videos.ctfassets.net/2vbtnveccz5s/3WoIutUseTYAnMy4kgscwJ/a44306c6f9745517f5c9038e605bf760/1-new_flow.mp4)

## Populate the trigger

The next step is to populate the trigger to cover the testing examples:

1.  Select the trigger and name it `Is the loyalty program free?`.
2.  Add a Intent trigger on the right and paste the following Intent examples into the field:

```example-inputs
Do I need to pay for the rewards program
How much does it cost to join the loyalty program
Is the rewards program free
What is the price of the loyalty program
```

![2-populate trigger](//videos.ctfassets.net/2vbtnveccz5s/35NhFK15J0l33BaRYekFms/cdd1ef90db46162fa71db10b46b8ce01/2-populate_trigger.mp4)

## Generate a condition
At this point we can either force Teneo to generate a Match or manually select one we are interested in. Let us start off by manually adding a [TLML Syntax Requirement](/studio/flows/concepts/triggers#condition) and automatically drafting a condition.

1.  Scroll down to the 'Match' section and click on the 'Add' button. This will toggle a drop-down list of different Match to select.
2.  Select 'TLML Syntax'(Teneo Linguistic Modeling Language) and then click on the 'Advanced Options' button under the condition field.
3.  Finally, click on the 'Draft' button. This will draft a condition based on the examples given to the trigger.  

!!! Selecting 'Draft' will replace any TLML Syntax condition written inside the Syntax condition panel from the first place.

4.  After a while, the following condition will appear:

![3-draft condition](//videos.ctfassets.net/2vbtnveccz5s/2lXumNmHXRYFCmiy8fM4Je/6933a7703bd7593e643f2a20f9bdda1e/3-draft_condition.mp4)

Here, we can see that Teneo used the [Intent examples](/article/build/flows/how-to/use-conditional-match-requirements#populate-the-trigger) to find matching [language objects](/studio/language-understanding/concepts/language-objects) and combine them in a language condition. This is human-readable and, if we understand the syntax, it can be fine-tuned to suit our needs. For now, we will just use the condition as is; later, we will see [how to further optimize this language condition](/studio/language-understanding/how-to/optimize-language-conditions) in order to shorten and increase the coverage of a Syntax condition.

!!! If you are developing using a language without any [Language Resources](/studio/language-understanding/concepts/lexical-resources), Teneo will generate a condition using plain words instead of [Language Objects](/studio/language-understanding/concepts/language-objects).

## Add an answer

To finish the flow, we need to add an answer text to the output.

1.  Select the Output Node and name it `You can join the loyalty program for free!`.
2.  Paste `You can join the loyalty program for free! Just ask your local barista for a club card and you're in!` into the 'Answers' field on the right.
3.  Hit 'Save'.

![4-add answer](//videos.ctfassets.net/2vbtnveccz5s/7Aqjrpf500yyCoIeZo9JIO/bedaba032b0b41cc3cb2403e36937040/4-add_answer.mp4)

That's it! We now have a flow that includes a trigger with a TLML Syntax Match.

## Test yourself

Go ahead and test yourself by adding one more example, `Can I join the loyalty program without paying?` and draft the condition again following the steps from this page.


Build - Use TLML Syntax Match

In Teneo, we can use different kinds of [Match](/studio/flows/concepts/triggers#match-requirements) requirements in our flow triggers. We have already shown some [examples](/getting-started/build-a-slot-filling-flow) of different ones. Now we will show you how to create a TLML Syntax trigger.

Both triggers with TLML Syntax Match and those with Class Match can be built automatically from testing examples. The difference between the two is that with conditions, we have the ability to hand-tailor intent trigger using Teneo's [Syntax Condition](/studio/reference/condition-syntax) to either cover a broad use case or a very specific set of words and sentences.

We will now build a new flow for people that are interested in joining the Longberry Baristas' loyalty program, which will have a trigger with a [TLML Syntax Match](/studio/flows/concepts/triggers#condition) and allow dialogs like the following:

> **User:** How much does it cost to join the loyalty program?  
> **Bot:** You can join the loyalty program for free! Just ask your local barista for a club card and you're in!

The final result will look like this:

![finale](//images.ctfassets.net/2vbtnveccz5s/7tyQFZ8QpwQ71iDTSBIXNq/7dfb987c36f36d55a6226c40d8948d72/finale.PNG)

## Create a new flow

Let's start by creating a new flow to cover this intent.

1.  Click on the 'Flow' icon in the top ribbon.
2.  Name the flow `User wants to know if loyalty program is free`.

![1-create-flow](//videos.ctfassets.net/2vbtnveccz5s/k6XHUHFMKfHuOMeX2mprZ/3300f0e6d87f9b23ae4745c6ea7dbaef/1-create-flow.mp4)

## Populate the trigger
The next step is to populate the trigger to cover the testing examples:

1. Navigate to the trigger and name it `Is the loyalty program free?`.
2. Click on 'edit' and paste the following Intent examples into the field:
* `Do I need to pay for the rewards program`
* `How much does it cost to join the loyalty program`
* `Is the rewards program free`
* `What is the price of the loyalty program`

![2-add-examples](//videos.ctfassets.net/2vbtnveccz5s/59E97QiJQNI29Z7w1TTvar/773c4a80fab62f6589725c17dbe1f718/2-add-examples.mp4)

## Create a TLML condition
At this point we can either force Teneo to generate a Match or manually select one we are interested in. Let us start off by manually adding a [TLML Syntax Requirement](/studio/flows/concepts/triggers#condition) and automatically drafting a condition.

1.  Scroll down to the 'Match' section and click on the 'Add' button. This will toggle a drop-down list of different Match to select.
2.  Select 'TLML Syntax'(Teneo Linguistic Modeling Language) and paste in the following condition

```tlml
(%WHAT_IS_THE_PRICE_OF.PHR &^ %LOYALTY_PROGRAM.NN.SYN)
	/
(%REWARD.NN.LEX &^ %PROGRAM.NN.LEX &^ %FREE.ADJ.LEX)
	/
(%SHOULD_I.PHR &^ %PAY_FOR.VB.MUL &^ %REWARD.NN.LEX &^ %PROGRAM.NN.LEX)
```

!!! You can use the function to 'Draft' a TLML Syntax condition in Studio Desktop. 

![3-add-condition](//videos.ctfassets.net/2vbtnveccz5s/1xmLzbKabtQOZi18pp9RUY/383d82e80009d92587a29cb138dc7168/3-add-condition.mp4)

Here, we can see that Teneo used the [Intent examples](/article/build/flows/how-to/use-conditional-match-requirements#populate-the-trigger) to find matching [language objects](/studio/language-understanding/concepts/language-objects) and combine them in a language condition. This is human-readable and, if we understand the syntax, it can be fine-tuned to suit our needs. For now, we will just use the condition as is; later, we will see [how to further optimize this language condition](/studio/language-understanding/how-to/optimize-language-conditions) in order to shorten and increase the coverage of a Syntax condition.

!!! If you are developing using a language without any [Language Resources](/studio/language-understanding/concepts/lexical-resources), Teneo will generate a condition using plain words instead of [Language Objects](/studio/language-understanding/concepts/language-objects).

## Add an answer

To finish the flow, we need to add an answer text to the output.

1. Navigate to the Output node and name it `You can join the loyalty program for free!`.
2. Click on 'Edit' and paste in the following answer `You can join the loyalty program for free! Just ask your local barista for a club card and you're in!`.
3. Hit 'Save'.

![4-save-flow](//videos.ctfassets.net/2vbtnveccz5s/ZpJdqIPyFrL8A0qtR1PnV/78978970db79d3664ce44ceee57ac340/4-save-flow.mp4)

That's it! We now have a flow that includes a trigger with a TLML Syntax Match.

## Test yourself

Go ahead and test yourself by adding one more example, `Can I join the loyalty program without paying?` and draft the condition again following the steps from this page.


Studio Web - Build - Use TLML Syntax Match

Use TLML Syntax Match

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

Safetynet

Trigger 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 a Sub-Flow

Use Bulk Import

Language Understanding

Annotations

Attached scripts

Language conditions

Language objects

Languages

Lexical resources

Libraries

Linguistic Modeling Language

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

Engine Scripting API Reference

Input Processing Path

Language Object Reference

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