Learn how to write and design a chatbot: UXWC course preview

Chatbot writing and design

Learn how to write and design a chatbot: UXWC course preview

Want to learn how to write and design chatbots? This guide will give you everything you need to know. No coding required!

Bobbie Wood
March 17, 2020


Curious about how to write and design chatbots? This post is made up of material from the first few lessons of our Chatbot Writing & Design course.

If you’re a UX writer, content strategist, developer, project manager, product manager, producer, or anyone interested in learning how to create a chatbot, this course is for you.

Learning how to write and design chatbots is an essential skill

This first unit will cover all of the basics of what a chatbot is, and explain why learning how to write and design chatbots is so crucial.

Before we dive deep into UX writing for chatbots, it’s important to understand the vocabulary used in this course and in the chatbot and conversation design industry. 

A few definitions

First, and most importantly, what is a chatbot? 

#1. A chatbot (also commonly referred to as a bot, short for software robot) is an automated, conversation-based experience that lives within messaging apps, websites, or on devices. It simulates human conversation via voice or text. Chatbot decisions are sometimes powered by Artificial Intelligence (AI), by human-created rules, or a hybrid of both methods.

The alarm clock on Alexa is a chatbot. Automated customer service experiences like American Express, TD Ameritrade, and The Weather Channel on Facebook are chatbots. The SMS alerts you receive from a drugstore like CVS (similar to Boots in the UK) are from a chatbot.

Bots can be purely entertaining, teach you things, grow your business, help build a habit, send news updates, answer frequently asked questions, and lots more. 

Chatbots sit at the intersection of these points – and always with the customer’s needs in mind.

 

 

 

 

 

 

 

 

 

 

 

#2. Conversation design is the art of writing and designing for chatbots. This is a newer design discipline based on human conversation. 

Conversation design involves writing the dialog and architecting the experience for an automated conversation that unfolds in a rule-based or intent-based narrative on a variety of device and software interfaces. In some cases, the dialog may be assisted by natural language processing (NLP). (We’ll define these terms in just a moment.)

To put it more simply, conversation design helps a chatbot talk to a user, and helps the user understand what to do, so they achieve what they set out to do when they began their conversation. Just like in UX writing, users have a goal and chatbot writing helps them reach it.

While chatbots rely on technology, conversation design is very human-focused. As Erika Hall puts it in her book, Conversational Design

“Conversational design is truly human-centered design, every step of the way. There is no next big thing, only the next step in an unfolding story of how people use technology to be more themselves.”

 

#3. Conversation designers are UX writers for chatbots. They design and write the dialog for the chatbot, as well as any other text, buttons, intents and replies needed to support the user  experience within an automated conversation. 

#4. A conversational interface is the application or platform that a chatbot lives on, like Facebook Messenger, Slack, Twitter DM, a website, an app, or a device like Amazon Echo or Google Home.

In the same way that UX writers write user interface (UI) text, conversation designers write the conversational user interface text that a user sees or hears (CUI, or VUI for purely voice-based experiences). 

 

#5. One more term we’ll want to cover is intent. A user interacts with a business or a software program because they have a need or a want. That need or want is called an intent in conversation design. The user might state their intent in several different ways—each of which we’ll need to recognize and respond to. For example, if a user wants to set an alarm, they might begin with:

  • “I need to set an alarm.”
  • “Wake me up at eight.”
  • “Set an alarm for eight A.M.”
  • “Change my alarm for tomorrow.”

The bot would need to understand the intent behind each of these utterances (the words users actually say), and ask for clarifying specifics, like what day or what time to set the alarm for.

#6. Our last term is slot. You can think of a “slot” as something like a variable or a parameter in programming. 

Two main types of bots

Currently, there are two main ways that chatbots work. Both require conversation design:

  • Rule-based chatbots: Bots that are based on a set of rules and use a planned, guided dialog. This chatbot has a script that the user must stay on.
  • NLP-based chatbots: Bots that use natural language processing (NLP) and artificial intelligence (AI) models to parse different intents and decide which answers to serve up. 

The best way to understand the difference between rule-based and NLP-based chatbots is that with rule-based chatbots, the bot only says what the conversation designer tells it to say and nothing more. The bot follows a strict script. If your user goes off-script, the bot is lost.

Rule-based bots are much simpler than NLP-based bots. They’re cheaper, easier, and faster for companies to build. They don’t require Artificial Intelligence. They do require human intelligence—that’s where you come in!

