What they are looking for
Buy or rent intent (10), target area (15), budget (20), and property type (10).
Case study · Real estate enquiries
Give every property enquiry a clearer next step.
A self-initiated local prototype that checks buyer and renter enquiries, explains which details are present, and gives an agent a synthetic listing match to review.
Useful enquiry details can arrive in different forms.
A buyer or renter may describe a budget, area, property type, timing, or financing in an unstructured message. An agent then has to find the missing details, decide what to clarify, and compare the request with available listings. This prototype brings those steps into a reviewable local workflow.
Example customer journey
From enquiry to an agent-reviewed next step.
The names, enquiries, and property records used in the walkthrough are fictional. The examples below describe tested workflow behavior.
- Submit a buy or rent enquiryA local demo form or POST webhook accepts structured fields or a short free-text request.
- Check the required detailsThe workflow validates contact information and a stable enquiry ID. Invalid contact details stop with HTTP 422 before scoring or storage.
- Extract, score, and explainOptional local Ollama extraction can structure free text. Deterministic rules calculate an explainable readiness score and identify missing information.
- Compare with fictional listingsThe local inventory matcher returns a synthetic listing match when the criteria fit; it does not query a real estate CRM or live market.
- Leave the decision with the agentThe agent reviews the enquiry, verifies listing availability and suitability, and decides what to ask or do next.
Explainable readiness score
A prompt for follow-up, not a verdict.
Points represent whether useful enquiry information was provided. They do not predict conversion or determine access to housing, a viewing, finance, or a property.
When and how they plan
Timeframe contributes 5–20 points; financing information contributes 8–15 points.
How an agent can follow up
A usable contact method and a provided name each contribute 5 points.
Hot, warm, or cold labels
The prototype labels 70+ as hot, 40–69 as warm, and below 40 as cold. These are internal completeness bands for demonstration only.
Verification record · 9 October 2026
What was exercised in the connected local workflow.
The active local n8n workflow was checked with synthetic enquiries. The workflow editor contains 25 nodes; validation checked 23 connections and 27 expressions with zero errors and one expected warning for the disabled Telegram node.
Complete structured enquiry
HTTP 200, readiness score 100 (hot), one fictional match (ROM-S-001), and a simulated notification.
Missing details were surfaced
HTTP 200, readiness score 45 (warm), one fictional match (ROM-R-001), and missing information returned for agent follow-up.
Fields extracted successfully
The local llama3.2:3b model extracted the requested fields; deterministic scoring returned 100 and matched ROM-S-001.
Invalid and repeated requests handled
Missing contact returned HTTP 422. Resubmitting a stable lead ID updated one matching Data Table row instead of creating a duplicate.
Local model failure had a fallback
With an unavailable model tag during setup, the request still returned HTTP 200, used mock_fallback, and included agent-review guidance.
HTML summary rendered in mock mode
Execution 547 succeeded and included lead fields, score reasons, a listing match, and a suggested next action. No email was sent in this preview.
Workflow evidence · captured 9 October 2026
The actual local n8n workflow canvas.
This screenshot shows the connected workflow structure, including local Ollama, mock notification, optional Gmail, and the disabled Telegram node. It is a workflow-editor capture, not an execution result or proof of message delivery.
Workflow map
The same enquiry path, simplified.
This static map is drawn from the verified workflow structure for easier reading. It is not another screenshot or an execution log.
Notification distinctions.
The default demo path returns a mock preview and sends no email. A separate synthetic Gmail send succeeded earlier (execution 546, Gmail SENT label); that proves only the recorded local test delivery to the approved connected inbox. The updated HTML template was previewed in mock mode, and repeat delivery was not tested. Telegram was not run and remains disabled.
The default demo path returns a mock preview and sends no email. A separate synthetic Gmail send succeeded earlier (execution 546, Gmail SENT label); that proves only the recorded local test delivery to the approved connected inbox. The updated HTML template was previewed in mock mode, and repeat delivery was not tested. Telegram was not run and remains disabled.
Disclosure and limits
A local prototype, not a client deployment.
This is self-initiated work with fictional listings and synthetic enquiries—not client work, production software, or evidence of business results.
No live property inventory
Matches come from fictional local records. No client CRM, listing feed, property portal, or live availability system is connected.
An agent reviews every next step
A readiness band is not a measure of a person’s worth or eligibility. An agent must check the request, listing, availability, and appropriate follow-up.
Local tools with bounded evidence
n8n, local Ollama, and local Data Tables were exercised. A synthetic Gmail send was verified; the edited HTML was previewed with mock mode. Telegram was not tested.
Production safeguards and operations
No public deployment, real estate CRM or inventory integration, consent and retention design, access controls, monitoring, repeat Gmail delivery, or production reliability was verified.
Before adapting this for an agency.
Agree on permitted data, consent, retention, access controls, live inventory and CRM connections, duplicate handling, monitoring, delivery rules, operating ownership, and costs. The agency remains responsible for decisions and customer communications.
Agree on permitted data, consent, retention, access controls, live inventory and CRM connections, duplicate handling, monitoring, delivery rules, operating ownership, and costs. The agency remains responsible for decisions and customer communications.
Discuss your process
Message @apps.bymukarram Where do property enquiries need a clearer handoff?
DM “CALLS” on Instagram with your business type and how you currently handle new enquiries.