An enquiry about a sold property can arrive weeks after an advertisement changes. A saved link, a forwarded screenshot and a reused street address all keep old information alive. Automation can check the current listing record and prepare a more useful response, provided it first establishes which listing the customer means. The difficult part is usually identity and status authority, rather than composing a polite reply.
The proposed process below produces a status-check record and an alternative-search handover. It does not make a portal authoritative, establish a sale's legal completion, or promise that another property is suitable. The agent still resolves identity conflicts and decides what information can be shared with the customer.
Use a stable listing identity before relying on an address
Capture the original link, listing reference, screenshot or quoted description. Preserve it with the enquiry identifier. If a link contains an agency listing ID, map that ID to the current internal record rather than searching only by the address text. Several units can share a building address, and the same property can have successive listing campaigns.
Maintain an explicit map between external portal references and agency records. Record where the mapping came from and which version is accepted. A model can suggest candidate matches from text, but it should not create a definitive relationship from a similar description or photograph. Missing unit numbers and reused photographs are reasons to ask for clarification.
Source: HubSpot record deduplication documents matching through record IDs and unique-value properties in relevant operations. It also distinguishes automatic contact/company deduplication and notes a company-domain exception for API-created companies. Those mechanisms do not establish a property's identity or deduplicate arbitrary listings automatically. Property matching remains an agency-specific mapping control.
Decide which status record answers the question
Write down the statuses the agency uses and who can change them. Active, under offer, withdrawn and sold can have different customer-facing meanings. Do not assume that under offer means unavailable for every enquiry, or that withdrawn means permanently off the market. The responsible agent should approve the response rule for each status.
Use the agency's authoritative record with a retrieval time and version. A portal can lag behind it; an exported spreadsheet can be stale. If the agency has not established a status authority, stop at a request for agent confirmation. Picking the latest timestamp from unrelated systems is not a substitute for deciding which record controls availability.
Source: OpenAI function calling explains that application code executes requested functions. A bounded lookup tool can retrieve the listing status and evidence reference. The application should restrict that lookup to the relevant record and return an explicit failure when it cannot complete. A tool request or an old cached response is not a successful current check.
Reusable old-listing status and response table
Use this proposed table in the enquiry workflow. The agency must approve the exact status meanings and wording before external messages are enabled.
| Check or result | Evidence required | Proposed action |
|---|---|---|
| Exact listing mapped | External reference, internal ID and accepted mapping | Retrieve status for that internal ID |
| Address-only match | Unit, street and candidate records | Ask for the original link or agent clarification |
| Active status | Authoritative record version and check time | Send to normal enquiry handling; do not yet confirm a viewing |
| Under-offer status | Current record plus agent's approved response rule | Prepare that response or route to the agent |
| Sold or withdrawn | Current authoritative status and permitted customer wording | Explain availability limit and ask about alternatives |
| Conflicting status | Each source, value, version and retrieval time | Hold automated availability wording for agent resolution |
| Lookup failure | Failed step and named owner | Say the team is checking, without inventing availability |
| Repeat enquiry | Stable enquiry/event ID and earlier case | Link the new message to history; avoid a second independent viewing request |
The handover record should contain the original enquiry, mapped listing ID, status evidence, proposed reply, agent decision and any alternative preferences volunteered by the customer. Keep a status check separate from a booking state. A property being active does not mean access or a viewing appointment has been confirmed.
A reusable unavailable-listing reply is:
“Thank you for asking about [listing reference]. Our current record, checked at [time], shows [agent-approved status wording]. Would you like the agent to help identify alternatives? If so, please tell us your preferred area, property type and any requirements you want us to consider. We have not arranged a viewing for this listing.”
Use the check time internally if displaying it would confuse the customer; retain it in the evidence record. Do not disclose transaction details beyond the agency's approved status wording. The completion check is that the reply can be traced to the correct listing and current accepted status, with the customer's response determining the alternative-search step.
Examine exact, ambiguous and repeated enquiries
Imagine a hypothetical enquiry carrying portal reference L-741. The accepted mapping points to agency listing A-88, whose current record is withdrawn. The agent's rule allows the team to say the listing is no longer available through that campaign. Automation prepares the reply and asks whether the buyer wants alternatives. It does not make up a reason for withdrawal or arrange access.
A second hypothetical enquiry says the two-bedroom flat in Green Court, accompanied by a cropped screenshot. The agency has three units in that building and one previous campaign using the same photograph. The system presents candidates for staff review and asks for the original link or unit reference. It does not choose the cheapest unit or the only one currently active merely to keep the conversation moving.
A duplicate notification with the same stable event identifier should find the existing case. A genuine second message from the customer may add preferences and should remain in the history. Distinguish repeat processing from new customer intent: identical text sent later can be a follow-up rather than a duplicate to discard.
If the status changes while an agent reviews the reply, refresh it before sending according to the agency's chosen freshness rule. Preserve both snapshots. A previously approved unavailable response should not go out after a record has been reactivated without someone confirming the appropriate wording.
Ask about alternatives without assuming a qualification outcome
Collect only the preferences relevant to an alternative search: area, property type, stated budget range, timing and essential features. Label these as customer statements. A budget figure is not evidence of affordability or financing approval. A preference for an area is not permission to send unrelated marketing indefinitely.
The agent can then prepare a shortlist using approved available records. Keep each candidate's identity and status separate from the old listing. If the customer declines alternatives, close the alternative-search task while retaining the enquiry history according to the agency's approved process. Repeatedly promoting substitutes would defeat the purpose of a useful status answer.
Give conflicts a human owner and test the map
Source: n8n human review describes pausing selected agent actions for approval or denial. It can be used around an external reply when a case needs review. It does not decide which listing is correct or implement an agency's status rules automatically.
Test the proposed workflow against staff-labelled examples of exact IDs, address-only enquiries, reused photos, changed portal references and unavailable lookups. Count incorrect property matches, unsupported availability statements, missed status conflicts and unnecessary clarification requests. Do not count every message prepared as a resolved enquiry. The desired outcome is a correct, understandable status answer or an assigned unresolved case.
Questions about stale listings
Should we trust the portal if it still says available?
Only according to the agency's documented authority rule. If the portal conflicts with the current accepted agency record, show the conflict to the agent and correct the relevant public information through the normal process. The workflow should not silently prefer whichever source would make a viewing easier to arrange.
Can the model infer sold status from an old conversation?
An old message can provide a lead for verification, but it should not replace the current status check. A transaction may have fallen through, a campaign may have changed, or the message may concern another unit. Return the referenced record and evidence time to the agent before using it in customer-facing availability language.
Does a successful status check authorise booking a viewing?
No. It answers the listing availability question under the accepted record. Viewing coordination still needs participant availability, access requirements and an approved booking step. Keep those state changes separate so the customer never receives a confirmed appointment based only on an active listing field.
If your business needs help defining this process, explore AI agents for estate agencies, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.