← All posts

Workflows

When nobody owns the lead: routing gaps on busy teams

A paid ad fires at 10am, three agents are online, and two hours later the lead still hasn't been contacted — here is what breaks and how to fix it.

A paid Facebook ad fires at 10:04am on a Tuesday. The lead fills out the form, gets an auto-reply confirming someone will be in touch, and then waits. Meanwhile, the notification lands in the team group chat. Two agents see it. Each assumes the other is handling it. The third agent is showing a property and has her phone on silent. By 12:15pm — two hours and eleven minutes later — the lead fills out the same form on a competitor's site.

Routing failure is not an exotic edge case. On any team running more than a handful of agents, it happens multiple times a week. The fix is not adding more Slack pings.

Why the group notification model fails

Sending a lead alert to a shared channel puts everyone in a bystander position. When responsibility is diffuse, it belongs to no one. Each agent reads the message in the context of whatever else they are doing and calculates — usually incorrectly — that someone else has it covered. This is especially common on teams where agents operate autonomously and there is no dispatcher or inside sales person actively watching the queue.

The problem compounds when leads come in from multiple sources — paid ads, the website form, Zillow, inbound text, inbound call — and each channel lands in a different place. There is no single queue. There is no owner.

What a routing workflow actually needs to do

A lead routing workflow has three jobs: assign the lead to exactly one agent, confirm that agent has accepted responsibility, and escalate if they have not acted within a defined window.

Assignment logic can be simple: round-robin, geographic zone, lead source, or agent capacity score. It does not need to be sophisticated to work. What matters is that the system writes one agent's name to the lead record the moment the lead arrives — not after a human decides.

Confirmation is the step most teams skip. The workflow should send the assigned agent a direct notification with a one-tap accept or reassign option. If the agent does not confirm within, say, 15 minutes, the lead automatically reassigns to the next agent in the rotation and the original agent is logged as unavailable. This creates accountability without requiring a manager to monitor anything in real time.

Escalation is the safety net. Say a team gets 40 leads a week. A handful will fall into edge cases: the first and second assigned agents both miss the window, the lead source is unfamiliar, the lead came in at 11pm and everyone was offline. A good workflow handles each scenario with a predefined rule rather than leaving it to chance.

Building the assignment logic

Before writing any automation, map the actual lead sources and where each one lands today. This audit step — sitting down with the team and tracing each source channel to its current destination — almost always surfaces a few channels that are going nowhere at all. A website form that emails a general inbox nobody monitors. A Google Business Profile message that nobody knew was turned on.

Once the sources are mapped, the assignment logic can be built as a simple decision tree. The trigger is the lead arriving. The first branch is lead source or geography, if the team routes that way. The second branch is agent availability — is anyone marked active right now? The third branch is the round-robin or weighted rotation among available agents.

This logic runs in the same automation layer that already handles the auto-reply to the lead. The assignment, the agent notification, and the confirmation timer all fire from the same trigger event. No separate systems, no manual steps.

What changes operationally

The visible change for agents is that they stop receiving shared-channel alerts and start receiving direct, personal assignment notifications. The notification tells them the lead's name, source, and what they need to do in the next 15 minutes. It is specific rather than ambient.

For the team lead or broker, the change is that the CRM now shows who was assigned to every lead, when they accepted, and when they made first contact. This is auditable. If a lead goes cold, it is possible to see exactly where the handoff broke down rather than guessing.

Routing data also reveals patterns that are invisible in the current model. Which agents are consistently accepting their assignments? Which lead sources have the longest time-to-first-contact? Which time windows have the most escalations? These questions are answerable once the routing workflow is logging every step.

Where to start

Pick one lead source — ideally the highest-volume one — and trace it from the moment a lead submits their information to the moment an agent first contacts them. Write down every step, who touches it, and how long each step takes. That map will show you exactly where routing breaks down. Build the assignment and confirmation logic for that one source first, get it stable, then extend it to the others.

Want this appliedto your team?Ask us.

Or write to ushello@realestateaigroup.com

Skip the reading — a 30-minute call is enough to tell you what’s realistic.