Real estate · Site visits
MixedReal estate developersBooking site visits from property leads before they go cold
A property lead that waits a day for a call has usually spoken to three other projects. These field notes cover a setup that qualifies leads on WhatsApp within minutes, books the site visit and shows which sources turn visits into bookings.
Valnora & Elric team6 min read
A developer selling two projects gets leads from three property portals, Meta and Google lead forms, and walk-ins. The leads land in an inbox and a spreadsheet. A telecaller works through them the next morning, and by then many buyers have already booked a visit somewhere else.
These notes cover a setup in Agent Serve that answers every lead on WhatsApp within minutes, books the site visit straight into the site office calendar, hands some leads to channel-partner brokers and shows which sources actually turn into bookings. Figures in this post are illustrative.
How do the leads get in?
From a portal lead to a site visit and a booking
Workflow · Qualify and book
- 01Portal and ad leadsPortal lead emails via a Gmail trigger, ad form leads via a Google Sheets or Webhook trigger.
- 02WhatsApp qualificationAn approved template, then reply buttons for configuration, budget and timeline.
- 03Leads tableSource, project, answers, score, assigned sales manager or broker, visit status.
- 04Visit bookingOffers open slots from the site calendar and creates the visit event.
Relay · Stalled leads
- 05Lead follow-up RelayWatches the leads table for qualified buyers with no visit after 24 hours.
- 06Sales manager approvesNudges and broker hand-offs run through an allowlisted workflow after approval.
Dashboard · Visit to booking
- 07Funnel dashboardLeads, qualified, visits booked, visits done and bookings by source and project.
- 08No-show monitorAlerts the site head when the weekly no-show rate passes a set level.
There is no built-in portal integration, and you do not need one. Most portals email each lead with a fixed layout, so a workflow with a Gmail trigger reads the email and an Agent block extracts the name, phone, project and any budget the buyer gave. Ad form leads usually already reach a Google Sheet or your CRM; a Google Sheets trigger or the generic Webhook trigger picks them up from there.
Every lead becomes a row in a leads table: source, project, phone and status. If the phone number is already there, the workflow adds the new enquiry to the same row, so one buyer who enquired on two portals is not called twice.
What happens in the first five minutes?
The workflow sends an approved WhatsApp template naming the project, because a first message to a new contact must be a template. When the buyer replies, the WhatsApp webhook trigger starts the qualification workflow, which asks three questions with reply buttons: configuration, purchase timeline and, if the portal did not supply it, budget band.
Buttons matter here. They keep answers clean enough to score without guessing, and they are quicker for the buyer than typing. A free-text reply is read by an Agent block, which maps it to the closest option or passes the conversation to the sales manager.
What the solution produces
WhatsApp qualification and booking (illustrative)
MessageHi Karan, thanks for your interest in Lakeview Phase 2, Whitefield. Can I ask three quick questions to share the right options?
Which home are you looking for? [2 BHK] [3 BHK] [Not sure]
Karan: 3 BHK
When are you planning to buy? [Within 3 months] [3–6 months] [Just exploring]
Karan: Within 3 months
Would you like to see the sample flat? Open slots this weekend: [Sat 11:00] [Sat 16:00] [Sun 11:00]
Karan: Sat 11:00
Booked: Saturday 11:00 at the Lakeview site office. Location pin and parking details below. Reply CHANGE to pick another time.
Broker hand-off brief (illustrative)
Record- Lead
- Anita M. · Housing portal · 2 BHK · ready to move
- Why a broker
- Wants possession within 2 months. Phase 2 hands over next year. Resale fits better.
- Assigned to
- Channel partner for Whitefield, per the broker table
- Consent
- Agreed on WhatsApp to be contacted by a partner broker
How is the visit booked?
Qualified buyers are offered three open slots from the site office's Google Calendar as reply buttons. When they pick one, the workflow creates the visit event with the buyer's answers in the description, sends a confirmation with the location pin and parking notes, and sets the row to "visit booked". A reminder goes the evening before, with a reply option to change the time.
The sales manager on duty sees the visit and a one-paragraph brief on their calendar, so the first conversation on site starts from what the buyer already said.
When does a lead go to a broker?
Some leads are a poor fit for the project but a good fit for someone. A buyer who needs to move in within two months does not want a project that hands over next year. A broker table lists each channel partner with the localities and buyer types they take.
A Relay, an AI coworker with its own instructions and access, watches the leads table. When a qualified buyer has no visit 24 hours after qualifying, or when their answers point at a broker, it drafts either a nudge to the buyer or a hand-off brief for the broker. Both are sent by running an allowlisted workflow. Under Assist autonomy, each one waits for the sales manager's approval, and the approval and the run are recorded.
The Relay reads the table but does not write rows. The workflow it runs updates the status.
What does the dashboard show?
The dashboard reads the leads table and the visits on each site calendar, plus bookings from your CRM or the sheet your sales team keeps. Its panels:
- leads, qualified leads, visits booked, visits done and bookings, by source and project
- visit-to-booking rate by source: the panel that tells you which portal is worth paying for
- median time from lead to first WhatsApp message, and from qualification to visit
- hand-offs by broker and what happened next
Define visit-to-booking rate and no-show rate as named metrics. A monitor on the no-show rate alerts the site head when it passes the level you set for the week, which usually means reminders or slot times need changing.
How to measure it
< 5 min
Lead to first WhatsApp message (illustrative)
The workflow starts as soon as the lead email or sheet row lands.
1 in 4
Qualified leads that book a visit (illustrative)
Measure your own baseline before setting a target.
Illustrative example. Figures show how the workflow is measured; they are not customer results.
What keeps buyers' data and consent in order?
Controls and governance
Approvals before action
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Audit trail
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
Run logs
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
Row-level access
Row-level policies narrow what each person sees in tables, dashboards, exports and scheduled reports.
Roles and permission groups
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
PII detection
A Guardrails block detects personal data and blocks or masks it before text reaches the next step.
More on how Agent Serve handles access, data and audit on the security page.
Message only buyers who gave their number with a request to be contacted, and stop on any opt-out reply. Hand a lead to a broker only after the buyer agrees in the chat; the Relay's draft says what consent it saw, and the sales manager checks it before approving. Row-level access keeps each broker and sales manager to their own leads on the dashboard.
Where should you start?
Start with one project, one portal and one site calendar. Run the qualification questions for a week, read every conversation, and adjust the wording before adding the other sources. For a related pattern on WhatsApp follow-up with consent and STOP handling, see WhatsApp cart and lead follow-up.
Questions teams ask
Do the portals and ad platforms connect directly?
Not through a built-in integration. Most portals email each lead, which a Gmail trigger can read. Ad form leads usually reach a Google Sheet or a CRM already, and a Google Sheets or Webhook trigger picks them up. If a portal offers an API, the API block can call it with the key stored as a workspace secret.
Can an AI voice call the lead instead?
Relays do not place calls. Agent Inbound & Outbound, a separate Valnora & Elric product available by invitation, answers and places calls and can pass warm leads to your team.
What you need
- A WhatsApp Business number connected to Agent Serve, with an approved first-message template per project
- A way for leads to arrive: portal lead emails in Gmail, or ad form leads in a Google Sheet or your CRM
- One Google Calendar per site office, with visit slots and the sales manager on duty
- A broker table: channel partner, localities covered and the kinds of buyer they take
- Where bookings are recorded today, in your CRM or a sheet, so the dashboard can count them
- A named sales manager per project to approve hand-offs and nudges