Go back to portfolio

AiListz · Web

AiListz: 90% Fewer Support Requests From First-Time Users

Designed the web platform’s content-generation, persona, plagiarism-checking and in-product guidance workflows.

Role
Product Designer
Scope
AI content-creation platform
Focus
Web
Designer
Gideon Awolesi
AiListz: 90% fewer first-time support requests case study cover

My contribution · AiListz

AI content-creation platform

The work used familiar, editable controls alongside guided prompts, so first-time users could understand the tools without losing control of the output.

90%
fewer first-time support requests

What I owned

  1. 01Mapped first-use onboarding, brand-style setup, content generation and plagiarism-checking flows.
  2. 02Designed conversational help and in-context explanations for unfamiliar AI decisions.
  3. 03Used shared interaction patterns across the editor, personas and advanced controls.

Overview

Details

  1. Role: Product Designer for the web platform.
  2. Objective: Help content creators draft content, check for plagiarism, switch personas, and use several AI tools without learning a different workflow for each one.

The validation focused on:

Make beta onboarding clearer for first-time users.

Reduce support requests with in-context guidance and clearer tool labels.

Test if conversational guidance made users more confident without taking control away from them.

User research

I interviewed bloggers, marketers, and developers about how they used AI tools and where the work got confusing.

  1. Onboarding: Technical language made a lot of AI tools hard for first-time users to understand.
  2. Disconnected tools: Each feature worked on its own, so none of them supported a complete content workflow.
  3. Unclear output: People couldn’t always tell why the product made a recommendation.

The interface used guided prompts and conversation to introduce each tool, and kept the settings and output controls visible.

AiListz: 90% fewer first-time support requests, User research, figure 1

Low-fidelity sketches

I mapped onboarding, brand-style setup, content generation, and plagiarism checking.

The wireframes showed where people could get stuck, especially when switching between personas.

AiListz: 90% fewer first-time support requests, Low-fidelity sketches, figure 1
AiListz: 90% fewer first-time support requests, Low-fidelity sketches, figure 2

Usability testing and refinements

Small groups tested the product over several rounds. Their feedback led to clearer menu labels, shorter prompts, and help with choosing a template or persona.

Menu structure: Each tool, including image generation and speech-to-text, used the same naming and navigation pattern.

AiListz: 90% fewer first-time support requests, Usability testing and refinements, figure 1

High-fidelity prototypes

I applied the visual system and rewrote placeholders in plain language.

A shared design system gave the plagiarism checker, persona switching, and text editor the same interaction patterns.

I put advanced controls inside collapsible sections, so new users only saw them when they needed them.

AiListz: 90% fewer first-time support requests, High-fidelity prototypes, figure 1

Context and challenge

Bloggers, marketers, and developers often had to move between separate AI tools for drafting, plagiarism checks, and persona changes. The product brought those jobs into one conversation-based interface, and the controls stayed visible.

AiListz: 90% fewer first-time support requests, Context and challenge, figure 1
AiListz: 90% fewer first-time support requests, Context and challenge, figure 2

Primary goals

  1. Guidance: Explain each tool at the point where a new user needs to make a decision.
  2. Shared patterns: Keep the same interface structure when new tools, such as image generation and speech-to-text, are added.
  3. In-product help: Answer common questions next to the relevant setting or output.
AiListz: 90% fewer first-time support requests, Primary goals, figure 1

AI design principles and conversation design

Show, don’t tell

Guided prompts and tooltips: Explanations appeared next to plagiarism checking, persona switching, and other unfamiliar decisions.

AiListz: 90% fewer first-time support requests, Show, don’t tell, figure 1
AiListz: 90% fewer first-time support requests, Show, don’t tell, figure 2

Conversational UI

Chat interface: Users could ask for help in natural language and get suggestions or a short demo of the feature, so they didn’t have to search through a long FAQ.

AiListz: 90% fewer first-time support requests, Conversational UI, figure 1

Transparency and user control

  1. AI explanations: Short summaries showed why the product suggested content or flagged possible plagiarism.
  2. Personalisation: Users could set the brand voice, tone, and style, and then edit the generated result.
AiListz: 90% fewer first-time support requests, Transparency and user control, figure 1

What changed in the beta

Onboarding: Guided prompts and clearer navigation made the beta easier to understand.

Testing showed that people could find the main tools with less explanation.

Support: In-product guidance answered common questions where people needed it.

I designed the guidance and chat assistance to answer common questions before anyone needed to contact support.

Support requests from first-time users dropped by 90%, and beta sign-ups spiked.

User control: Explanations and editable settings made the AI output easier to inspect and correct.

Survey responses were positive about the in-product guidance and explanations.

User feedback: “It feels like I have a smart assistant guiding me, rather than wrestling with a confusing AI tool. I can see exactly what’s happening and why!”
AiListz: 90% fewer first-time support requests, What changed in the beta, figure 1
AiListz: 90% fewer first-time support requests, What changed in the beta, figure 2
AiListz: 90% fewer first-time support requests, What changed in the beta, figure 3

Need this level of detail in your product?

Work through the hard product decisions early.

If you’re a product team, that can mean a focused design, system, or prototype project. If you’re hiring, it’s a chance to look closer at how I work across research, interfaces, and code.