How to deal with errors like a bot

Tips and tricks for dealing with mistakes

Tess Tettelin
6 min readMar 11, 2021

Iā€™m sure Iā€™m not the only one who absolutely loves that little backspace button on my keyboard. I donā€™t know how often Iā€™ve pressed it by now, but itā€™s definitely A LOT.

Sadly, there is no backspace button in real life.

You can prepare oh so well, but in the end, weā€™re only human. We do weird things and make mistakes all the time. I remember sitting down at a tiny restaurant somewhere in the South of Thailand and looking at the menu, not understanding a single word of what I was trying to read. So instead, I just pointed at something and ended up eating a very dubious-looking dish that Iā€™m pretty sure had chicken feet in it. The lady who cooked and served it kept staring at me, so I had no other choice than to finish the entire plate, thank her, and continue my journey feeling a little bit nauseous.

What Iā€™m trying to say is, mistakes happen all the time, itā€™s how you handle them that matters. The same goes for chatbots. No matter how well youā€™ve trained them, bots deal with people and people are very unpredictable. We express ourselves in a bazillion different ways and say the weirdest things (especially to bots) so itā€™s kinda impossible for your bot not to make any mistakes.

So how can you deal with these errors gracefully and efficiently? By making sure you have a few good error messages built into your conversation. Not sure how to do that? Iā€™m here to help! Here are my best tips and tricks on creating kick-ass error messages:

1 ā€” Keep calm and clarify the mistake

The first step to writing a good error message is to first acknowledge and then clarify the actual error. Just own up to the mistake. If your bot is not able to understand a request, let the user know, but please donā€™t act as if itā€™s the WORST THING THAT EVER HAPPENED. Overly apologetic bots are not helpful, theyā€™re just reallyā€¦ annoying. Also, most users understand by now that bots are virtual things that mess up every now and then. That being said, they do expect you to clarify the mistake and provide them with a way forward.

Which brings us to the next tip.

2 ā€” Provide a way back to the ā€œmain menuā€

When using more traditional graphical user interface (GUI), it has become second nature for us to look for the home button whenever we want to start over. Command+r please. But when it comes to conversational interfaces, starting over can be a bit more tricky, though it shouldnā€™t be impossible.

Letā€™s say youā€™re building a chatbot for a product platform that can help its users do the following tasks:

  1. Explain pricing models
  2. Show product features
  3. Book a platform demo

If I ask this bot to ā€œgive me the number of the CEO,ā€ the NLP probably wonā€™t recognize that intent ā€” at least, I hope not. This use case it isnā€™t part of the original bot scope, so the bot wonā€™t understand the question and will need to fall back on an error message:

Sorry, I canā€™t help you with that, but I can tell you all about pricing and product features, or book a platform demo to get you started straight away!

Sounds good, right? With an error message like this, the bot not only shows empathy and understanding, but it also provides the user with a way to continue the conversation.

Another way to guide the user back to the ā€˜main menuā€™ is by adding a ā€˜start overā€™ intent with expressions like ā€œhelpā€ and ā€œstart overā€ that trigger the ā€˜main menuā€™ or introduction message.

3 ā€” Write various error messages

One of the best practices of conversation design is to create different variations of bot messages: various greetings, various responses to chatter and yes, you guessed it, various error messages! No one wants to hear the same message over and over again ā€” it causes a bad user experience and feels way too robotic ā€” two of a botā€™s biggest sins. So make sure to create various error messages to keep the experience conversational:

User: I need a massage.
Bot: Sorry, I didnā€™t get that. Can you rephrase?
User: I just want you to massage me!
Bot: Sorry, I still donā€™t understand. Try one more time?
User: MASSAGE, NOW
Bot: Sorry, I canā€™t understand. Would you like me to connect you with customer service instead?

4 ā€” Make sure you have a back-up plan

If your bot is really stuck and canā€™t understand its user, make sure it can reroute them to another line of support. This could be an FAQ page on your website, a phone number to reach customer support, or even an email address where they can send their question to.

Chatlayer.ai provides built-in options to redirect a user: forward the call to another phone number, send an email, or connect the user with a live chat integration like Genesys.
Inga, the chatbot of ING, provides an elegant way out of an error

5 ā€” Add some humor (but tread carefully)

I love a funny bot, I really do, but it all depends on what Iā€™m trying to achieve with it and how important those tasks are. For example, if Iā€™m trying to transfer my house rent using a banking bot and it keeps messing up, I wonā€™t be in the mood for a joke. But if Iā€™m using a retail bot to browse for new clothing and it canā€™t seem to find the ā€˜perfect white shirtā€™, I donā€™t mind a little joke to lighten things up. As my CEO likes to say: ā€œwhen in doubt, leave it outā€. Iā€™d like to add: ā€œBut when appropriate, go for it!ā€

This is a non-urgent, low-risk task where a little joke is appropriate

6ā€” Make your users feel heard

If your bot canā€™t help its user, at least make sure they feel heard. Ask for feedback! I always include a little feedback flow into every bot I build, not only is this super-duper handy for collecting valuable feedback on the botā€™s performance, but it also shows the user that, yes, we do care about your opinion and we do want to hear what you think. People really appreciate it if you give them a chance to share some feedback.

Right, I think thatā€™s about it! If you have any questions, feel free to get in touch. And if not, carry on and happy bot-building!

Hi there, Iā€™m Tess, language lover and taco enthusiast! Currently Conversation Design Lead at Chatlayer by Sinch, I like to write about the things I learn and see when building multimodal bots.

Interested in knowing more about voice and chatbots? Want to swap ideas or talk conversation design? Reach out to me on Twitter!

Donā€™t forget to leave some šŸ‘

--

--

Tess Tettelin

Conversation Design Lead at Sinch. Writing about technology, human behaviour and anything else that crosses my mind.