The Saturday 3pm portal lead nobody claims
A buyer taps a listing on Zillow or realtor.com. Every agent on your team is showing a house. By the time anyone's free, the lead has called the next name on the list.
The short version
4 things that decide this
- 01Weekend afternoons are your highest-traffic window and your lowest-coverage window at the same time. Agents are in the field, not at a desk.
- 02In a secret-shopper test of the top 74 US brokerages, 41% never answered the website inquiry at all, and only 9% answered inside five minutes (Roof AI, November 2025).
- 03An answered Saturday isn't more agents on call. It's an intake layer that answers in a minute, qualifies the buyer, checks whether they already work with someone, and books the showing to whoever's actually free.
- 04Price, offers and contract terms still go to a licensed agent, every time. That's where the software's job stops.
3:07pm, and every agent is already booked
Picture your team's Saturday. Three agents are out on showings, one's driving between them, and the office is empty because nobody staffs a desk on a weekend. A buyer scrolling Zillow on their phone taps "request a tour" on a listing they like. It lands in your CRM at 3:07pm.
Your round-robin does what it's set up to do. It pings the team. And it keeps pinging, because nobody picks it up. One agent is walking a buyer through a kitchen and can't check their phone. Another sees the notification, means to call back after the showing, then forgets by the time they're driving to the next one. A third assumes someone else already grabbed it.
It isn't a staffing problem. You've got enough agents; what you're short on is someone free at exactly the moment a buyer wants to talk. One operator on a real estate forum put it plainly. Every lead triggers a notification: "unclaimed lead, whatever source it's from." It sits there until someone has the time and the reminder to act.
Most brokerages never pick up the phone at all
Roof AI secret-shopped the top 74 US brokerages by sending a website inquiry to each one and timing the response. 41% never answered the inquiry at all. Only 9% answered inside five minutes, the window most buyers will actually wait before moving to the next listing. And 91% of the brokerages that did respond routed the lead into a static form with no live follow-up behind it (Roof AI, November 2025).
That test measured the top of the market. Even the highest-volume brokerages in the country miss four out of ten inquiries. Your three-agent team with no ISA desk isn't beating that average on a Saturday. And a missed lead doesn't just disappear. It goes to the next name on your buyer's list, usually another agent on the same portal page.
None of this is about effort. Your agents are doing exactly what you're paying them to do: showing houses. It's a structural problem. A round-robin assumes someone is free to claim the ping, and on the day your leads peak, nobody is.
What an answered Saturday actually looks like
You don't need a fourth agent on call every weekend. Picture an intake layer instead, one that picks up the moment the lead lands, by text, phone or the form itself. It answers in under a minute, not whenever someone's next free.
It asks what a good ISA would ask. What's your timeline? Are you pre-approved? And the question that matters most: do you already work with an agent? A yes routes you back to your own agent, never poached. A no gets your showing request booked straight to whoever's actually on duty.
Every detail gets written back to your system as it happens: source, notes, the qualifying answers. It lands in Follow Up Boss, BoldTrail, Lofty or whatever CRM your team runs. Nobody claims the booked showing inside fifteen minutes? It re-routes on its own, instead of sitting in an unclaimed queue until Monday. You're not adding an inbox for someone to babysit. This closes the gap between the lead landing and a qualified person knowing about it.
None of this replaces your agents. It buys them the minutes they don't have on a Saturday. Once a conversation turns to price, an offer or contract terms, it goes straight to a licensed human, full stop. And nobody gets an automated text without consent captured first. Its job is to get a real person into the thread fast, never to run the negotiation.
- 01Text, phone and web-form intake answered inside a minute, any day of the week.
- 02Qualifies timeline, pre-approval and whether the buyer already has an agent.
- 03Books the showing request to the agent actually on duty, not whoever's free to check a phone.
- 04Writes source and notes to Follow Up Boss, BoldTrail, Lofty or whatever you run, and re-routes at fifteen minutes unclaimed.
- Lead landsText, phone or web form, answered inside a minute, any hour of the weekend.
- QualifyTimeline, pre-approval, and whether you already work with an agent.
- Book and routeShowing request goes to whoever's on duty; re-routes if unclaimed at 15 minutes.
- Price, offer or contract talkHanded to a licensed agent, every time. No exceptions.
Everything above the last row runs on its own. The last row is a person's job, on purpose.
Some of the systems we have shipped
Related questions
01How fast should a brokerage actually respond to a portal lead?+
Inside five minutes, if you want a meaningful shot at the conversation. Only 9% of the top US brokerages managed that in a recent secret-shopper test. Every hour past that window, the odds the buyer has already moved on climb.
02Will the AI ever talk price or negotiate an offer with a buyer?+
No. It answers, qualifies and books the showing. Once a lead asks about price, an offer or contract terms, it hands off to a licensed agent.
03What happens if the lead already has a buyer's agent?+
It asks directly, and a lead who already has representation gets routed back rather than pursued. That question is part of the qualifying script, not an afterthought.
04Does this replace our round-robin or sit alongside it?+
It sits in front of it. Your round-robin still decides who's on duty. The intake layer just makes sure someone qualified knows about the lead inside a minute, not whenever a notification gets noticed.
