Five-Minute Lead Response: A Real Estate Lead-Routing Build

Real estate leads decay fast. A buyer who fills out a Zillow form at 9:47 PM has typically contacted three other agents by 9:52. If your response time is measured in hours, you're not competing — you're paying for warm leads that someone else closes.

This is a breakdown of how a Catalyst lead-routing build comes together for a small real estate team. Not a fabricated case study — the actual decisions, the integrations, where humans stay in the loop, and what a working handoff looks like.

The Problem We're Solving#

A typical two-to-five agent brokerage gets leads from four or five places: Zillow Premier Agent, Realtor.com, their own website, Facebook lead forms, and referrals dropped into email or text. Each source has its own format, its own notification, and its own follow-up rhythm. The agent's inbox becomes the de facto CRM, which means leads slip.

The symptoms are predictable. Response times stretch past an hour. Lower-quality leads (tire-kickers, wrong price range, investors browsing) get the same energy as serious buyers. Nothing gets logged consistently, so there's no honest read on which source actually produces closings versus which one just produces noise.

The goal of this build isn't to replace the agent. It's to make sure every lead gets a response inside five minutes, gets a basic qualification pass, and lands in one place with enough context that the agent can pick up the conversation without re-reading anything.

Step One: Unify the Intake#

The first piece is collapsing every source into a single stream. We use a workflow tool (typically Make or n8n, depending on the team's existing stack) with dedicated triggers for each channel:

• Zillow and Realtor.com leads route via their email parser or partner API into a webhook.
• Website forms post directly to the same webhook.
• Facebook lead forms connect via their native integration.
• Referrals get a simple form the agent fills on their phone (or a forward-to-parse email address).

Everything normalizes into the same record shape: name, phone, email, source, property of interest, timestamp, raw message. That normalization is unglamorous but critical. Every downstream step assumes a clean schema, so if you skip this you spend the rest of the project writing exceptions.

At this stage we also do duplicate detection. If the same phone number came in from Zillow yesterday and the website today, the system flags it as a returning lead rather than creating a fresh record. Agents hate working duplicates, and CRMs full of them are how teams lose trust in their own data.

Step Two: Instant Response, Calibrated to Source#

Within sixty seconds of a lead hitting the pipeline, the system sends a first-touch response. This is where most automation builds get it wrong — they send a generic "Thanks for your interest!" that sounds like a robot and trains the lead to ignore future messages.

We build source-aware templates instead. A Zillow lead asking about a specific listing gets a message that references that property by address and asks one qualifying question ("Are you looking to tour this week, or still in the early research phase?"). A website contact form submission gets a different opener. A Facebook lead form, which usually has lower intent, gets a softer touch.

The messages go out via SMS through Twilio (or the team's existing texting platform) because text response rates outperform email by a wide margin for real estate. Email goes out as a backup with the agent CC'd so they have a paper trail.

We always include the agent's real name and a real callback number. Leads can tell when they're talking to a system, and the goal is to buy the agent the five to fifteen minutes they need to personally reply — not to pretend the bot is the agent.

Step Three: Qualification Without Annoying the Lead#

This is the part that requires the most judgment. You can't fire twelve qualifying questions at someone who just clicked a listing. But you also can't hand the agent a lead with no context.

The build uses a short back-and-forth — usually two or three exchanges — driven by an LLM with tightly scoped prompts. It captures three things: timeline (touring this week vs. months out), financing status (pre-approved, talking to a lender, cash, undecided), and price range fit relative to the listing they asked about.

A few caveats worth being honest about. The LLM occasionally misreads sarcasm or short replies. It will sometimes mark a serious buyer as low-intent because they typed "just looking." That's why qualification outputs are advisory, not gatekeeping. Every lead still reaches the agent. The qualification just determines priority and what the agent sees first.

We also cap the conversation. After three exchanges or any signal that the lead wants to talk to a person, the bot hands off explicitly: "I'll have [Agent] call you in the next few minutes." Then it pages the agent.

Step Four: Routing and Handoff#

For a solo agent, routing is simple — every lead goes to them. For a team, the rules get interesting. We typically build routing logic around three factors: geography (which agent covers which zip codes), specialty (luxury, first-time buyers, investment), and current load (who's already juggling ten active conversations this week).

The handoff to the CRM is where the build actually pays off long-term. Whether the team uses Follow Up Boss, kvCORE, HubSpot, or a Google Sheet they refuse to give up, the system writes a complete record: lead details, source, the full text of the qualification conversation, an intent score, and a suggested next action. The agent opens one screen and sees everything.

Notification goes via the agent's preferred channel — usually a Slack message or a push notification from the CRM's mobile app. The notification leads with the one thing that matters: "Hot lead, asked about 412 Oak St, pre-approved, wants to tour Saturday." Not a wall of fields.

What This Build Actually Costs and Delivers#

A build like this typically takes two to four weeks depending on how many sources need integrating and how clean the team's existing CRM is. Monthly running costs land in the $80-200 range for a small team — Twilio messaging, LLM API calls, and the workflow platform subscription.

What you should realistically expect: first-response time drops from hours to under five minutes consistently. Agents stop missing leads on weekends. Qualification context shortens the first call. You get honest source-by-source reporting because every lead is now logged the same way.

What this doesn't do: it doesn't close deals for you, it doesn't replace nurturing long-term leads, and it won't fix a team that doesn't return calls. Automation amplifies the system underneath it. If the underlying follow-up discipline is weak, you'll just route bad responses faster.

There are also failure modes to plan for. Twilio outages happen. LLMs sometimes generate replies that need to be caught by a safety check before sending. Zillow occasionally changes its email format and breaks the parser. A working build includes monitoring and a fallback path — usually a direct SMS to the agent with the raw lead — so nothing gets dropped silently when something breaks.

If you're running a real estate team and your lead response time is the thing holding you back, this is exactly the kind of system we build. Walk through your current setup with us on a discovery call and we'll tell you honestly whether automation will move the numbers or whether the bottleneck is somewhere else.