DESIGN & TONE FOR CX AI
05 / 05

qualtrics assist

Scope
Conversation, model, product design
Company
Qualtrics
For
56.3K+ CX analysts, monthly
With
UXR, PM, data science, product science

Personalizing how an AI assistant speaks to CX teams.

The tone menu in Qualtrics Assist’s original design wasn't wrong, but it just wasn’t ours.

Witty. Confident. Empathetic. Six options handed to users that never once looked to Qualtrics for wit. Our users were CX professionals at major companies, seeking deeper insights from customer feedback. Why would they choose a tone we didn’t have?

Other assistants offered options to customize tone, length, and formality. I saw the potential for personalization and later, to align the tool to users' brand voice.

Original tone settingsClick to enlarge
witty
Didn't match a product built for serious, professional work
confident
Implies its opposite exists elsewhere; a bad signal for a tool meant to help people trust their own data
personable, engaging, direct
Voice traits masquerading as tone
empathetic
Only one that held up, but it's standard

I led end-to-end design across
content, conversation, and interaction.

I designed the voice and tone framework, personalization sketches, and AI response logic.

what we heard

The literature backed up a pattern I kept seeing anecdotally: an AI with no defined character undermines trust about as fast as one that oversells its own abilities (Dorton & Harper, 2022)Dorton, S. L., & Harper, S. B. (2022). A naturalistic investigation of trust, AI, and intelligence work. Journal of Cognitive Engineering and Decision Making, 16(4), 222–236..

One of our users oversaw consumer insights and used Assist to make sense of customer feedback. In their words,

I need clear summaries to reduce cognitive load and help stakeholders understand the main issues. But the responses are often unclear or lack nuance—I have to ask, ‘in human speak, what are people saying about this category?’
— CONSUMER STRATEGIST, MAJOR MEDIA COMPANY

AI guidelines from scratch

I ran our existing product voice against NN/g's four tone dimensions. If we weren't funny or irreverent elsewhere in the product, adding a settings option to be either was a trust risk.

FormalCasual
Mostly conversational, but never pushed toward casual
FunnySerious
Professionals doing real work, not much room for humor
RespectfulIrreverent
Respectful over irreverent
EnthusiasticMatter-of-fact
Matter-of-fact by default, enthusiastic only when there’s good news

Then I applied our voice and tone to the tool, defining formality and length too.

simple and clear
  • Simplify concepts, words, and ideas
  • Provide the right amount of info at the right time
  • Ease navigation across Qualtrics Assist in a logical, manageable way
honest and trustworthy
  • Establish trust for customers
  • Communicate candidly and ethically
  • All info should be honest and research-backed
helpful and accessible
  • Empower every user
  • Make sure everyone can use Qualtrics Assist, regardless of background or skill
consistent and conversational
  • Talk to users naturally
  • Communicate concepts, words, and ideas the same in each formality
celebratory
  • Recognize success
  • Focus on achievement and actions
  • Emphasize that we’re celebrating them, not us
educational
  • Provide context and rationale
  • Don’t assume; focus on informing
  • Make it easy for them to take action
encouraging
  • Help them meet their goals
  • Point out benefits of taking the desired actions
  • Let them know why we’re giving them certain info, and anticipate any questions and needs
helpful
  • Emphasize info that’ll improve their experience
  • Explain our rationale and how to learn more
  • Be aware if we're interrupting
  • Pair CTAs with relevant info for easy decision-making
informational
  • Focus on the facts; avoid bias
  • Provide solutions or next steps
  • Refer to opportunities they might not know of
  • Provide tools for completing future tasks or avoiding similar issues
inspiring
  • Highlight benefits to the person or organization
  • Emphasize that we can work to meet their goals
  • Focus on what they can do for success, no matter the outcome
supportive
  • Anticipate questions, re: their goals
  • Assure that we value their time and energy
  • Explain why we need certain info
  • Confirm privacy or security commitments
casual
  • Informal, but don’t use slang
  • Friendlier, can use exclamation points
  • Doesn’t adhere to strict grammar rules
neutral (default)
  • Straightforward, though still friendly
  • Neutral greetings like “Hi”
    • Avoid “Hey” / “Hey there” (too casual)
    • Don’t use too many exclamation points
  • Doesn’t adhere to strict grammar rules
