LLM-Powered Real Estate Search and Agent Matching

zillow · Tech · 2024 · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.6 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: Real estate search support and agent matching

StreetEasy needed to answer common listing questions quickly and create more trustworthy agent introductions while controlling LLM cost, latency, hallucination risk, fair-housing compliance risk, and subjective quality in personalized communications.

Constraints:

Architecture

StreetEasy built two LLM-based features. Instant Answers uses BERTopic and BERT embeddings to discover frequent buyer questions, prepares context from listing and building data, and pre-generates answers with chain-of-thought validation against context to minimize cost and latency. Easy as PIE computes structured agent-fit attributes from deal history, user preferences, and property data, then uses a chain of prompts plus LLM and human evaluation to generate concise agent bio summaries.

Diagram confidence: reconstructed (reconstructed from prose).

flowchart LR
  Topics["Historical inquiry topic model"] --> Context["Property context dataset"]
  Context --> Answers["Instant Answers generator"]
  Answers --> Cache["FAQ cache"]
  AgentAttrs["Agent-fit attribute computation"] --> BioChain["Bio summarization chain"]
  BioChain --> Evaluation["Human and automated evaluation"]
  Answers --> Evaluation
  Guardrails["Fair Housing guardrails"] --> Answers
  Guardrails --> BioChain
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
Historical inquiry topic model Uses BERTopic and BERT embeddings to identify common buyer FAQ themes from anonymized inquiries. Property context dataset
Property context dataset Aggregates active listings, past listings, and building pages for grounded FAQ answer generation. Historical inquiry topic model, Instant Answers generator
Instant Answers generator Pre-generates answerable property FAQ responses and validates drafts against context data. Property context dataset, FAQ cache
FAQ cache Serves pre-generated answers without per-query LLM generation cost or latency. Instant Answers generator
Agent-fit attribute computation Computes price-range, neighborhood, listing, building, property-type, and experience attributes from agent and user data. Bio summarization chain
Bio summarization chain Uses drafting and revision prompts to create concise, card-friendly agent summaries. Agent-fit attribute computation, Human and automated evaluation
Human and automated evaluation Combines LLM-based scoring, human review, A/B tests, metric monitoring, and response monitoring. Instant Answers generator, Bio summarization chain
Fair Housing guardrails Sets compliant response boundaries with review by ethical AI, legal, and broader AI teams. Instant Answers generator, Bio summarization chain

Data flow

For Instant Answers, historical buyer questions are topic-modeled, property context is aggregated from active listings, past listings, and building pages, answerable FAQs are selected, and answers are pre-generated and validated against context. For Easy as PIE, agent deal history, inferred user preferences, and property data create suitability attributes, while LLM summarization condenses agent bios through drafting and revision prompts.

4 supporting quotes
“We decided to pre-generate answers to the most frequently asked questions using available data instead of responding to inquiries in real-time.”article, stated
“Context Data Preparation: We aggregated and pre-processed property data from active listings, past listings and building pages to create a comprehensive dataset.”article, stated
“We computed these attributes based on the agent’s deal history (based on their StreetEasy profile), the user’s home preferences (inferred from their search activity), and data about the specific property they are browsing.”article, stated
“Based on the evaluation, we adopted a chain of prompts, iterating through drafting and revision tasks before returning the finalized summary.”article, stated

Why this architecture

StreetEasy pre-generated FAQ answers because real-time generation would be more expensive and less predictable for high-traffic listing pages. It used context validation to reduce hallucinations and used a separate summarization chain for agent bios because that task needed concise, UI-fit language judged for informativeness and creativity.

3 supporting quotes
“Specifically, we wanted to build an AI system that would cost less than a few hundred dollars, while scaling to support StreetEasy/Zillow traffic.”article, stated
“This approach not only minimized computation cost and latency, but also ensured the reliability of the answers.”article, stated
“the main goal of the summarization task was to create short and concise bio summaries—easily fitting into the carousel card shown in the design,while remaining informative and unique to each agent”article, stated

Models used: LLMs · BERTopic · BERT

Scale

Alternatives considered (roads not taken)

Traditional web FAQ search

Rejected because: It can be slow and inefficient, requiring users to navigate complex search and irrelevant results.

“The traditional, web-based knowledge base/FAQ depends on search mechanisms that are sometimes slow and inefficient.”article, stated

Real-time LLM answers to shopper inquiries

Rejected because: Pre-generation reduced computation cost and latency and made reliability easier to control.

“We decided to pre-generate answers to the most frequently asked questions using available data instead of responding to inquiries in real-time.”article, stated

Single-step answer generation

Rejected because: The team needed to prevent hallucinations and avoid answering unanswerable questions.

“One of the main challenges we faced was preventing LLM from hallucinating and returning answers to unanswerable questions.”article, stated

Automated summarization metrics alone for agent bios

Rejected because: Human review was needed to judge informativeness and creativity.

“we used LLM-based evaluation to score how well the summaries comply with the requirement, and human-in-the-loop review to rate the level of informativeness and creativity.”article, stated

Patterns

latency-optimization (serving)

Instant Answers pre-generates FAQ responses from available property data to avoid real-time LLM cost and latency at serving time.