With NLP-based (AI) chatbots, the bot learns over time, starting with what we train it to know, but it still needs the conversation designer’s help to deliver its knowledge.

An NLP-based bot is like a chatbot that went to school, but still needs to do homework practice and learn how to apply its new skills in the real world.

With an NLP or AI-based bot, the user can use their own words or phrases and the bot will look for similarities from past conversations (training) or existing data models to interpret the question and provide an answer. It’s a more sophisticated form of chatbot.

It also requires deeper development resources and comes with a heavier price tag. Large corporations most commonly build these bots.

In this course, we’ll be creating a rule-based chatbot. Although many of the design principles apply to both text and voice chatbots, we’ll focus on simple CUI design in this course.

Everything you learn here will help you to build more sophisticated bots down the road.

Why businesses want to write and design chatbots

It seems like every website or store you visit has some form of chat component, either automated or human-powered. There are clear reasons a business may want to implement a chatbot, and many benefits to sales, marketing and support with automation. 

Convenience

The first thing that comes to mind is the convenience for the business and the customer. Chatbots enable businesses to respond to customers 24/7, even when the business is closed.

A business can also have personalized conversations with many customers at once, plus scale their marketing, sales, and support initiatives to reduce queues and wait times.

Customers no longer have to wait for a human to join a live chat, or wait on hold on the phone. This is a huge benefit. According to HubSpot, 57% of consumers are interested in chatbots for their instantaneity.

A customer can also choose to chat at the time that works best for them because of the always-on nature of a chatbot. If they want to send a message at 3am they can, and if they want to pick up the conversation at a later time or even another day, they have the ability to do so.

Efficiency

Chatbots are a form of automation, meaning their messages are triggered automatically through a customer action instead of a business owner sending a message from their own phone or computer. Delivering a personalized, consistent brand experience to every single customer that engages with a chatbot is invaluable to a business.

Persistent channels

If you currently receive automated text messages from a business (like a political campaign or a store you shop at), you may notice that you receive them on a scheduled weekly or monthly basis.

These bots offer businesses a persistent, continuous channel for communicating with customers. When a user texts a business or messages the business’s Facebook chatbot, they become a user that the business can re-engage with strategically at a later time, including using personalized information like their name or referring to previous questions.

As we mentioned earlier, when a lead leaves a website, they’re usually gone. If they haven’t signed up for a newsletter or left an email address, the business will have a hard time initiating any engagement with them again. Bots create a 2-way connection that can help build ongoing relationships. (Read more about the benefits of SMS chatbots.)

Technology

Emerging technologies, like chatbots, help to set a business apart from their competitors by showing innovation and a willingness to try even harder to meet customer needs. 

Additionally, having many automated conversations with users allows the business to take a look inside the minds of their customers.

They can see the most frequent requests, look at instances where a user is trying to use the chatbot for something it was not built for, or quickly survey a large group of people.

The data collected from the chatbot is very useful for the business. If a business is using NLP for their chatbot, they are able to improve their data model and train their chatbot to be smarter using the conversation data from real customers.

How does a conversation designer write and design chatbots?

As we covered in the previous lesson, a conversation designer is a UX writer for chatbots. There are many other common names in the industry for a conversation designer — 

  • Chatbot Writer
  • AI Writer
  • AI Interaction Designer 
  • Conversation Architect 
  • Conversational UX Writer 

They all do the same thing—design the conversation that a user has with a computer.

UX Writers make excellent chatbot writers 

There’s a lot of UX within conversation design, which is why UX writers make great conversation designers.

With chatbots, the words that appear in on-screen speech bubbles make up almost the entire experience. The dialog between the bot and the user determines the different paths they can take, so the words become the primary mode of interaction. 

How the bot responds to user’s needs influences how they move through the flows. There aren’t many visual cues to help guide them, only your words. That means a chatbot is only as good as the writing that goes into it. 

It makes sense that many general principles of successful UX writing apply when designing chatbot conversations. After all,  the core of UX writing is to facilitate seamless communication between a user and a digital product. Chatbot design aligns with the same design principles as UX writing:

  1. Be friendly
  2. Be concise
  3. Guide users
  4. Prevent and fix errors
  5. Make sure users successfully complete tasks

Cathy Pearl, Google’s Head of Conversational Design Outreach, describes conversation design this way:

“It’s how we can create experiences that enable computers to communicate like humans do, and not make humans learn a weird computer-like language”

