Output nodes are flow nodes that specify how the bot should respond. Most importantly they contain the answer texts, but they also let you specify various properties which are outlined below.
Answer texts are specified in the 'Answers' panel. You may add several answer texts that are phrased slightly differently to your output node. That way your bot won't sound repetitive if a user runs into the same output node more than once. If you define more than one answer text, you can specify whether the bot should pick one at random, or in the order provided. To do this, use the toggle 'Order random'/ 'Use current Order'. Teneo will use the answer marked as 'Fallback' if all answer texts in the output have already been given once.
Revisitability has to do with interruptions, for example situations where your bot has asked a question to the user and the user responds with a request for clarification, switches topic, or simply responds in a way that is not understood. In short: if you want your output node to survive such an interruption you make it revisitable. Otherwise, you make it non-revisitable.
If a flow is interrupted after a revisitable output node, your bot will return to that point of the flow when the interruption is completed.
If a flow is interrupted after a non-revisitable output node, your bot will simply drop the flow. You can thus think of non-revisitable output nodes as optional end nodes, or exit points. They even have the same appearance as end nodes: they have a purple border.
You specify revisitability with a toggle in the 'Answers' panel. Here you can also limit how many times you allow the output to be revisited. If the limit is exceeded, the flow is dropped.
If you add a resume prompt to an output node, that prompt will be given instead of the ordinary answer texts when the node is revisted after an interruption. You add resume prompts in the 'Resume Prompts' panel.
With skip conditions you may specify when an output node should be skipped. They are used to avoid redundant questions for information that is already known. For example, if a user says: I would like a strawberry ice cream please, you want your bot to skip the question Ok, what flavor would you like?.
You add skip conditions to your output node under its 'Skip conditions' panel. There you specify when it should be skipped (e.g. if the variable for flavor has already been set), and where it should skip to, i.e. which transition to follow after the output has been skipped. More on setting skip conditions here.
Output parameters can be used to provide your app with information that has no place in the regular answer text. For example, suppose a bot can provide weather information in a mobile app. The answer text of an output might contain a humanlike description of the weather (It's quite sunny in Amsterdam at the moment, make sure to wear sunscreen!). But in addition to that, the app could display a widget with more detailed weather info. The information that needs to be displayed in the widget could be passed on as JSON in an output parameter. Each output node can have as many output parameters as you like, each parameter needs to have a name and a String as value.
Each output node has a separate URL field. This URL is included as a separate field in your bot's response. The frontend application can use this field to for example automatically open a webpage. The same is true for 'emotions': each answer text can have an emotion associated with it. This emotion is included as a separate field in your bot's response and can for example be used by frontends that display avatars.
For more technical details on how applications can connect to your bot and Teneo's response format, please refer to Connect to your bot.
Was this page helpful?