Property Enquiry Automation for Estate Agents: Qualifying Buyers and Booking Viewings
A walkthrough of AgentLane's Property Enquiry Qualifier agent — how it grades a buyer or tenant enquiry, when it books a viewing, and what it deliberately leaves to the agent.
By AgentLane Founder · Founder
AgentLane ships a purpose-built agent for this job — the Property Enquiry Qualifier. This post is the walkthrough: what it actually does with an inbound enquiry, when it books a viewing, and what it leaves to the listing agent.
Property enquiries arrive at all hours, and most of them need the same first pass: is this a buyer or a tenant, what's the budget, how soon do they want to move, and do they want to see something now? That first pass is what this agent automates — fast, consistently, and with the listing agent told about every enquiry.
What the agent does, step by step
Webhook (enquiry) ──► Look up client config ──► Qualify enquiry (Gemini)
│
▼
Parse qualification (code)
│
▼
Book the viewing on Cal.com (only when the enquiry names a time, a name and an email)
│
▼
Email the listing agent a summary
That's the real, shipped flow, reproduced from the agent's reference documentation.
Qualify. AgentLane's managed Google Gemini model on Vertex AI reads the enquiry and grades it hot, warm or cold — how ready this person is to view or commit — with a plain-text summary: buyer or tenant, budget, timeline and the recommended next step.
Book, only when it safely can. If the enquiry names a viewing time and includes the person's name and email, and the client has a Cal.com viewing event type configured, the agent books that time. Otherwise no booking is attempted and the listing agent follows up.
Tell the listing agent, every time. Every enquiry ends in an email to the listing agent headed with the grade. There is no listings matching, no three-way switch, no Slack alert and no decline or nurture email to the enquirer — the flow is the same steps every time.
What it requires, and what's honest to say about the industry tag
In practice it needs two credentials: cal_com to book the viewing and resend to email the listing agent. The AI runs on AgentLane's own managed Gemini models, so no AI key of yours is needed; the portal still lists anthropic and postgres as legacy requirements on this agent, and neither is read. It requires AgentLane staff approval before provisioning, the same review dialog as any other non-instant agent:

Worth being precise about the industryFit tag itself: AgentLane's own agent documentation describes Real Estate as a taxonomy-only vertical today — no real-estate client has actually been provisioned on the platform yet, so the tag won't trigger a "Recommended" badge the way an industry with existing client outcomes would. That's a statement about how the catalog's badge logic works, not a hedge about whether the underlying agent functions.
A word on the response-speed statistics you'll find elsewhere in real estate marketing content: several widely circulated claims about "the percentage of buyers who go with whichever agent responds first" don't trace back cleanly to a verifiable primary source when you try to run them down, so this post isn't going to repeat one. What's not in dispute is the basic mechanic: a buyer enquiry that sits unanswered for hours is a buyer who has moved on to the next listing site by the time anyone replies.
How this relates to Lead Qualifier
If your agency already runs the general-purpose Lead Qualifier agent for other clients, the mechanics here are the same — grade, book only a requested time, email a summary. What Property Enquiry Qualifier changes is the grading: it is tuned to buyer-or-tenant, budget and timeline, and it emails the listing agent rather than a business owner.
For an agency weighing whether to offer this under its own brand, the white-label economics are the same as any other catalog agent — a flat fee per client, marked up however the agency prices it, covered in our white-label margin breakdown.
Where to start
If you're an agency with an estate-agent client losing buyer enquiries to slow follow-up, or you run an agency yourself, see how a non-instant agent gets requested and provisioned — the request-dialog steps are the same ones this agent goes through. Or talk to us directly about being the first real deployment of this agent into the vertical it's built for.
The flow diagram above is reproduced from the agent's own reference documentation. Updated 2026-10-18: an earlier version of this post described a retired flow with listings matching, a three-way switch, Slack alerts and a Claude scoring step.
Frequently asked questions
- Is Real Estate a real industryFit tag, or a placeholder?
- It's real in the sense that matters — the agent genuinely does the work described in this post. Where it's honest to be precise: AgentLane's own docs describe Real Estate as a taxonomy-only vertical today, meaning no real-estate client has been provisioned on the platform yet, so it won't show a 'Recommended' badge tied to existing client outcomes. That's a statement about badge logic, not about whether the agent works.
- Does it write listing descriptions or run marketing?
- No. It only handles the inbound side — a buyer or tenant enquiry coming in, graded, booked when the enquiry asks for a specific viewing time, and summarised for the listing agent.
- Does it match a lead to my listings?
- No. There is no listings lookup anywhere in the flow. The agent grades the enquiry and summarises what the person is looking for — buyer or tenant, budget, timeline — so the listing agent can match it against current stock.
- What happens to an enquiry that isn't ready to view?
- The listing agent still gets an emailed summary with the grade and the recommended next step, so every enquiry is seen. The agent does not send the enquirer a decline or a nurture email.
- Does it replace an agent's judgment on a serious buyer?
- No — it handles first-contact qualification and calendar mechanics. Negotiating an offer, assessing a buyer's actual financing position, and closing stay entirely with the agent.