Category

overview the categories feature is an organizational tool within the exo chatbot platform designed to help you manage and structure your conversation flows (intents) as a chatbot grows in complexity with dozens or even hundreds of flows, it can become difficult to locate and manage specific user journeys categories allow you to group related flows into logical, user defined buckets for example, you could create categories for "sales queries," "technical support," "account management," and "general faqs " by assigning each flow to a relevant category, you create a clean, organized, and easily navigable structure this makes the bot development process more efficient, especially for teams, as it allows builders to quickly find and work on flows related to a specific business function key capabilities of the categories module include creation and management add, rename, and manage a list of custom categories tailored to your business needs flow assignment assign any flow to a specific category directly from the flow builder filtering use the category filter on the main "flows" page to instantly view only the flows belonging to a specific group how to use categories this guide explains how to create categories and how to assign your conversation flows to them 2 1 navigating to and creating a category from the main console menu, navigate to workflow > categories on this page, you will see a list of all existing categories to add a new one, click the add category button (or similar, based on the ui) enter a name for your new category (e g , account support) and save it you can also search for existing categories using the search bar on this page 2 2 assigning a flow to a category the primary way to use categories is by assigning them to your flows navigate to the flow builder by either creating a + create flow or editing an existing one from the main flows page click on the first node in your flow, the intent trigger node, to open its configuration panel locate the select category dropdown field choose the desired category from the list if you haven't created any, the default will be "others " save the changes to the node 2 3 filtering flows by category go to the main flow management page by navigating to workflow > flows click on the filter button located above the table of flows in the filter options, select the category dropdown and choose the category you wish to view click apply the table will now only display the flows assigned to that specific category common examples and use cases organizing by department for a large enterprise bot, create categories like hr, it support, finance, and facilities to separate departmental queries structuring by product line an e commerce bot could have categories for electronics, apparel, home goods, and customer service grouping by user intent a banking bot could be organized into categories such as check balance, fund transfer, loan application, and report fraud internal vs external flows use categories to distinguish between flows designed for internal employees (e g , employee onboarding) and those for external customers (e g , product inquiry) best practices establish a naming convention keep category names clear, concise, and consistent this makes it easier for all team members to understand the structure don't over categorize while useful, having too many categories can be as confusing as having none aim for a balanced structure that logically groups your flows without being overly granular use a "general" category wisely it's okay to have a general or "others" category, but review it periodically to see if new, more specific categories should be created from the flows within it assign categories immediately make it a habit to assign a category as soon as you create a new flow this prevents a build up of uncategorized flows that need to be sorted later common mistakes inconsistent categorization two developers might create similar flows but assign them to different categories (e g , putting a "password reset" flow in it support while another is in account management) this defeats the purpose of organization creating duplicate categories forgetting to check if a category already exists and creating a new one with a similar name (e g , having both sales and sales inquiries) leaving everything in "others" the most common mistake is neglecting to categorize flows at all, leading to a large, unmanageable list in the default "others" category using categories for flow logic categories are purely for organizational purposes within the console they have no impact on the bot's runtime behavior or how a user interacts with it do not expect filtering by category to change how the bot works for the end user