Using the Tester you can test your conversational flow using chat or via phone call.
The phone conversation will be triggered by an outbound call from the studio platform to your own device.
After you selected the event in your agent you'd like to test, select "Phone Call" and fill in the phone number you want to receive the call to. Once you pick up the call, the agent will greet you with the welcome message you added. Now, you can test your conversational flow via the phone.
After you selected the event in your agent you'd like to test, select "Chat". Once you click "Start Test", it will show you the welcome message of your agent.
The tester will also show when actions have been performed successfully, e.g. when SMS and Emails were sent successfully.
Sometimes the flow can be influenced e.g. by the user's phone number, whether the agent was reached during or after hours, etc.
A list of all Parameters used in the agents will show when you click on the cog on the top right of the tester. It will be divided by custom parameters created by you and system parameters. Here you can fill in the parameter values that might have an effect on the outcome of the conversation.
Refresh the testing session by clicking on the two circular arrows on the top right and test your flow with the new values.
You can test the "No Input" scenario for Collect Input or Listen nodes by simply typing "no input" into the tester. It will return the desired response for this scenario.
When testing your conversational flow in the chatbot tester, you can easily locate each node used. Click on the "Go to node" icon next to the agent response or user input box and the canvas will zoom in on the relevant node.
Firstly, the tester will notify you if the Webhook was executed successfully. If unsuccessful, the check would turn red and show an unsuccessful attempt message.
If your Webhook node returns a failure, you can get more information by clicking on the code sign on the top right of each text bubble, the JSON file of the conversation will open on the left of the tester. This can be a very helpful tool to debug.