The drop-down menu can be found at the top of the platform. There’s a chance you can only see a white half-circle, but if you hover your cursor over the white half-circle then the menu will appear. The menu is not fixed unless you click the white half-circle.
Naming your chatbot
Next to your chatbot's photo, there's a placeholder, where you can name your chatbot. The name is internal, so it will only be visible to you and your team.
Zoom in and out
These two functions are useful when you need to zoom out on your chatbot to get an overview of the entire bot and structure of the bot or zoom in to find a specific part of your bot.
Undo and redo changes
These functions can be used if you want to undo an edit you have just made or retrieve the edit, which you have undone.
As the name suggests; it saves your changes. It’s important that you save your changes often while working on your chatbot, and we recommend you save every time you add a new module to your chatbot. When you save your changes the platform does not automatically publish these changes to a chatbot that is live. Therefore, if your changes should be published to a live chatbot you should also press "Publish changes".
Here you can test the communication flow of the chatbot. It’s nice to do regularly to get a sense of the messages and the timing of the different messages. You will need to save changes before you can test your newest edits, otherwise, you will be testing the latest saved version of the chatbot.
The testing feature includes a debugging function that allows you to gain insight into what Module Connections and Global Connections are being matched, which webhooks are being fired and whether the webhooks were successful or not.
Additionally, the testing feature allows you to set some Initial Variables. These variables allow you to define the value of a given variable with the purpose of testing how the flow of your chatbot would go if the variable was filled.
For example, in the screenshot below, we're filling the variable "first_name" with the value "Kevin". This allows us to simulate a conversation where the user's first name is "Kevin".
Another example for showcasing the usefulness of the Initial Variables is testing conversation flows that are dependent on channel-specific variables such as the ones that are returned from using our Zendesk Chat Agent Availability webhook template. Because webhooks made from this template will always fail if you don't fire them while you're in the Zendesk Widget, Initial Variables are useful here because we can force the availability of a certain department to be "true" by using the following code in the Initial Variables:
When you have saved changes an orange button will appear, which says “Publish changes” when you press this it will automatically publish your changes to a live chatbot (if your chatbot is live) and the button will change and become pink and say “Updated”. This also means that even though you save your changes, they will not appear in your live chatbot before you have pressed this button.