Review-first run
Real Estate Agents get a listing descriptions run sheet with real input, source checks, answer repair, and a handoff path for a buyer, seller, lead, or broker reviewer. listing descriptions gives the user a concrete listing copy map with fact-only feature notes to inspect, not just wording to polish.
Turn property facts, features, neighborhood context, photo notes, and compliance limits into a listing description for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need MLS description under 900 characters, feature bullets, no fair housing issues, no exaggeration, mention updates and transit. Phrase shopping in write listing descriptions fails because the note should become listing copy map with fact-only feature notes. The next version should keep that rough note visible. This write listing descriptions run should turn that note into a listing description. For write listing descriptions, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
A copy-ready buyer emails workflow that starts with buyer criteria, listings discussed, timing, next step, and local constraints, produces a ready-to-edit message with subject line, body, tone notes, and review checklist, and flags what humans must verify. buyer emails examples stay close to a client-facing property workflow with compliance and local-fact limits, so the prompt has a real work setting.
Turn buyer criteria, listings discussed, timing, next step, and local constraints into a buyer email for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need short email comparing 3 homes, pros and tradeoffs, showing availability, next step, and no pressure tone. buyer note with criteria and next-tour action would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. Real Estate Agents should use the note as the base for a buyer email. Before real estate agents run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Ready-to-run path
A role-specific page for seller scripts with a recommended prompt, filled scenario, output grader, repair prompt, and related workflows. seller scripts catches the failure point where seller scripts can sound confident while market evidence and legal-sensitive boundaries are thin, because that is where polished answers usually fail.
Turn seller motivation, property context, market data, concerns, and meeting goal into a seller script for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need script for pricing conversation, prep checklist, timeline, objections, and how to explain comps respectfully. Reviewer approval for write seller scripts has to compare the first answer with the supplied note. A practical prompt should keep the missing details visible. Start write seller scripts from the rough request before shaping a seller script. A usable write seller scripts input includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Review-first run
Turn rough follow up after open houses notes into open house follow-up messages; use the prompt, sample input, rejection rules, and review checklist together. follow up after open houses review starts at the moment where visitor follow-up can imply interest, private facts, or next-step readiness that the notes do not prove.
Turn visitor notes, property interest, objections, timing, and next action into open house follow-up messages for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need three follow-up versions: interested buyer, casual visitor, agent with buyer. Mention verified facts only and ask next step. Examples for follow up after open houses help only when they keep the source note visible while shaping visitor follow-up set by interest level. The reusable version should keep this case as evidence. In follow up after open houses, the supplied note becomes the base for open house follow-up messages. A usable follow up after open houses input includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Ready-to-run path
A practical route from rough notes to a neighborhood guide outline, built around amenity categories, commute context, lifestyle fit, and source caveats, neighborhood guide outline quality, amenity categories and commute context, and local-compliance restraint, and reusable prompt fields. neighborhood guides gives the user a concrete guide outline with source-limited local notes to inspect, not just wording to polish.
Turn local amenities, commute notes, housing style, lifestyle fit, and source limits into a neighborhood guide outline for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need guide sections, data to verify, local amenities, commute notes, housing types, and fair housing safe language. Phrase shopping in outline neighborhood guides fails because the note should become guide outline with source-limited local notes. The prompt should turn the note into checkable material. This outline neighborhood guides run should turn that note into a neighborhood guide outline. For outline neighborhood guides, paste the source as bullets, constraints, and audience notes so the model has enough shape for a neighborhood guide outline formatted as clear sections, bullets, and a review checklist.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.
Ready-to-run path
A copy-ready market updates workflow that starts with local data source, timeframe, inventory, price trend, and caveats, produces a market update formatted as clear sections, bullets, and a review checklist, and flags what humans must verify. market updates examples stay close to a client-facing property workflow with compliance and local-fact limits, so the prompt has a real work setting.
Turn local data source, timeframe, inventory, price trend, and caveats into a market update for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need client-friendly update, explain what changed, what it means for buyers and sellers, include caveats, no prediction guarantees. market note with timeframe and caveat row would be weak without the source details, so the evidence has to stay attached. A strong response should keep the practical limits in view. Real Estate Agents should use the note as the base for a market update. Before real estate agents run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
- Reject if
- Do not use the answer if it hides unsupported claims about source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.
Review-first run
Move from a rough social posts request to copy options grouped by angle, audience, proof point, and revision note, using runnable prompts plus reject-if and repair rules. social posts catches the failure point where social posts for real estate agents can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.
Turn listing or service angle, platform, audience, proof, and compliance limits into social posts for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need 5 posts, each under 120 words, no fair housing issues, include CTA, and mark facts I must verify. Reviewer approval for create social posts has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start create social posts from the rough request before shaping social posts. A usable create social posts input includes what is known, what is uncertain, and what the reviewer must verify.
- Reject if
- Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Ready-to-run path
Prepare a review reply with prompts that name the source, protect the risky claims, and leave a checklist for review reply quality, public reputation and property-service context, and recipient-safe next step. reviews gives the user a concrete reply version with escalation and public-tone limits to inspect, not just wording to polish.
Turn review text, customer sentiment, service facts, tone, and escalation boundary into a review reply for a buyer, seller, lead, or broker reviewer.
- Bring first
- Need public reply under 80 words, thank client, no private transaction details, mention trust and next-step referrals lightly. Phrase shopping in reply to reviews fails because the note should become reply version with escalation and public-tone limits. A stronger run should protect the user's real limits. This reply to reviews run should turn that note into a review reply. For reply to reviews, paste the source as bullets, constraints, and audience notes so the model has enough shape for a ready-to-edit message with subject line, body, tone notes, and review checklist.
- Reject if
- Reject the answer if it invents facts, numbers, policy claims, citations, credentials, or examples that were not in the notes.