AI Property-Inquiry-to-Viewing Playbook

When a property changes status before a viewing is booked, a fast automated reply can become a false promise. This playbook moves one inquiry to a verified answer, accepted broker handoff, or confirmed viewing while keeping qualification neutral and legal, financing, valuation, and representation decisions with authorized people.

Copy the pilot card below into a document or spreadsheet and begin with one listing question. If the listing source or the broker who receives an exception is unknown, stop and fix that gap first.

Copy the pilot card and define completion

Inquiry transition	Source to check	Allowed result	Stop or human handoff
When [listing question] occurs, move from [start] to [end]	[listing, assignment, and calendar source]	[verified answer, viewing, or no action]	[conflict/sensitive request and receiver]

• Start: one property-inquiry break has a baseline, owner, approved criteria, and current listing source.
• End: the lead reaches a verified answer, accepted broker handoff, confirmed viewing, explicit nurture state, or documented stop.
• Evidence: listing version, expressed search criteria, permission, routing reason, appointment state, handoff receipt, and outcome.
• Time horizon: one representative listing cycle including unavailable property, changed price, duplicate inquiry, opt-out, and sensitive request.

Roles and prerequisites

Role	Owns	Approves	Receives handoff
Listing operations	Property facts and availability	Listing answer	Data conflict
Broker/team lead	Representation and next step	Viewing and advice	Qualified inquiry
Scheduling owner	Verified calendars and access	Appointment	Access exception
Compliance/legal owner	Advertising and qualification rules	Sensitive exception	Policy risk
Workflow owner	Scope, QA, and expansion	Keep/pause/expand	Cross-team issue

Map listing ID, property facts, status, price/version, showing rules, broker assignment, calendar, consent, communication history, and suppression state. Approve neutral property- and transaction-based questions. Require jurisdiction-specific legal review before launch.

Phase 1: map property and lead state

• Owner: listing operations with broker lead.
• Inputs: listing system, CRM, calendars, routing rules, communication events.
• Actions: trace inquiry through answer, assignment, viewing, follow-up, offer-stage boundary, and stop state.
• Output: source and state map with freshness and precedence.
• Exit gate: each automated fact and next step has one owner and source.
• Escalation/rollback: stop when duplicate records, stale listings, or broker ownership cannot be reconciled.

Phase 2: choose neutral qualification and one transition

• Owner: workflow owner with compliance review.
• Inputs: customer-stated property needs, operational capacity, reversible actions.
• Actions: select one job such as listing answer-to-viewing; remove questions about protected or proxy personal characteristics; define no-action rules.
• Output: approved question set, routing rule, and acceptance criteria.
• Exit gate: criteria describe the property, transaction, timing, or explicitly requested service—not the person's suitability.
• Escalation/rollback: route sensitive or ambiguous requests to the compliance owner without generating neighborhood or demographic judgments.

NAR's fair-housing resource center documents a US professional context for nondiscriminatory housing practice. It is not legal advice for every market; local counsel must approve the deployed workflow. Review the source.

Phase 3: validate listing, assignment, and viewing truth

• Owner: listing operations for facts; scheduling owner for access.
• Inputs: current listing, broker roster, showing restrictions, calendar.
• Actions: recheck status and price before answering; assign by approved operational rule; verify access and calendar before confirmation.
• Output: eligible response/viewing context or named handoff.
• Exit gate: listing and scheduling systems agree and a broker owns the next step.
• Escalation/rollback: withdraw stale information and cancel unconfirmed calendar holds.

Phase 4: execute and nurture from expressed intent

• Owner: broker lead; workflow owner controls automation.
• Inputs: eligible context, approved message, consent and frequency rule.
• Actions: send one idempotent response, record the exact property/search criteria the person supplied, and schedule only permitted follow-up.
• Output: answered, booked, broker-owned, nurtured, or stopped state.
• Exit gate: CRM, calendar, listing, and customer-facing state reconcile.
• Escalation/rollback: suppress nurture after opt-out, property closure, representation conflict, complaint, or unresolved policy risk.

The National Fair Housing Alliance provides responsible-advertising guidance. It supports an advertising review control, not a conclusion about the legality of a specific message. Review the source.

Phase 5: review and expand by market cell