formal
  • Straight to the point, but not particularly warm
    • Be sparing with $10 words
  • Definitely no exclamation points
  • Adheres to strict grammar rules
short
  • 1-2 sentences, with simpler structures
    • Simple
    • Simple + complex or compound
  • <300 characters
medium (default)
  • 2-3 sentences, mix of structures
    • Simple + compound
    • Simple + complex
  • <400 characters
long
  • 3-5 sentences, more complex structures
    • Compound
    • Compound + complex
    • Compound-complex
  • <500 characters
01 / 04
02 / 04
03 / 04
04 / 04

personalization sketches

Responses at every lengthClick to enlarge

what the team said

I sought feedback from the product scientist, lead designer, and a UX director, alongside a second research pass on how users reacted to informational vs. supportive tone in other AI features (automated summaries, AI-generated comments). The findings were consistent:

OBJECTIVITY >
Users strongly preferred the tool to be objective in speech
SENSITIVE TO TONE
"Cheery" or emotionally charged tones read as irritating
GET TO THE POINT
Summaries should tell them what they need to know, quickly
NO SLANG IN OUTPUTS
Concerns surfaced with the tool handling informal feedback
MEET THEM WHERE THEY ARE
No desire to be forced into one conversational style

post-feedback changes

Tone
celebratory
Not an option; it’s the default success tone
educational
For users who want to learn more about their insights
encouraging
Risked reading as emotionally charged
helpful
Cut from the sketches, brought back after team feedback, for first-timers out of their depth
informational
For users who just want the facts and next steps
inspiring
Risked being “cheery” and irritating
supportive
Risked being emotionally charged
Formality
casual
Too informal, lost nuance
neutral (default)
Not a user-facing setting
formal
No real use case
Length
Expanded the range and added two tiers.
brief
<500 characters; the major points in one paragraph
short
<750; more detail, but still simply the facts
medium (default)
<1,250; the right level of detail and simplicity
long
<1,750; detailed and a bit more complex
extended
<2,500; extremely detailed, with all the complexity

in the product

I wrote, designed, and prototyped the end-to-end interaction logic for this AI voice settings flow.
This prototype goes from customization to how the setting changed the output.

Personalization flow
Formality
Left the UI entirely; Neutral became the fixed default
Tone
Redesigned the checkboxes to a single dropdown, so each reply is consistent
Length
Changed from radio buttons to a five-tier dropdown, each with 1-line descriptions
Navigation
AI voice settings joined the overflow menu
I really applaud her for her impact to Assist—which is pushing the designs forward [and] generally punching well above her level. Out of all the designers I have worked with, Sarah is by far the strongest designer, systems thinker and problem solver.
— LEAD DESIGNER, QUALTRICS ASSIST

(re)setting guidelines to criteria

What shipped in 2024 was a style guide of traits. Revisiting it this year, I rebuilt it as a scoring rubric of three criteria with a four-point scale.

Criterion
4Exemplary
3Meets
2Partial
1Misses
tone
Checks against
Tone settingHonest and trustworthy
Matches the selected tone exactly, staying objective about the user’s data
Matches the selected tone, with minor drift in one sentence
Mixes tones, or adds emotion the data doesn’t support
Wrong tone, or cheery and emotionally charged about the data
naturalness
Checks against
Neutral formalityClear and consistentActive voice
Reads like a knowledgeable colleague: “Hi,” active voice, consistent terms
Natural, with one stiff or overly casual phrase
Noticeably robotic or chummy (“Hey there!” or stacked exclamation points)
Reads machine-made or slang-heavy; terms shift mid-response
appropriateness
Checks against
Length tierSimple, striving for brevityAccessible and helpful
Within the length limit, right detail for the output, ends on a next step
Within the limit, but slightly over- or under-explained
Over the limit, or buries the main point
Off-task, misleading, or ignores the length setting
Model evaluation criteria, built from the original AI voice framework

I’d left Qualtrics before Assist reached EA but supported its journey there with the UXR lead. About half of customers eagerly adopted the tool in their workflows, and they asked for more customizable settings and sentiment analysis. Both were opportunities I'd have loved to take on.

In retrospect, this work—more than any single guideline—is the throughline in how I think about AI voice today.

FROM THE BEGINNING
weekly job summary
Read →