archie chatbot
the problem
Customers had to email Support or their implementation manager for answers. Many tasks had to be done one by one because there was no bulk editing. Custom reporting, one of our most requested features, meant relying on external tools or our team.
the research
I onboarded and interviewed customers to see where Archie added the most value. The findings showed which view each persona preferred. Owners wanted full screen for reporting, while production managers and purchasers wanted a side panel for bulk tasks and quick lookups.
my role
User research, product design, frontend development
the team
1 designer, 2 engineers, 1 AI specialist
the timeline
1 month
the tools
Figma, Claude code, Posthog
the goal
Let customers answer questions, update data in bulk, and create reports inside the product, and use real customer prompts to find gaps in our toolsets.
the solution
Two views available on every page: full screen and a context-aware side panel. Familiar chatbot patterns, so there’s nothing new to learn. Example prompts tailored to each user’s role and permissions
the impact
Customers could get answers, bulk updates, and reports in the product instead of going through Support or external tools. Reviewing conversations also exposed gaps in our toolsets that engineers then closed, improving the underlying product.