• Owner: workflow owner with compliance owner.
• Inputs: valid answers, viewing reconciliation, handoffs, opt-outs, complaints, policy flags.
• Actions: review by listing type, office, language, source channel, and stage; inspect all sensitive cases.
• Output: signed keep/pause/expand decision.
• Exit gate: quality and compliance thresholds hold across representative cases.
• Escalation/rollback: disable the affected rule/listing/channel cell and preserve unaffected verified cells.

Fictional completed run

A fictional brokerage pilots inquiries for small commercial warehouses in one district. A lead asks whether a listing permits light assembly, requests a weekday viewing, and then asks whether the area is suitable for a particular nationality. The workflow answers only the documented property-use fact, refuses to characterize people or neighborhood demographics, and passes the sensitive question to a broker with the original wording. The listing changes to pending before the viewing is written, so the availability check prevents confirmation. The broker offers a human-reviewed alternative only after the lead repeats its operational criteria. No lead score, housing recommendation, or conversion claim is made.

Inquiry transition	Source to check	Allowed result	Stop or human handoff
Warehouse question to weekday viewing request	Current listing version, broker assignment, and access calendar	Answer documented use; confirm only while listing remains available	Nationality/suitability question goes to compliance and broker; pending status blocks viewing confirmation

Handoff, QA, and measurement

The Trigger column is the join key between the two compact tables.

Trigger	Severity	Owner
Sensitive/proxy criterion	Critical	Compliance/broker
Listing/calendar conflict	High	Listing/scheduling
Advice, finance, valuation, offer	High	Broker/team lead; compliance/legal owner approves policy exceptions

Trigger	Required context	Response target	Fallback
Sensitive/proxy criterion	Exact wording, listing, action withheld	Before response	Neutral refusal and human review
Listing/calendar conflict	Listing ID/version, requested time	Before confirmation	Withdraw or rebook
Advice, finance, valuation, offer	Customer request and verified record	Same service window	Human-only route

QA checks: listing freshness; neutral question set; duplicate identity; broker assignment; calendar/access; consent/frequency; opt-out; sensitive language; accepted handoff; rollback.

The Metric column is the join key between the two compact tables.

Metric	Definition	Baseline
Valid-response rate	Responses supported by current listing, permission, and approved rule / attempted responses	Pre-pilot replay
Viewing reconciliation rate	Due viewing transitions matching listing, calendar, broker, and customer states / due transitions	Pilot
Sensitive-case containment	Flagged cases with no automated suitability judgment and accepted human route / flagged cases	Policy test set

Metric	Decision threshold	Owner	Cadence
Valid-response rate	Set before launch	Listing operations	Weekly
Viewing reconciliation rate	Set before expansion	Scheduling owner	Weekly
Sensitive-case containment	100% required	Compliance owner	Weekly

Failure	Early signal	Corrective action
Stale listing or invalid viewing	Listing version/status changes or access owner does not accept	Withdraw the answer/appointment and let listing operations or scheduling verify it
Steering or proxy-personal qualification	Script or review flags demographic, suitability, or protected/proxy language	Suppress the response and route the exact wording to compliance/legal and the broker/team lead
Unauthorized advice, nurture, or orphaned handoff	Advice/offer request lacks owner, opt-out is present, or assignment times out	Stop automation, preserve the record, and require an accepted authorized human route

Pause the affected rule, listing, or channel cell until the correction passes review.

Frequently asked questions

What may an assistant ask a property lead?

Use approved questions about the property or transaction: property type, location requested by the customer, budget range, timing, use requirements, and viewing preference. Legal review decides the final list.

Can AI recommend a neighborhood?

Do not generate demographic or suitability judgments. Provide verifiable property and amenity facts only within an approved policy, or route to a qualified human.

Can it score leads?

Only with an approved purpose, explainable operational inputs, bias testing, appeal/correction process, and local legal review. This playbook does not supply such a model.

What should a broker receive?

The original request, listing/version, customer-stated criteria, consent state, answers sent, unresolved issue, urgency, and any withheld action.

What to do after completion

Limits. This playbook is not legal, housing, financing, valuation, or brokerage advice. It claims no real estate benchmark, conversion result, integration, or Easy AI capability.

Use the lead qualification playbook to design neutral operational criteria, the lead assignment template for accepted ownership, and the AI-to-human handoff guide for exception context.