Bot Testing

overview the bot testing feature is a critical quality assurance tool within the workflow module that helps you ensure the reliability and accuracy of your chatbot's conversational abilities its primary purpose is to automatically check for "intent clashes"—scenarios where a user's query could mistakenly trigger the wrong conversation flow because two or more intents have overly similar training phrases by simulating user inputs, this tool analyzes the content you've uploaded to the chatbot and identifies potential conflicts that could negatively impact the user experience it allows you to proactively find and fix issues where the bot might get confused between, for example, a user asking for their "account balance" versus their "last account statement " the feature provides flexibility by allowing you to test individual intents, select groups of top intents for faster checks, and filter the tests based on the last modification date the results are presented in a clear report that can be exported via email for further analysis how to use bot testing this guide explains the process of using the bot testing tool to validate your chatbot's intents 1 navigating to the feature from the main console menu, navigate to workflow click on the bot testing tab in the secondary navigation bar 2 configuring and running a test the bot testing interface will allow you to configure the test parameters select intents to test you can choose how to run the test test individual intents select one or more specific intents from a list to check for clashes among a small, targeted group test top intents choose this option for a faster test that focuses on the most frequently used or recently modified intents start the test once you have selected the intents, click the "start testing" or a similar button to initiate the process the system will begin analyzing the training phrases for the selected intents to identify potential overlaps (optional) stop test you have the option to stop a test in progress if needed 3 reviewing results and taking action after the test is complete, the results will be displayed on the screen, highlighting any intents that are found to be clashing the report will show which intents are in conflict and provide insights into why they are clashing (e g , similar keywords or phrasing) export report you can choose to have the detailed test report exported to your email for offline review and record keeping fixing clashes based on the report, navigate back to the flows tab, open the conflicting intents, and edit their training questions to be more distinct and specific common examples and use cases post content upload after you have created several new flows or used "extract web faqs" to add dozens of intents, run a bot test to ensure the new content doesn't conflict with existing flows debugging user issues a user reports that when they ask "how do i apply for a loan?", the bot sometimes provides information about checking loan status running a bot test on the "apply for loan" and "check loan status" intents can quickly identify the source of this confusion pre deployment sanity check before publishing your changes from the development environment to production, running a comprehensive bot test is a crucial final step to catch any regressions or new conflicts best practices test iteratively don't wait until you've built the entire bot to run a test test small, related groups of intents as you build them this makes it much easier to find and fix clashes make training phrases distinct if a clash is detected, the best solution is to make the training phrases for the conflicting intents more unique add context specific keywords to differentiate them use the "last modified" filter regularly test the intents that have been recently changed this ensures that recent edits haven't unintentionally created new problems with older, stable intents regularly audit your bot schedule a full bot test periodically (e g , once a month) to maintain the overall health and accuracy of your chatbot as it evolves common mistakes never testing building a bot with hundreds of intents without ever running a clash test is a primary cause of poor and unpredictable bot performance ignoring test results running a test and seeing the clash warnings but not taking action to resolve them the tool is only effective if its results are used to improve the bot creating vague intents building intents with very generic, single word training phrases (like "help," "info," or "details") is a guaranteed way to create clashes with more specific intents