“This approach not only minimized computation cost and latency, but also ensured the reliability of the answers.”article, stated

prompt-chaining (prompting)

StreetEasy uses step-by-step answer validation for Instant Answers and a chain of drafting/revision prompts for agent bios.

“We instructed the LLM to first draft answers to all questions, and then validate these answers against the context data before returning the final response.”article, stated
“we adopted a chain of prompts, iterating through drafting and revision tasks before returning the finalized summary.”article, stated

eval-driven-development (evaluation)

The team used faithfulness, response relevancy, design compliance metrics, LLM-based summary scoring, human review, A/B tests, and post-deployment monitoring.

“We then evaluated these answers using LLM-based metrics such as: Faithfulness, which measures the factual consistency of answers, given the provided information; and Response Relevancy”article, stated
“After deployment we conduct A/B tests and monitor key metrics and LLM responses, in order to ensure continuous improvement of the application.”article, stated

human-in-the-loop-gate (quality)

Human review complements LLM evaluation for subjective agent-bio quality and sensitive personalized communications.

“Automated evaluation and human feedback are both necessary to maintain quality and prevent errors.”article, stated

safety-policy-enforcement (safety)

StreetEasy uses Fair Housing guardrails, legal review, ethical AI review, and prompt boundaries to reduce discriminatory output risk.

“We also leverage the Fair Housing guardrails and create clear instructions and examples in our prompts”article, stated

Tradeoffs

Pre-generate property FAQs

Chose cached answers to common questions over real-time LLM answers to every inquiry.

Rationale: Pre-generation lowered computation cost and latency and improved answer reliability.

“We decided to pre-generate answers to the most frequently asked questions using available data instead of responding to inquiries in real-time.”article, stated

Validate generated answers against context

Chose draft-then-validate prompting over direct final-answer generation.

Rationale: The extra validation step reduced hallucination risk and prevented responses to unanswerable questions.

“This step-by-step approach helped us generate more accurate and reliable answers.”article, stated

Use generated bio summaries in a constrained UI

Chose short LLM-generated agent summaries over long self-written agent biographies in carousel cards.

Rationale: The card format required concise but unique messages that highlighted relevant professional qualifications.

“the main goal of the summarization task was to create short and concise bio summaries—easily fitting into the carousel card shown in the design,while remaining informative and unique to each agent”article, stated

Gotchas (what bit them)

LLMs can answer when they should abstain.

Root cause: Property questions may be unanswerable from available data, and unconstrained generation can hallucinate.

Resolution: Use chain-of-thought prompting to draft, validate against context, and only return final responses after validation.

“Our primary goals were to identify which FAQs can be answered using available data, and to ensure that we only respond to answerable questions.”article, stated

Real estate LLM features can amplify unfair or discriminatory outcomes.

Root cause: LLMs trained on broad data can perpetuate and amplify existing societal biases.

Resolution: Coordinate with ethical AI, legal, and broader AI teams and use Fair Housing guardrails in prompts.

“LLMs that are trained on vast datasets can inadvertently perpetuate and amplify existing societal biases, leading to unfair or discriminatory outcomes.”article, stated

Automated metrics do not fully capture subjective communication quality.

Root cause: Agent-introduction copy must be informative, creative, and relationship-building, not merely compliant with requirements.

Resolution: Use human-in-the-loop review alongside LLM-based evaluation.

“human-in-the-loop review to rate the level of informativeness and creativity.”article, stated

Cross-functional alignment is a production requirement, not a nicety.

Root cause: LLM-powered user journeys must align technical feasibility, design, marketing, user needs, and business goals.

Resolution: Use iterative PEMD collaboration and continuous monitoring/evaluation/refinement.

“Building a successful AI application is an iterative, cross-functional process.”article, stated

Evaluation

StreetEasy evaluated Instant Answers with faithfulness, response relevancy, non-LLM design metrics, and answerability checks, while Easy as PIE used LLM-based requirement-compliance scoring, human review for informativeness and creativity, post-deployment A/B tests, key metric monitoring, and response monitoring.

Metrics: Faithfulness · Response Relevancy · non-LLM design compliance metrics · human informativeness and creativity ratings · A/B test metrics · LLM response monitoring

3 supporting quotes
“We then evaluated these answers using LLM-based metrics such as: Faithfulness, which measures the factual consistency of answers, given the provided information; and Response Relevancy”article, stated
“we used LLM-based evaluation to score how well the summaries comply with the requirement, and human-in-the-loop review to rate the level of informativeness and creativity.”article, stated
“After deployment we conduct A/B tests and monitor key metrics and LLM responses, in order to ensure continuous improvement of the application.”article, stated

Outcomes

The article reports the cost target, user-page dwell-time context, historical-question window, buyer-survey percentages, and traffic-scale requirement, but not adoption or conversion results.

3 supporting quotes
“showcases our recent deployment of two LLM-based features.”article, stated
“By following these steps, we confidently provided pre-generated answers to common questions, enhancing the user experience for home shoppers while maintaining efficiency and accuracy.”article, stated
“The development and deployment of these two LLM-powered features provided invaluable learnings and insights into the challenges and exciting opportunities”article, stated