UX/UI DESIGN · REAL ESTATE TECH
Mobile Dialer: Designing the Calling Tool Agents Would Actually Use
For a real estate agent, the dialer is not a feature. It is the engine of the entire day. Leads only turn into appointments through conversations, and conversations start with a dial. The more an agent calls, and the faster they call, the more pipeline they build.
So the dialer should have been the most-used tool in the app. Instead it was the one agents went out of their way to avoid.
The mobile dialer ran on a single line only. It could not record calls or summarize them. It dropped close to a third of its connections. It hid its own Start Dialer button on smaller phones, and once the call modal was dismissed there was no way to bring it back. Agents reacted the way people always react to a tool that fights them. They stopped using it. They dialed from desktop, called straight from their personal phones, or paid out of pocket for third-party tools like Dialpad.
That is what made this closer to a 0 to 1 than a redesign. The product technically existed. In the actual workflow of the people it was built for, it did not. The job was not to refresh a tool agents used. It was to design the version they would choose for the first time.
This is the part that made it hard. Winning back a user who has already written your product off is a different problem than improving one they like.
The brief was a single question:
"How might we optimize the web and mobile dialer experience to increase agent productivity, reduce friction in lead engagement, and ensure we're leveraging modern dialing technologies to drive better connection outcomes?"
That gave me a real tension to design against:
Rebuild enough trust that agents would open the dialer again
Without piling a relearning curve onto the agents who had grudgingly stuck with it
And make calling feel fast, reliable, and worth doing, instead of one more thing that might freeze mid-dial
The deeper truth under all of it: agents were not avoiding the dialer because they did not want to call. Calling is how they get paid. They were avoiding it because the tool made the single most repeated moment of their day harder than picking up their own phone.
I ran this as a design sprint, which meant earning the right to design before drawing a single screen. Before committing to any direction I separated three things the team had been treating as one: what we were assuming, what we actually knew, and what we still needed to find out.
Surfacing the assumptions first
A tool with near-zero adoption collects a lot of theories about why. I pulled those theories into the open and had the team vote, so we were not about to redesign on top of beliefs nobody had tested.
Turning the riskiest assumptions into research
I converted those assumptions into eight research areas, each with its own interview questions, so the conversations were aimed at the things we were least sure about rather than the things we already believed.
Talking to the people who live in the dialer
I interviewed active CINC users across the roles that actually touch the tool: a broker and site owner, an ISA who works around 150 leads a day, and a realtor and site owner who had already left the native dialer for Dialpad. Different tech comfort levels, different workflows, same product.
What came through, over and over
Adoption was a trust problem, not a feature gap. People were not asking for one missing button. They had quietly routed around the tool entirely, to desktop, to their own phones, to Dialpad.
No recording or AI summary on mobile gutted the value. The one thing brokers most wanted for coaching and follow-up was the one thing the mobile dialer could not do.
Reliability had broken confidence. Freezes, dropped calls, and roughly a third of connections failing taught agents not to trust it with a live lead.
There was nowhere to disposition or take notes between calls. Once a call ended, the workflow fell off a cliff.
It was hard to even find or build a call list, especially on a phone, especially on the go.
Agents wanted to move between desktop and mobile without losing their place in the middle of working a lead.
With research in hand, I reframed everything from the user's point of view and got the team to prioritize. This is where a sprawling pile of complaints became a short list of things worth solving.
The problems
1. Audit the existing experience. I mapped the current dashboard flow - where agents made unnecessary decisions, where context was missing, and where simple actions took too many steps.
2. Identify the high-leverage gaps. Rather than redesigning everything, I prioritized the follow-up section as the highest-friction, highest-value area - the place agent productivity either succeeds or stalls every single day.
3. Prototype in Figma. I built a clickable prototype of the new dashboard and detail view, focused on hierarchy, type-level transparency, and inline action.
4. Refine the panel structure. I worked through several layout iterations on the stat panels before landing on the two-panel approach, testing which metric combinations gave agents the clearest read on pipeline health at a glance.
Before - Dashboard Four equal-weight stat panels competed for attention. The follow-up section listed Today / Upcoming / Past Due as raw counts, with no signal about what kind of action each required.
After - Dashboard Two modernized lead panels anchor the top. Each follow-up category now breaks down by type - calls, texts, emails, meetings so agents know exactly what their day demands before they tap anything.
After - Follow-up detail Tapping any category opens a full list with filter and type controls, lead name, task description, due date, an inline action button (Call / Text / Email), an edit link, and a mark-complete checkbox - one uninterrupted flow where agents used to be forced out of the app entirely.
The best dashboard redesigns don't just look cleaner, they make the right next action obvious. This project was about removing the cognitive load between an agent opening the app and knowing exactly who to contact, how, and when.
A strong UX designer finds those gaps in an existing product and closes them precisely, without burning the whole thing down to do it.
Because the redesign is pre-launch, the real proof comes at deployment. The metric I'll be watching is follow-up completion on mobile - whether agents stop defaulting to desktop and third-party to-do apps and start trusting the app to run their day. That's the behavior the whole redesign is built to change.