In a chatbot, the language must be incredibly efficient, build user trust, and clearly establish the “rules” of the conversation, since there is no human to step in and help. This conversation is non-linear and multi-pathed, like a choose your own adventure book or a video game. The more flexibility and alternative flows you design for your bot, the more engaging it will be, and the more likely it is that the user will complete the experience without failure.

The responsibilities of a conversation designer

Writing the conversation a user has with the chatbot is only one part of what a conversation designer does. Before we even start writing, the convo designer has to think through strategy, planning, outlining, and mapping flows.

When planning a chatbot, the conversation designer must create and design all of the dialog paths or flows the user could take to reach the end goal. Those paths can include business goals like sales conversion, issue resolution, subscribing, or something else. 

They must also take into consideration—and predict—instances where a user may get confused, say something unexpected, or want to act on an experience that may not be one of the paths designed for the chatbot. 

For example, if you have a customer acquisition chatbot designed to give a user a quote for a service, but that user wants to get to customer support instead, you would need a plan for this.

We’ll break the responsibilities of a conversation designer into four phases: 

  1. Strategy
  2. Design
  3. Prototyping
  4. Testing 

The strategy phase

In the strategy phase, the chatbot designer seeks to understand the goals, expectations, and desired outcomes for the bot. Then, the designer has to understand how to meet those goals. And lastly, the designer must decide how the chatbot will lead the user down planned dialog paths to arrive at that goal.

The strategy phase includes the following responsibilities:

  • Interviewing the business stakeholders to determine the chatbot goal and key intents
  • Interviewing the department stakeholders who understand the steps needed to reach the goal (they could be on the sales or customer support team)
  • Creating an outline/flow map of the conversation experience

The writing & design phase

In the writing and design phase, the hard work happens. This is where you’ll build out your specific dialog options and paths for the bot.

The design phase includes the following responsibilities:

  • Creating a template for the the key flows based on your flow map
  • Creating and documenting the personality of the chatbot
  • Writing the dialog of the chatbot
  • Writing a few user responses (pre-planned answers available to users)

The prototyping phase

In the prototyping phase, we will see the chatbot experience shape up into something that feels more real. You’ll create a mockup of your flows to see and share the user experience with testers.

The prototyping phase includes these responsibilities:

  • Choosing a tool or platform for prototyping (for us, it’s Botsociety)
  • Building the hello, fail state or catchall, and goodbye flows (more info later in the course!)
  • Building additional task flows in the prototyping tool
  • Ensuring each step includes user responses for them to choose from

The testing phase

The testing phase, like most user testing, is critical for ensuring that the options we’ve designed actually work for users. We’ll look for opportunities to optimize and streamline our bot before releasing it.

The testing phase includes the following responsibilities:

  • Exporting and sharing the chatbot prototype
  • Reviewing the prototype and identifying friction points
  • Iterating on the chatbot script and writing any additional flows or messages to improve the experience
  • Reviewing the prototype with key stakeholders to test comprehension and success based on the initial goals

As the chatbot industry evolves, we may see a future where chatbot “conversational strategists” emerge, and work with a conversational designer to create the ideal experience for a chatbot user. For now, the conversation designer is responsible for all four of these phases.

See how different generations use chatbots as part of their overall communication

Writing dialog flows

Once a user is inside of a chatbot, they will interact with a variety of flows while they work to achieve their end goal. A flow is a name for a specific section of the conversational dialog, one of the paths. The name comes from the conversation flow, or progression of the conversation. In UX writing and UI design, we’ll often refer to these as “task flows.” 

The conversation designer is responsible for writing each of these flows, and also connecting them together so a user is able to seamlessly navigate through the entire conversation on many paths. 

To imagine it visually, if you had a flow chart that mapped out the conversation, a flow would be one line on the chart. We call this chart a flow map, which is the outline or dialog tree of the entire chatbot experience.

Example of a flow map (draw.io)

 

 

 

 

 

 

 

 

 

 

 

 

There are several key flows that make up a chatbot: 

    • Hello Flow
      Greet the user and get them started.
    • Main Flow
      Take the user through the intended task.
    • Goodbye Flow
      Resolve the experience and ensure satisfaction.
    • Fail State or Catch All Flow
      What the bot says when it doesn’t understand the user’s intent and wants to redirect them.

Keen to learn more? Check out our Chatbot Writing & Design course!