Travel Bot
Report Updated: 1 week ago

Bot Health

70%

Learn what this metric represents.

Enable continuous testing to keep your bot health score updated and receive real-time notifications.

Continuous Testing
Issues found while testing script Trip inquiry story 7 days ago
Warnings identified while testing script Ticket purchase 7 days ago
Successfully finished testing script: Confirm Booking 9 days ago
Successfully finished testing script: Trip inquiry story 9 days ago
Warnings identified while testing script Ticket purchase 9 days ago
Successfully finished testing script: Confirm Booking 9 days ago
Test engine instance created. 9 days ago

Thematic Reports

Summary of high-level results

1

Functionality

Issues
1

Usability

Warnings

Performance

Metrics
1

Help

Support

Privacy

Compliance

Functionality

Unresolved issues, detected during the last bot audit, having a negative impact to the behavior of your bot

The bot response did not match the expected one. Based on the utterance found in line 5 of the Trip inquiry story, the message sent by the bot to the user should have been the similar to the following: Let's see what we can find.

The respective message is highlighted below:

👤 User
Can you show me all hotels with a pool?
Bot 🤖
Please, repeat your question.
Tip
Try to re-train your chatbot engine to reply appropriately to the particular request made by the user. Moreover, you should also include as many rephrased user utterances as possible during the training phase in order to enable your bot to better identify the user's intend and be able to respond appropriately to users' utterances expressed in slightly different manners.

Usability

Unresolved warnings, detected during the last bot audit, affecting the conversational user experience

Based on your Ticket purchase script, our analysis indicated that your bot response, deriving from line 3 of test script, contained too much text. This has been found to negatively affect conversational user experience.

The respective message is highlighted below:

👤 User
I want to buy a ticket for Amsterdam
Bot 🤖
Great! I would be glad to help you with this request. First of all, I would need to ask you to confirm whether you would like to book an airplane ticket. Then, I would need a few personal details such as your name and your passport number in order to book a flight for you. Are you OK with this process?
Tip
Consider keeping the size of your bot utterances under 90 characters. You should avoid monologues. While being informative, try to keep responses as concise as possible. Let users take their turn and do not go into heavy-handed details unless the user will clearly benefit from it.
Example
Do
🤖
OK, I found 4 sections with available spots for 2 people sitting together: sections 211, 212, 215, and 218. Do you want to hear more about one of those?
👤
Yeah, the one in section 211
🤖
Ok, in section 211, row 14, seats 7 and 8 are available. You can purchase them for $130 each. Do you want to get these?
Don't
🤖
Ok, I found 4 sections with open seats. Section 211, row 14, has 2 open spots: seats 7 and 8. You can purchase these for $130 each. Section 212, row 7, has 2 open spots: seats 15 and 16. You can purchase these for $130 each. Section 215, row 2, has 2 open spots: seats 9 and 10. You can purchase these for $160 each. Section 218, row 5, has 2 open spots: seats 4 and 5. You can purchase these for $150 each. Which would you like?

Performance

Metrics showcasing the responsiveness of your bot

Average response time

How much time is required to respond to a user request

Uptime

Depicting the time your bot was operational or had a downtime

Help

Evaluating whether your bot understands the users' support requests

Handled vs unhandled help requests

The percentage of support requests' comprehended by your bot
70% Handled
30% Unhandled

Missed requests

Train your bot to support utterances such as the ones presented below
help me please
/help
show help menu
fallback detected no response detected

Privacy

Checking if your bot complies with privacy-related best practises

Accessible privacy policy
Detected

Be transparent regarding who owns the data shared with your bot. The privacy and protection of user data is paramount in today’s interconnected world.

Right to be forgotten
Detected

The right to be forgotten reflects the claim of a user to have (certain) data deleted so that third parties can no longer have access to them. This action should be available to your bot users.

Customize testing to your needs


Try our Premium Plan