However, that’s not why you are here at the moment because these are just secondary pieces of information in this article. After some research, I decided to test myself in a challenge. My goal was to design and set up a working chatbot for business purposes in less than 2 hours.
In order to demonstrate the true potential and scalability of this technology I stuck with one rule.
The project must not require any prior experience in coding!
If you stick around, you will learn:
- what core UX practices should you involve
- what tools you need to create a simple bot on your own
Let’s get started.
Table of Contents
About the project
One of the huge benefits of having a bot is that you can frame it as a decent automated customer service equipment. It can be a great addition to your conversion optimization toolbox. I decided to create a simple chatbot that would allow customers to view the menu and book tables in a few steps. This would also mean that the business — let’s name it Barnie’s Restaurant — could automatize these processes. Having a nifty little feature like this can lead to increase customer experience.
The two basic tools I’ve used creating the chatbot:
- a whiteboard and some markers
- a bot building platform
There are plenty of them out there to choose from and you can easily pick one that fits your purpose the most. I went with Motion AI. It has some nice templates and pre built modules ready to deploy. The UX is great and it offers a smooth, convenient experience overall even if you’ve never done anything like this or have no programming experience so far. In other words, it’s not just user- but also very beginner-friendly. Another good platform I would recommend is Chatfuel since it’s also very user-friendly. Botsify is great too, but it can be overwhelming for newcomers at the beginning.
The design process:
Before jumping into the actual design process I always like to work my way around the problem itself. When people hear the word “problem”, they usually think of something wrong. I like to think of problems as questions that need answers. Some can be easy to answer while others can be challenging. At this point you should decide the following:
- What is the main problem, what do I expect by solving it?
If you can’t answer this question, the next thing you should decide is the why? Is it because of complexity or not?
- How complex is the problem?
- Do I REALLY need a chatbot?
It might sound funny but it’s important to ask this question. You have to make clear that you have at least one reason to invest resources into the project.
Make sure you’ve gathered enough data about the users. Not only the quantity matters but quality insights are also required to answer the following question:
- What describes my users/customers the most?
If you are familiar with the world of User Experience Design, the term “Persona” should ring a bell. In case it doesn’t, there’s no need to panic – it’s not rocket science.
- What personality would correlate the best with the Personas?
In the example of Barnie’s little assistant Nom-Nom Bot, I decided to go with a slightly informal tone.
This is the part where the magic happens, the actual design flow. If you look at the whiteboard it might look like a big mess at first but the core elements are easy to spot.
Things to keep in mind during planning:
1. Avoid wall of texts:
No need for long introductions about how awesome your company is. That’s why you have an ‘About’ page on your site. If you really insist on introducing it, make a separate option for it.
This isn’t a book club.
Introduce the bot in a polite way, keep it short, clean and don’t waste time.
“A computer shall not waste your time or require you to do more work than is strictly necessary.” — Jef Raskin
2. Offer only what you can fulfill:
Don’t try to pretend that your bot is a human because this will create a false illusion, which misleads your users/customers and instinctively increases their expectations.
At the beginning, my greeting was followed by this statement:
I’m Barnie’s assistant, Nom-Nom Bot!
This simple statement will make it clear to the user that s/he is talking to a chatbot. Don’t even try to go fancy and name it <something> AI because this will automatically trigger unwanted conversations that have nothing to do with your business.
3. Provide fearless exploration:
Think of your chatbot as if it was an app that the users want to explore. During the exploration, they click/tap on things sometimes just out of curiosity. The worst you can do is not providing a way back thus making them feel that they might regret the next step.
In the Nom-Nom Bot project, I decided to let the visitor navigate around freely by letting him know that going back is an option indeed.
4. Optimize for mobile:
You might think that you have plenty of space to fit information in but nothing is more annoying than a stuffed small screen that you have to scroll through. If you compare figure 3 with figure 4 you can see the difference.
5. Have common answers ready:
The less they have to type, the faster and smoother the flow will be.
6. Provide a way of exit:
A common practice in business etiquette and protocol is offering the guest a seat that provides a clear view over the room’s exit. The psychology behind this practice is that the guest’s position gives him/her the option to leave, building up trust and comfort at the same time.. Needless to say that this applies also to the world of UX and a good designer keeps this in mind.
+1 Always thank them:
They might go through the whole process or back right away as soon as they see that it’s a chatbot. It doesn’t matter at this point if they leave with a confirmation process or not, one thing is for sure:
“You MUST thank them.”
If you have ever considered that you might need a chatbot, well, I have good news. With some very basic tools and a little bit of investment, you can make yourself and your business a real favor by creating a chatbot. The growing hype around AI will make this reasonably fresh technology future-proof.