Hero - Build your bot

[Listeners](/studio/conversations/concepts/listeners) can be used in multiple ways in Teneo. For this example, we will demonstrate one way of using a listener inside a flow. In the previous page on how to [handle ambigous inputs](/studio/conversations/how-to/create-a-custom-order-group#create-a-flow-for-partial-understanding), we demonstrated a way to handle partial understanding and catch keywords. Adding on to that, we will now add a [listener](/studio/conversations/concepts/listeners) to recognize if a coffee type is mentioned and the user wants to order it. 

Before our changes, we would have a conversation like this:

> **User:** espresso    
> **Bot:** You're talking about coffee. Would you please tell me what you wanted exactly? Did you want to order a coffee or see our selection coffees?  
> 
> **User:** order    
> **Bot:** Ok, what coffee would you like?     

After our modifications, it will look like this:

> **User:** espresso    
> **Bot:** You're talking about coffee. Would you please tell me what you wanted exactly? Did you want to order a coffee or see our selection coffees?  
> 
> **User:** order    
> **Bot:** Ok, a **espresso** will be ready for pickup in 5 minutes.     

To achieve this we need to do the following: 
* Create a [flow variable](/studio/flows/concepts/variables#flow-variable).
* Add a [flow listener](/studio/conversations/concepts/listeners#flow-listener).
* Modify the flow link to include the mentioned coffee type.

## Create a flow variable
Let us start off by opening the [Partial Understanding: Coffee](/studio/conversations/how-to/create-a-custom-order-group#create-a-flow-for-partial-understanding) flow and creating a new flow variable to store the coffee type mentioned by the user. 
1. Open the [Partial Understanding: Coffee](/studio/conversations/how-to/create-a-custom-order-group#create-a-flow-for-partial-understanding) flow in edit mode.
2. While inside the flow, navigate to 'Flow' tab located.
3. Click on 'Variables' add a new variable that has the name `coffeeType` and the value `""`.    

![1-add var](//videos.ctfassets.net/2vbtnveccz5s/5HMawvnD1NfV9jw5P8DR4v/0eb1380c27b9b7d4e101cf012e4f99ec/1-add_var.mp4)

## Create a flow listener
Now it is time to add a flow listener to listen for the coffee type. We will also use the previously created [COFFEES_SERVED.ENTITY](/getting-started/create-custom-entities#create-a-coffees-served-entity) for the condition.
1. While inside the 'Variables' section, switch over to 'Listeners'. 
2. Click on the 'Add' button. This will open up a new flow listener.
3. Name the listener `Listen for coffee types`.
4. In the TLML Syntax field, paste in the following: `%COFFEES_SERVED.ENTITY^{coffeeType = lob.coffeeType}`.
5. Click on 'Ok'.
6. Click on the back arrow in the menu to return to the Home tab of the flow.

![2-add listener](//videos.ctfassets.net/2vbtnveccz5s/644QPRW2tEqWcmH6Y9EyNw/657297b8eee10606b771e12c605c69b0/2-add_listener.mp4)

!!! This can also be done by adding an [Entity Match](/studio/flows/concepts/triggers#match-requirements) to the intent trigger.

## Modify the flow link
The next step is to modify the flow link to send over the flow variable that stores the mentioned coffee type to the 'User wants to order a coffee' flow. 
1. While inside the flow, select the flow node 'User wants to order a coffee'. 
2. Navigate to the 'Target' section and select the drop-down menu right beside 'orderedCoffeeType'.
3. From the drop-down menu, select the previously created flow variable 'coffeeType'. This will send the value from this flow variable to the 'orderedCoffeeType' flow variable inside 'User wants to order a coffee'.
4. Save the flow.

![3-modify flow](//videos.ctfassets.net/2vbtnveccz5s/17kDrCDOuN5qbIau30OtfU/2cebb894d2f72a4e5d9a49439634781b/3-modify_flow.mp4)

## Try it out
Let's go ahead and test the modified flow by mentioning a coffee type:    
> **User:** `espresso`    
> **Bot:** You're talking about coffee. Would you please tell me what you wanted exactly? Did you want to order a coffee or see our selection coffees?  
> 
> **User:** `order`    
> **Bot:** Ok, a **espresso** will be ready for pickup in 5 minutes.     


Build - Use Listeners

[Listeners](/studio/conversations/concepts/listeners) can be used in multiple ways in Teneo. For this example, we will demonstrate one way of using a listener inside a flow. In the previous page on how to [use TLML Syntax Match](/article/build/flows/how-to/use-conditional-match-requirements), we demonstrated a way to use TLML Syntax to add users to our loyalty program. Adding on to that, we will now add a [listener](/studio/conversations/concepts/listeners) to recognize if an email is mentioned and register the user to the rewards program.

Before our changes, we would have a conversation like this:

> **User:** Do I have to pay for the reward program? My email is test@teneo.com        
> **Bot:** You can join the loyalty program for free! Just ask your local barista for a club card and you're in!    

After our modifications, it will look like this:

> **User:** Do I have to pay for the reward program? My email is test@teneo.com      
> **Bot:** Thank you for showing interest to our loyalty program, we will send out a confirmation of your registration to test@teneo.com!     

To achieve this we need to do the following: 
* Create a [flow variable](/studio/flows/concepts/variables#flow-variable).
* Add a [flow listener](/studio/conversations/concepts/listeners#flow-listener).
* Split the path and recognize the mentioned email in a new output.

## Create a flow variable
Let us start off by opening the [User wants to know if loyalty program is free](/article/build/flows/how-to/use-conditional-match-requirements) flow and creating a new flow variable to store the coffee type mentioned by the user. 
1. Open the [User wants to know if loyalty program is free](/article/build/flows/how-to/use-conditional-match-requirements) flow.
2. While inside the flow, click on the variable icon below the Flow Overview.
3. Add a new variable that has the name `email` and the value `""`. 
4. Click on 'Confirm' to save the variable.   

![1-use-listeners-1](//videos.ctfassets.net/2vbtnveccz5s/4twReIGO3ORVYVoiSvgCi9/01e188a85c9f2d747446451ff502f385/1-use-listeners-1.mp4)

## Create a flow listener
Now it is time to add a flow listener to listen for the coffee type. We will also use the __EMAIL.ENTITY__ for the TLML Syntax condition.
1. Switch over to listeners, by clicking on the 'Listener' icon.
2. Click on the 'Add' button. This will open up a new flow listener.
3. Name the listener `Email entered`.
4. In the TLML field, paste in the following: `%EMAIL.ENTITY^{email = _USED_WORDS}`.
5. Click on 'Confirm'.

![2-use-listeners](//videos.ctfassets.net/2vbtnveccz5s/3hlUoaYtBCSYDmAzSiTpkW/321dc1ff27fefac0083af60913026309/2-use-listeners.mp4)

!!! This can also be done by adding an [Entity Match](/studio/flows/concepts/triggers#match-requirements) to the intent trigger.

## Split the path
The next step is to modify the flow structure by creating a new path for when an email is mentioned by the user. 

1. Navigate to the Plus icon above the output node. Followed up with 'Split Path' and 'Transaction Element', 'Output'. This will add an [Junction](/article/build/flows/concepts/junctions) before the two paths.
2. Go to the new transaction an click on the Plus icon above the output node. 
3. Click on 'Match' followed up with 'Flow Variable'. From the dropdown menu, make sure 'email' is selected (this should be default).

![3-use-listeners](//videos.ctfassets.net/2vbtnveccz5s/3QRVqEL2ZK1Pnr3AbAJmuG/bb3808a825de9d914f735360e275a9d4/3-use-listeners.mp4)

## Modify the new Output
As a last step, we need to finish the flow by modifying the newly added Output node. 

1. Navigate to the output node and name it: `User registered to loyalty program`
2. Add the following answer: `Thank you for showing interest to our loyalty program, we will send out a confirmation of your registration to ${email}!`.
3. Finally, go ahead and click on 'Save'.

![4-use-listeners-save](//videos.ctfassets.net/2vbtnveccz5s/7xW4YQmlfwGwpRu2ZeJPZy/2ab94f1161b7f442742907fa5ca55b30/4-use-listeners-save.mp4)

## Try it out
Let's go ahead and test the modified flow by mentioning a email:    
> **User:** `Do I have to pay for the reward program? My email is test@teneo.com`      
> **Bot:** Thank you for showing interest to our loyalty program, we will send out a confirmation of your registration to test@teneo.com!     

![4-use-listeners](//videos.ctfassets.net/2vbtnveccz5s/3m4THUqzaWXuyhvcRbKVqi/bb850ee50f2fb3e3fabc5fae4f2b2a32/4-use-listeners.mp4)


Studio Web - Build - Use Listeners

Use listeners

Use Listeners

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

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

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