Conversation Design

Chatbot Mapping & Dialogue

Project Title

SwiftSense Navigation Chatbot


Role(s)

Conversation Designer


Skills

Journey Mapping

Brand Voice & Tone

Conversation Design


Relevant Software

Draw.io

MS Excel

VoiceFlow

Figma




Challenge


Help users navigate SwiftSense.com.


Solution


Design a chatbot that guides users using concise brand voice.


My Process


* Collaborated with shareholders to articulate chatbot goals, identify brand voice, and align on key messages.


* Designed user flow maps, developed new copy, and participated in user research testing.



Discovery

My Role

I was brought onto the SwiftSense chatbot project to design chatbot that captured the SwiftSense's brand voice while helping users navigate the flagship site.


Brand Overview

SwiftSense is a mid-size SaaS data visualization platform that caters to small business owners inexperienced with data analytics. SwiftSense’s slogan, “Analytics for All,” reflects the brand's commitment to data democratization through accessible UI, hassle-free integration, and affordable price plans.


Brand Voice

Friendly, casual, and somewhat goofy.


User Overview

The chatbot's primary user base is small to medium sized business owners, IT teams, and marketers navigating the flagship SwiftSense site. These professionals possess varying levels of data literacy


Project Limitations

- Due to limited NLP data, user input buttons would prioritized over capture inputs

- Limited user research and testing analytics

- Chatbot must be designed within VoiceFlow


Define

Brand Goal

Shareholders expressed the primary goal of the chatbot was to reduce call center burden. By leveraging a chatbot to resolve simple user queries, call centers could focus efforts toward resolving complicated issues.


User Goals

Based on previously discovered user interview research, a typical SwiftSense.com user visits the site to achieve one or more of the following:


- Connect to a sales agent

- Connect to technical support

- Learn more about the SwiftSense's product and value proposition.



Design (Flows)

Based on the brand goals, user research, and user goals, I decided to design three primary flows: a sales flow, a technical support flow, and information flow. The sales and technical support flows would generate respective support tickets, while the information flow would provide information on SwiftSense’s products and share links to the SwiftSense blog.


In addition, these primary flows would be supported by four contextual flows: a hello flow, a catch-all flow, a human-hand off flow, and a goodbye flow.


Each flow would be designed to seamlessly connect with one another. The result would be a chatbot conversation that would end with either the user achieving their goal or, as a last resort, connect them to a human service agent to resolve their issue.


Hello Flow

Sales Flow

Technical Support Flow

Information Flow

Catch-All Flow

Human Hand-Off Flow

Goodbye Flow

Design (Dialogue)

"Swiftie" The SwiftSense Chatbot


I chose to give the SwiftSense chatbot a simple, friendly name to reflect the brand's voice and commitment to accessibility. Swiftie wants to make small business owners feel welcome, but understands that they have visited the site for a specific goal, not to chat with Swiftie. They may not know how to navigate the site or where to start, so Swiftie guides users with gentle efficiency.


Polite and cooperative. Swiftie wants to work with users rather than just tell them what to do. They are always polite and use language like “please” and cooperative phrases like “let’s” and “we.”


Extroverted, but not overwhelming. Swiftie is eager and excited to chat with users but writes simple, short responses whenever possible.


Goofy but task-oriented. Swiftie has a goofy sense of humor and loves to crack contextual jokes, but only when appropriate. It tones down its humor when a user may be frustrated, such as when they need to contact technical support or experience a no-match.


excel sheet #1: hello flow dialogue

excel sheet #2: sales flow dialogue

excel sheet #3: technical support dialogue

excel sheet #4: information flow dialogue

excel sheet #5: catch-all flow dialogue

excel sheet #6: human hand-off flow dialogue

excel sheet #7: goodbye flow dialogue

Prototypes & Testing

With my user journey maps and dialogue scripts completed, I created my first prototype within Voiceflow. After training Swiftie's NLP to identify input entities and synonymous values, I began conducting usability tests by attempting to complete each flow from beginning to completion.


Usability testing revealed several flaws to the NLP's entity capture, such as it's ability to differentiate a user's first name from their full name. To solve this, I revised the dialogue flow so the chatbot would ask for the users first name during the hello flow and full name during the sales and technical support flows. By capturing separate entities, the chatbot could use the user's first name in conversation as well as repeat the user's full name when confirming their support ticket.


In addition, the chatbot had difficulty reiterating a user's request ticket in some cases. For example, when a returning customer but did not have access to their nine-digit product code, resulting in the chatbot reporting a [nil] product code value in the support ticket. To solve this, I mapped additional sub flows within sales and technical support flows to account for these variables.


hello flow prototype

sales flow prototype

technical support flow prototype

information flow prototype

catch-all flow prototype

human hand-off flow prototype

goodbye flow prototype

Delivery

With the chatbot completed, users could submit request tickets directly to appropriate SwiftSense agents, therefore reducing contact center burden.