As you build your bots, it's important that you understand how to add, delete, clone, and test Modules, edit Module messages and connections, and add KPI tags. Below, we'll address the platform features you'll use to do so successfully:
Add new module
To add a Module, you can either right-click on the canvas or use the right sidebar menu, then choose the desired Module type.
Notice how the new Module has a number in the upper left corner? When you've just created the Module, it will be a negative number. After saving, a positive number will appear. We always recommend saving right after creating a Module.
If you hover your cursor over a Module, a preview of the text within that Module appears. You'll also be able to see a number of different functions displayed above the Module. The functionalities are as follows:
This is where you can edit the message of your Module. You can also edit by double-clicking the Module.
This is where you can connect the Module to other Modules. This means the chatbot will send your customer to another designated Module based on the end user’s input.
This function will create a copy of your Module.
This is where you can delete a specific Module. Upon clicking this, you will receive a pop-up message wherein you must confirm that you do wish to delete the Module before it is removed from your bot.
Test flow from here
This function differs from the Navigation bar's "Test" button, which always tests your bot's communication flow from the beginning. In contrast, the "Test flow from here" function only tests from this specific place in the flow.
This is especially useful when your bot becomes bigger and more complex, so you don’t have to start over every time before being able to test what you're really interested in.
Add KPI tag
When you hover your mouse over a Module, a tag option will appear underneath the Module. This is the KPI button, where you can add a KPI tag. This should only be used on starting Modules, fallback Modules, and handover Modules.
By adding a KPI tag, you can gather data on these specific parts of your chatbot, tracking metrics like how many end users have interacted with your chatbot, needed to be handed over to customer support, or ended up in a fallback path.