917 minutes was the average wait before a broker replied across 384 brokers in eleven states, and nearly half of the enquiries were never answered.
The enquiry lands. Nobody is awake. A portal notification at eleven at night, into an inbox that opens at nine. The buyer is still awake, still looking. For a six-person brokerage the morning starts with a pile, and the pile is read in the order it arrived.
By hand today
Portals and CRMs deliver the enquiry. None of them answers it. Follow Up Boss pulls Zillow and Realtor.com leads into a record for $69 a user a month; the UAE CRMs sell Bayut and Property Finder capture as their headline. Ingestion is bought. What lands in the record at eleven at night is still there, unanswered, at nine.
So the stage runs by hand, on volume:
“we get spammed with 100+ emails a day so pick up the phone or text”
Rose Higgens, on BiggerPockets
The enquiry comes four ways: a portal email, a message in the portal’s own inbox, a WhatsApp on a personal phone, a referral spoken aloud. Only the first two are systems.
What it costs you each week
917 minutes
The average wait before a broker replied, across 384 brokers in eleven states, secret-shopped. Nearly half of the enquiries were never answered at all.
Source: WAV Group with the Weichert Lead Network, Agent Responsiveness Study, 13 January 2014
Researchers posed as buyers. Verbatim: “48% of buyer inquiries were NEVER responded to.” Among the rest, “Average response time was 917 minutes (or 15.29 hours)”, with 1.5 call-backs and 2.07 emails after first contact. wavgroup.com
Two things to print beside it. The study is twelve years old. And Weichert’s own lead division co-produced it and is the contrast case inside it. The number is usually credited to the wrong people and the wrong year; it is this one.
Fast replies go with more conversations in every audit, and nobody has tested whether the speed causes it. This chapter builds on the correlation and says so.
The build
Open Claude Code. Ask for the reply. Gmail reads the portal email; Playwright opens the portal inbox with no API. The reply goes back the way it came. It asks permission and the three questions. HubSpot gets the person and the note within the hour, whatever the hour.
Open Claude Code in the engine folder. Connect the mailbox the portal writes to: for Gmail, the community server taylorwilsdon/google_workspace_mcp, with fifteen minutes budgeted for the Google Cloud OAuth setup (the GongRzhe Gmail server the lists name is archived). For a portal inbox with no feed, Microsoft’s Playwright MCP, headless, with a saved login. For the CRM, HubSpot’s own remote server at mcp.hubspot.com. Write reply.md once: an acknowledgement in your words, the consent line, and the next chapter’s three questions, when, how much, and whether the money is arranged. Then say what you want:
Every ten minutes, read the inbox for new portal enquiries, and read the
portal inbox in Playwright with the saved login. Tell me the total before
you do anything. Reply to each within the hour, on the channel it
arrived on: email by email, a portal message in the portal's own reply
box. Use reply.md, filled with the listing and their name, nothing else.
Never reply on WhatsApp. In HubSpot, create the contact if none matches
the email or phone, and add a note: the listing, what they wrote, when
it landed, when you replied. Leave the timeline, price range and
pre-approval fields blank until they answer; never fill them from a
guess. Report three counts each morning: landed, replied within the
hour, still waiting.
What comes back is a script, a schedule and three counts. At nine the morning starts with a list: who wrote overnight, what they were sent, who has answered. The reply is yours, written once; the tool fills in the name and the listing.
Why never WhatsApp. A portal email has not opened a WhatsApp window, so the first WhatsApp message to that person is a paid template, approved before the enquiry existed. That build is chapter 8.
Three honest limits, which Claude Code will tell you about. A saved portal login expires and a portal page changes shape, so a run that finds zero enquiries reports zero, never silence. HubSpot blocks notes if the account has sensitive data turned on. And two channels are not read here: a WhatsApp on a personal phone, since the book never reads WhatsApp Web, and a spoken referral.
What it feeds
Qualifying it. The next stage tells a buyer from a browser in three questions. It needs the questions asked, and the answers arriving. The number to read: minutes from enquiry to first reply, with the count of enquiries that got none beside it.
The next chapter reads what the buyer answered and fills the three fields from it, in the buyer’s words, so no field is ever a guess.
The number that proves this stage worked is the median minutes from enquiry to first reply, across every channel, with the count that received none beside it. A median alone hides the half that got nothing.
What stays with a person
Whose hour is this? Whether an enquiry gets your own morning or goes to a colleague is a judgement, made after the reply, never before. A referral arrives inside a relationship. It is answered by a person, from the first line.
The reply at eleven at night is a door held open. Who comes through it is yours to judge; the tool never disqualifies anybody. A blank field means nobody has answered yet, never a browser.
“Would you give up on them after they don’t return your ONE phone call? Or, decide in advance that they’re not a ‘good lead’ because they didn’t leave a phone number?”
Dean Jackson, reposted by Julie Martin, on ActiveRain
And the referral. Someone who trusts you said it aloud. The night reply would spend that, so a person answers it, the same day.
For balance, one agent:
“I always think these threads are interesting because I always get call backs and email backs.”
Russell Brazil, on BiggerPockets
The tools you already pay for
Nothing new to buy.
Mail is the inbox the portal already writes to, read through the night.
Portal is the inbox behind your login, opened by the tool instead of by you.
CRM is HubSpot, or Pipedrive, Zoho or Follow Up Boss through their own servers; it gains the person, the note, and three blank fields.
Every enquiry answered inside the hour, and every one that was not, counted. Then qualifying can begin by morning.
Ask: Of the enquiries that landed last night, how many had a reply before you woke up?
This is stage 9 of twenty, after messaging fifty owners on WhatsApp in a morning and before telling a buyer from a browser in three questions. The whole engine in order is the book, Building a real estate sales engine with Claude Code and Codex, end to end.