Your Buyer Said “Maybe a Townhouse.” Don’t Rewrite the Search.
AI-generated editorial illustration. The buyer messages and records below are fictional.
A buyer texts: “Maybe a townhouse would get us more space. Keep the $475,000 cap.”
Their accepted search instructions specify detached homes, at least three bedrooms and a monthly HOA ceiling. A careless AI summary turns the new message into “search townhouses under $475,000.” Three limits disappear. An alternative becomes a replacement.
Maybe is not a database command.
Give an internal oppy a smaller, more useful job: identify the proposed amendment, preserve everything else, and draft the question that resolves the ambiguity.
More inventory, not permission to widen the brief
NAR’s November 12 housing release puts October inventory supply at 5.1 months, up from 4.7 in September. Its separate REALTORS Confidence Index survey reports median time on market of 35 days, versus 33 in September. 1
Those are national measures, not local forecasts or proof that buyers change their minds more often. They are current context for a familiar brokerage task: managing an evolving conversation without losing the instructions already agreed.
The interface is changing, too. Mike DelPrete’s October property-search experiment used real MLS listings through early, non-public connectors to build a customized search experience. He identifies data protection, licensing and governance as unresolved foundations. It was an experiment, not a generally available integration. 2
Conversational search makes one distinction especially important: what the buyer is exploring versus what the buyer has instructed.
Build one Buyer Search Amendment Clerk
This is a proposed configuration, not a released Oppy template or native MLS feature. The clerk reads a supplied packet and drafts a field-level change brief. It does not find listings, assess affordability, send messages or update a saved search.
Oppy’s creation walkthrough documents choosing a role and supplying knowledge such as scripts and product materials. Use those building blocks for this narrowly defined internal role. 4
Before using real buyer material, inspect actual access and function permissions. Keep client-facing sending and external search-writing routes unavailable for this exercise. The Oppy functions guide documents Public/Admin invocation permissions; Admin-only is not synonymous with read-only. Prompt wording is not an access control. 5
Supply the accepted instructions deliberately. Do not ask the oppy to reconstruct them from memory. Anthropic’s agent-memory research warns that saved notes can be wrong initially or drift, then be trusted in a later session. That is an engineering caution, not a finding about Oppy. 3
Start with the evidence, not a summary
Use only authorized, necessary material. This fictional packet includes the original wording and a source locator:
CURRENT_ACCEPTED_CRITERIA: C14
Source: C14-01, accepted buyer instruction message
Exact wording:
“Detached houses only. No more than $475,000.
At least three bedrooms. HOA dues no more than
$250 per month. A garage would be nice, not essential.”
Accepted fields:
Purchase price: at most $475,000, hard limit
Property type: detached only, hard constraint
Bedrooms: at least 3, hard constraint
HOA dues: at most $250/month, hard limit
Garage: preference, not required
NEW_BUYER_MESSAGE: C14-02
“Maybe a townhouse would get us more space.
Keep the $475,000 cap.”
Hard limits and preferences come from the buyer’s wording, not the model’s taste. A price cap is a search instruction, not an affordability assessment. If the baseline or its acceptance evidence is missing, request it. Do not manufacture one.
Copy this amendment prompt
You are an internal Buyer Search Amendment Clerk.
Compare CURRENT_ACCEPTED_CRITERIA with NEW_BUYER_MESSAGE.
Use only the supplied evidence packet.
For every baseline field, return:
- Current value and its source locator.
- Relevant exact buyer wording.
- Proposed value, if any.
- Classification: unchanged, explicit amendment,
exploratory, or unclear.
Silence about a field does not delete it.
“Maybe,” “could,” and “what if” do not establish a
committed change. Preserve numeric limits, AND/OR
relationships and buyer-designated hard constraints.
Do not infer permission to raise the budget, waive
an HOA limit, or reduce bedrooms. An alternative
that conflicts with a hard constraint requires
clarification; it is not an accepted replacement.
Return a field-level brief, unresolved questions,
and one concise clarification draft.
Do not search, send, publish, or update records.
Then ask:
Show every baseline constraint absent from your output. Restore it or identify the exact buyer evidence authorizing its removal.
This second pass checks omissions. It does not certify correctness or enforce tool restrictions.
The useful answer changes nothing yet
For C14-02, the price cap is unchanged and explicitly restated. Property type is exploratory. The bedroom minimum, HOA ceiling and garage preference remain unchanged. “More space” does not authorize dropping bedrooms or raising the budget.
The clerk’s clarification draft:
Would you like townhouses included alongside detached homes, keeping the same price cap, bedroom minimum and HOA limit?
A human reviews and sends that question through an authorized channel. Human approval of an AI brief cannot substitute for clarification from the buyer.
Now add a fictional reply:
C14-03, buyer clarification:
“Yes, include townhouses too. Keep the other limits.”
The candidate amendment is detached OR townhouse, not townhouse only. That small logical operator is the difference between adding an option and quietly removing one.
Accept one change, carry four fields forward
Give the clerk its final drafting instruction:
Using C14-03, prepare candidate record C15.
Change only property type to detached OR townhouse.
Carry every other field forward verbatim.
Attach C14-03 as the amendment source.
Identify the superseded property-type field.
Mark C15 “candidate, not applied.”
A person checks the evidence, accepts the candidate and manually updates the authorized saved search. Keep earlier records for reference, but supply only one clearly labeled accepted record to the next review. C15 is a proposed document label, not a native Oppy versioning feature.
No automatic MLS connection is assumed. No demographic inference or neighborhood steering belongs in the packet. The task is to preserve explicitly supplied property criteria, not invent a buyer profile.
The operating rule is short: when the buyer changes one thing, show the one thing.