This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

Conversational User Interface Design Best Practices

  • 20750 views
  • 7 min
  • Oct 01, 2019
Anastasia D.

Anastasia D.

Copywriter

Alexander M.

Alexander M.

UI/UX Designer

Tags:

Share

For this blog post, we teamed up with Alexander Martynenko, one of the leading UI/UX designers at RubyGarage, to create a concise guide to designing conversational UIs. Keep reading to learn what conversational UIs are, why they’re worth paying attention to, and how to create them. 

What’s a conversational user interface?

A conversational user interface (CUI) is a digital interface that allows users to interact with a product based on principles of real-life human communication. Put simply, users don’t need to look for information in the graphical interface; they can just tell the device what to do verbally or in writing. The core technology used by conversational interfaces is Natural Language Processing (NLP). NLP is a form of artificial intelligence that deals with parsing the real intent of a user’s command. Traditionally, computers understood a query or command in a programming language; but with NLP technology, they can clearly understand natural human language.

The main idea behind conversational UIs is to create seamless and simple communication between a consumer and a device. Huge technology companies such as Google, Facebook, Apple, and Amazon consider CUIs to be the future of communication with users. 

Types of conversational user interfaces

There are essentially two types of conversational UIs: chatbots (like Facebook Messenger) and voice assistants (like Apple’s Siri, Microsoft’s Cortana, Amazon Echo, and Google Assistant).

Chatbots

Today, more and more businesses, especially in the ecommerce industry, are integrating live chatbots since they’re easier to implement than voice assistants. A chatbot is a visual interface where communication between a bot and a user is natural and is displayed in chat bubbles. Chatbots revolutionize the way online businesses interact with customers. In order to choose the right chatbot for your product, let’s compare the two types of chatbots that exist today.

AI-driven chatbots

AI chatbots can understand the intent of a user’s query before giving a response, as they use natural language processing and machine learning. An AI-driven bot can not only understand commands a user gives but also generate its own responses according to the context. Here are some more advantages of AI chatbots:

  • They continuously improve
  • They can be programmed to understand different languages
  • They understand patterns of user behavior
  • They learn from the data they gather
  • They can make decisions

Rule-based chatbots

As the name suggests, rule-based chatbots are powered by a set of rules. All possible conversations between bot and user are mapped out.

Chatbots

This means rule-based chatbots can answer only predefined questions and can’t respond to any others. Although rule-based chatbots are less flexible in conversation than AI bots, they’re easier to predict. These are some of the other benefits of rule-based chatbots:

  • They’re less expensive since they’re faster to train
  • They’re more secure
  • They integrate with legacy systems easily
  • They can use some interactive elements and media

Voice assistants

A voice assistant is an AI-based service that uses voice recognition and NLP technologies to perform a particular action in response to a voice command. Voice assistants are also bots, but they don’t use any graphical interface – only voice. 

Voice user interfaces (VUIs) operate based on artificial intelligence, machine learning, and voice recognition technologies. The technology required to create a VUI is very complex, so few companies can afford to implement voice assistants.

Voice assistant’s usage

Conversational UI design best practices

In order to create an effective conversational interface, it’s necessary to follow best practices and basic principles of creating conversational processes – as well as the basic rules for their visual design. Let’s learn the basic rules of creating stunning conversational UIs. 

#1 Make the application’s background clean

The background of the application shouldn’t distract a user from the dialog, so make it clean and minimalistic. If you use a pattern, it shouldn’t draw much attention. The main thing a user should be focused on is the dialog itself.

conversational ui

#2 Be concise

A concise conversational UI has two main advantages: it simplifies the understanding of the text and leaves enough whitespace. In addition, shorter sentences are better displayed and perceived on small displays. If you need to display more text, break it into multiple messages.

conversational ui best practices

#3 Avoid false options

False options are options that a bot can’t respond to meaningfully. For example, say a user sends a request to search for information. In order to see more search results, the bot reminds the user to type “more,” though there are actually no additional results. This is a false option so it leads the user to a dead-end.

conversational ui design

#4 Choose the right words for commands

Be consistent in choosing phrases for commands. Using different phrases (e.g. save, add to your list, remember) to denote the same functionality can confuse users. With too many synonyms, users won’t remember what commands actually do. That’s why we suggest using one phrase for one functionality so users remember its meaning.

#5 Choose the right voice for the assistant

When choosing a voice, give your assistant a personality that links it closely to your brand. To let customers know they’re talking to a voice assistant, many brands also give their assistant a name. This allows them to be transparent with customers while maintaining a friendly tone. Consider the following things when creating a voice for your assistant:

  • Target audience
  • Social context
  • The problem your bot solves
  • The brand your bot represents

#6 Make sure your bot understands commands

When your bot doesn’t understand a command, there are many strategies you can try before sending the message “Sorry, I don’t understand”:

  • Check if the unknown command is the result of a typo
  • Check if an unknown command is synonymous with a known command
  • Use an alternative strategy specific to your bot’s domain

Basic principles of conversational interfaces

Purna Virji, the senior global communications manager at Microsoft, has outlined four basic principles of interactive interfaces:

Clarity

There are two systems that determine our decision-making: emotional and intuitive (Homer stage) and logical and thoughtful (Lisa stage). In conversational UIs, it’s necessary to keep people at the Homer stage where everything is easy, convenient, and intuitive. If users go to the Lisa stage, the decision-making process slows down. 

Character

Users prefer virtual assistants with an easily perceptible personality. Make sure your bot is interesting and memorable. Also, your bot’s personality is highly dependent on its purpose. It should never conflict with your brand. Importantly, you shouldn’t try to deceive people into thinking they’re talking to a person. It never works. A bot can have a great personality without having to be human.

Compassion

Your bot should be able to show compassion. For example, a bank bot should warn users if a transaction will result in an overdraft, just as a person would do.

Correction

Every chatbot (whether voice or graphical) needs a default setting for those cases when it doesn’t know how to respond or move forward. However, this phrase can’t be repeated. When a bot repeats the same thing over and over, it leads to a conversational dead end. Correction should always offer a way forward.

Wrapping up

An important step towards creating an effective conversational UI is realizing what’s involved in building a conversational experience. Of course, it takes a conscious effort to humanize a conversational interface so a chatbot or voice assistant can become a compelling communication partner. But following the basic rules we’ve listed above will help you make this process easy and create a successful conversational UI.

CONTENTS

Tags:

Authors:

Anastasia D.

Anastasia D.

Copywriter

Alexander M.

Alexander M.

UI/UX Designer

Rate this article!

Nay
So-so
Not bad
Good
Wow
8 rating, average 4.5 out of 5

Share article with

Comments (0)

There are no comments yet

Leave a comment

Subscribe via email and know it all first!