Designing an AI assistant for Freedom Mortgage.

Freedom Mortgage loan agents lost time searching documentation and escalating routine questions. I led research and design for an AI assistant that reduced time spent on documentation-heavy questions by 82% and saved each agent 2.3 hours a week.

Role
UX researcher + designer
Team
3 designers, 1 PM, 2 devs, 5+ stakeholders
Tools
Figma, FigJam
Timeline
Apr – Sep 2025
The final approved Halo assistant prototype: splash, chat intro, thinking state, response, and error screens, marked ready for dev.
The final Halo assistant, built around natural-language questions in the agent workflow.
Overview

Routine questions were slowing down the floor.

Loan agents spent hours answering repeat questions, searching documentation, and moving between disconnected systems. When a workflow broke, they often had to stop and ask a manager for help.

The goal was to give agents one place to find reliable answers without adding another tool to manage. I led the user research, then turned what we learned into prototypes and final designs.

Research

I started on the call-center floor.

We shadowed loan agents through their daily work and watched where the process slowed down. Three patterns kept appearing.

Broken workflows caused escalations. Agents followed rigid paths and stopped when something unexpected happened. Even small errors could require a manager.

Disconnected tools wasted time. Agents moved across more than four systems while trying to answer a single borrower question.

Unclear feedback increased risk. Agents had to remember complex rules without enough guidance from the product, which raised stress and created room for compliance mistakes.

Personas

The assistant had to prevent breakdowns, not create another one.

I turned the research into two personas. Jordan, a Loan Advisor, needed fast answers without leaving the task at hand. Rachel, a Manager, needed fewer repeat questions and more confidence that agents were following the right process.

Both pointed to the same design requirement: the assistant had to fit the existing workflow and help agents recover when it broke.

Persona cards for Rachel Sinclair, a Loan Advisor Manager, and Jordan Carter, a first-year Loan Advisor.
Jordan and Rachel represented the agents asking questions and the managers handling escalations.
Competitive research

I studied how mature assistants handled the details.

We compared assistants from Chase, Rocket Mortgage, and Intercom, looking closely at interaction patterns, motion, and tone of voice. I used ChatGPT to help organize the patterns, then translated them into recommendations for button placement, chatbot copy, and response behavior.

Competitive teardown of AI chat motion and animation patterns, including open, close, bot-typing, message-entry, and hover states.
The patterns that shaped the first interaction model and tone.
Design

I kept the first ideas cheap to change.

I sketched several layouts before moving into Figma. That let the team compare directions quickly while the structure was still easy to change.

I built the strongest direction with the existing design system, then turned it into an interactive prototype for user testing and stakeholder walkthroughs.

Hand-drawn wireframe sketches exploring the executive dashboard layout, including trends, chat, and graph arrangements.
Early sketches kept the layout flexible before the direction moved into the design system.
Testing

People wanted to type, not tap.

The first test produced a clear signal. People disliked choosing from buttons inside the chat and preferred asking questions in their own words.

We removed the buttons and focused the MVP on natural-language input. I folded feedback from users, marketing, and brand into the final prototype, then worked with developers on a markup guide so the build matched the design.

The Halo chat interface across four states, showing knowledge-base result buttons and typed natural-language queries.
The tested direction replaced response buttons with natural-language input.
Impact

Less time on paperwork, more time with borrowers.

82%
Reduction in time spent on documentation-heavy questions.
Each agent also saved 2.3 hours a week for higher-value borrower work.

The assistant gave agents a faster path to reliable answers inside their workflow. That meant less time searching documentation and more time helping borrowers.

The final approved Halo assistant, demo-ready and marked ready for development.
The final assistant, prepared for development and pilot rollout.

Ready to ship something measurable?

LinkedIn