Skip to main content

Best Practices

📄️ Flow checklist

Teneo makes it easy to start creating new Flows as soon as you've created your environment. Before you get started, however, it is best to plan ahead in order to make it easier to manage larger projects as they continue to expand. Standardizing everything from naming conventions to the quality and quantity of trigger example inputs will help ensure the highest possible quality of a solution, making it not only effective, but also easy to understand and troubleshoot. As there are a lot of things to keep in mind when designing Flows, we have compiled the following checklist which can be used to quickly verify that your newly built Flow meets the highest standard.

📄️ Writing good answers

No matter how well designed the rest of your solution is, your bot will not be any good if the answers returned to the end user make no sense or are poorly phrased. The answers that a bot gives to user input are defined in the output nodes of a Teneo solution. The quality and style of these answers have a massive impact on how an end user perceives the final bot, and therefore need to be planned carefully. The style of the answers, e.g. the tone of voice, should also reflect the company that the bot represents; Teneo therefore makes it simple to tailor such design choices to different companies. On this page, we will go through our recommendations on how to write the best possible answers for your solution.