Don't botch the bot: Designing interactions for AI
Summary
It seems like every company is adding a conversational AI chatbot to their website lately, but how do you actually go about making these experiences valuable and intuitive? Savannah Carlin will present a case study on a conversational AI chatbot—Marqeta Docs AI—that she designed for a developer documentation site in the fintech industry. She will share her insights, mistakes, and perspectives on how to use AI in a meaningful, seamless way, especially for companies like Marqeta that operate in highly regulated industries with strict compliance standards. The talk will use specific examples and visuals to show what makes conversational AI interactions uniquely challenging and the design patterns that can address those challenges. These include managing user expectations, handling errors or misunderstandings within the conversation, and ensuring that users can quickly judge the quality of a bot’s response. You’ll gain a deeper understanding of the intricacies involved in designing interactions for AI, along with practical advice you can apply in your own design processes. Take-aways What to consider before you add AI to your product to ensure it will be valuable, usable, and safe for its intended workflows The interactions that are unique to conversational AI experiences and the design patterns that work for them Common challenges in designing conversational AI experiences and how to overcome them
Key Insights
-
•
Defining a clear and specific primary use case is crucial before starting any generative AI chatbot project.
-
•
High-quality, thoroughly reviewed training data is foundational to delivering accurate and useful AI outputs.
-
•
Initial state messaging must clearly frame what the chatbot can and cannot help with to reduce irrelevant or off-topic queries.
-
•
Loading indicators for AI text responses should be subtle, with progress reflected by text appearing rather than distracting animations.
-
•
Supporting efficient scrolling and prompt review is vital since users frequently check and refine their inputs against often long answers.
-
•
Error states in AI chatbots shift from traditional fixed errors to helping users write better prompts to get more relevant results.
-
•
Transparency about accuracy, AI limitations, and source citations builds user trust, especially in regulated domains like FinTech.
-
•
Providing users with prompt engineering guidance via documentation significantly improves the quality of chatbot interactions.
-
•
Accessibility considerations, like keyboard navigation and screen reader compatibility, must be integrated from the start, especially given the large text outputs.
-
•
Chatbots can reduce customer support friction and encourage users to ask questions they might not have otherwise, enhancing user engagement with the product.
Notable Quotes
"If you have any doubts about the quality of the training data, do not proceed."
"You want to assist people in framing the interaction and setting their expectations correctly so they know how to be successful."
"The biggest difference with error states in AI bots is helping people write prompts effectively, not just recovering from simple failures."
"Loading text itself is a loading indicator; the letters appearing show progress better than jumpy animations."
"People often forget what they wrote and then want to check their prompt again before refining it."
"Every output should have at least three source links, almost like citations in a research paper."
"We had to be very careful about accuracy because we're in FinTech and compliance is critical."
"People started asking questions to the bot that they wouldn’t have taken the time to email about."
"It’s really important to be clear and transparent about what the tool is good at and what it’s not good at."
"Accessibility testing included making sure everyone could navigate it using a keyboard alone."
Or choose a question:
More Videos
"Flexible and staggered schedules help people not get burned out."
Lavy Kumar Kat Temple Shan Sebastian Tara Jensen Jenn ChouFuture of Work
June 9, 2021
"Our user base is really fun and complex, with different preferences that require nuanced automation approaches."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"Conjoint analysis reveals how consumers make choices by examining trade-offs they are willing to make."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
"Closing the distance is about connecting not only with customers but also between cross-functional team members."
Monty HammontreeThe Future of UX Research
December 3, 2020
"The designers started to send notes of thank you to the ex members of the design ops team for making their life easier."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"You can own the infrastructure that allows knowledge to flow but you can't actually own the knowledge itself."
Kate TowseyAsk Me Anything (AMA) with Kate Towsey
April 2, 2025
"Visualizing data in a way executives can interpret is key to shifting from I think to I know."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Lack of confidence caused by unlabeled or difficult controls often leads assistive tech users to give up on purchases."
Sam ProulxOnline Shopping: Designing an Accessible Experience
March 28, 2023
"For screen reader users, you often need to build entirely new prototypes using systems like Microsoft Word or Google Docs to convey semantic information."
Sam ProulxPrototype Reviews, People With Disabilities, and You
October 1, 2021
