AI Prompts for Real Estate Agents: 12 Copyable Workflows

Prompt 1

Build a verified listing fact sheet before writing copy

Use when: you have a seller intake, tax record, prior listing, measurements, disclosures, or notes and need one reviewable source before marketing begins.

Paste: only approved property source material. Remove unnecessary personal or financial information.

You are preparing a listing fact sheet for a licensed real estate agent.

Use only the source material pasted below. Do not use outside knowledge. Do not invent, infer, average, or “improve” any property fact.

Create five sections:
1. Confirmed facts, with the source name and exact source location for each fact.
2. Conflicts, showing every value that disagrees and where each value came from.
3. Missing facts needed before MLS input or public marketing.
4. Claims that require human verification, including condition, materials, age, measurements, views, updates, school, neighborhood, zoning, utilities, and included items.
5. Questions for the listing agent or seller.

If a fact appears in only a prior listing or marketing document, label it “prior marketing claim, not independently verified.” Do not write public copy yet.

SOURCE MATERIAL:
[paste approved sources]

Human approval: the agent resolves every conflict and marks the approved fact sheet before any description or MLS draft begins.

Prompt 2

Draft a listing description from approved facts

Use when: the property facts have already been checked and you need a first draft, not a fictional version of the home.

Draft a real estate listing description using only the APPROVED FACTS below.

Audience: [likely buyer need, not a protected class]
Channel and limit: [MLS/public remarks/website] [character or word limit]
Voice: plain, specific, warm, and factual. Avoid generic luxury language.

Rules:
- Do not invent a feature, measurement, material, condition, update, view, benefit, school claim, commute time, neighborhood description, or lifestyle claim.
- Do not describe who should live there or use language that could express a protected-class preference.
- Do not turn “near” into a travel time unless a verified source supplies it.
- Do not call anything new, renovated, private, safe, quiet, best, perfect, or maintenance-free unless that exact claim is approved.
- If the facts are too thin, ask up to five questions instead of filling the gap.

Output:
1. Draft description.
2. Fact-check table mapping every concrete claim to an approved fact.
3. Fair housing and advertising review flags.
4. Final items the licensed agent must approve.

APPROVED FACTS:
[paste the approved fact sheet]

Human approval: check the facts, MLS rules, brokerage policy, fair housing language, character count, and final public copy.

Prompt 3

Turn showing notes into a buyer recap and CRM note

Use when: you have your own notes or a consented transcript after showings and need the details preserved before the next property blurs them together.

Turn the showing notes below into a source-faithful buyer recap.

Do not add property facts, buyer preferences, urgency, motivation, financing details, or next steps that are not in the notes. Separate what the buyer said from what the agent observed. Mark uncertain statements as uncertain.

Output:
1. One CRM note with date, properties seen, buyer reactions, preferences learned, objections, questions, and promised follow-up.
2. A property-by-property table: liked, disliked, unknown, follow-up needed.
3. Action list with owner and due date only when the notes provide one. Otherwise write “date not set.”
4. A short text draft in my natural voice that confirms the buyer's stated next step. Do not send it.
5. Missing questions I should ask before changing the search.

NOTES OR TRANSCRIPT:
[paste the minimum necessary notes]

Human approval: verify addresses, prices, client statements, and promises before saving the CRM note or sending the text.

Prompt 4

Turn a seller call into decisions, promises, and a draft update

Use when: a listing call covers showings, feedback, pricing, repairs, marketing, and several promises at once.

Read the seller-call notes below and create an action ledger.

Use only what was said. Do not invent agreement, consent, a price change, repair authorization, marketing claim, deadline, or legal conclusion.

For each item show:
- observed fact or direct statement;
- source location or quote fragment;
- decision made, or “no decision recorded”;
- action;
- owner;
- due date, or “not stated”;
- whether client approval is still required.

Then draft a concise seller recap email that restates confirmed decisions and asks for confirmation on anything ambiguous. Do not present a suggestion as an agreement. Do not send it.

End with “Agent review required” and list every number, date, promise, property claim, and decision I must verify.

CALL NOTES:
[paste notes or consented transcript]

Human approval: the agent confirms every commitment and sends the final message.

Prompt 5

Prepare a lead follow-up draft from CRM context

Use when: the CRM contains a real trigger and you want a relevant draft, not an empty “just checking in.”

Prepare one follow-up message from the CRM context below.

First identify the real reason to contact this person now. If there is no specific trigger, say “No useful follow-up trigger found” and stop.

Rules:
- Use only the provided conversation, activity, property interest, task, and approved facts.
- Do not invent familiarity, a prior promise, market urgency, competition, scarcity, savings, property availability, or client motivation.
- Do not mention protected-class information or infer personal circumstances.
- Do not give legal, lending, tax, inspection, or valuation advice.
- Keep it under [length] and sound like a quick note from a real person.

Output:
1. Trigger found and source.
2. Draft text or email.
3. Facts or links that need verification.
4. Best human next step if they reply.

Do not send or update the CRM.

CRM CONTEXT:
[paste only the needed timeline entries]

Human approval: confirm consent, channel, identity, timing, opt-out requirements, facts, and tone before sending.

Prompt 6

Create a ranked daily brief instead of a notification dump

Use when: your calendar, inbox, CRM, listings, and transactions all compete for attention.

Create today's real estate daily brief from the supplied sources.

Rank by consequence and time sensitivity, not by which system produced the most notifications.

For each item include:
- observed fact;
- source and source timestamp;
- conflict or missing information;
- why it matters today;
- decision or action needed;
- owner;
- prepared draft or checklist, if safe;
- authority: inform, prepare, recommend, or wait for approval.

Priority order:
1. closing, contract, contingency, money, access, or client risk;
2. promises due today;
3. appointments and preparation;
4. revenue follow-up with a real trigger;
5. routine administration.

Do not assume a task is complete because an email was sent. Do not invent a deadline. If sources conflict, show the conflict. End with the three decisions that most need my attention.

SOURCES:
[paste approved calendar, CRM, inbox, listing, and transaction extracts]

Human approval: the brief may organize and prepare. The agent still decides, contacts people, moves money, and changes records unless a separate tested permission exists.

Prompt 7

Review transaction deadlines with source and calculation visible

Use when: you need a second set of eyes on a contract packet. This is preparation, not legal advice or a replacement for licensed review.

Prepare a transaction deadline review from the documents below.

For every possible deadline show:
1. deadline name;
2. controlling document and exact clause or page;
3. trigger date;
4. calculation rule exactly as written;
5. calculated date;
6. amendment or conflict that may change it;
7. confidence: confirmed, ambiguous, or missing;
8. person responsible for human verification.

Rules:
- Do not invent a deadline, default rule, business-day rule, holiday treatment, jurisdiction rule, or legal interpretation.
- Do not silently choose between conflicting documents.
- If the calculation depends on a legal interpretation or missing fact, stop and state the question.
- Preserve amendments and superseded dates in the history.

Output a draft deadline ledger and a separate “licensed review required” list. Do not calendar, notify, waive, remove, or change anything.

DOCUMENTS:
[paste or attach the approved transaction documents]

Human approval: the agent or authorized transaction professional verifies the controlling documents and dates before any calendar or client communication changes.

Prompt 8

Prepare a listing launch checklist from the signed file and SOP

Use when: a listing has been signed and work must move through photography, MLS preparation, marketing, signs, access, and seller updates.

Prepare a listing launch checklist using the signed listing documents, approved fact sheet, and team SOP below.

Create a table with task, required source, current fact, missing input, owner, target date, dependency, approval gate, and status.

Rules:
- Signed documents control client instructions. The team SOP controls process. Do not let a prior listing or marketing draft override either.
- Do not invent photography time, go-live date, price, showing instruction, lockbox permission, occupancy, seller approval, or MLS field.
- Mark any conflict between the signed file, seller message, calendar, and SOP.
- Keep publishing, ordering, spending, account changes, and client-facing messages behind human approval.

Finish with:
1. the five items that block launch;
2. drafts that can be prepared now;
3. questions for the seller or listing agent;
4. a short status update draft. Do not send it.

SOURCES:
[attach or paste approved documents and SOP]

Human approval: the listing agent confirms price, dates, seller instructions, public copy, MLS entry, spending, and launch.

Prompt 9

Explain a market report without turning movement into a prediction

Use when: you have a current MLS, association, or RPR report and want a client-ready explanation grounded in the actual data.

Turn the approved market report below into a plain-language update for [audience] in [market and property type].

Use only the supplied data. For every number, preserve the geography, property type, date range, metric definition, comparison period, and source.

Separate:
- what the data directly shows;
- reasonable questions the data raises;
- local context I should add from my own experience;
- what the data cannot prove.

Do not claim a cause, forecast, best time to buy or sell, guaranteed outcome, price direction, or individual property value unless the supplied source supports that exact statement. Do not turn a one-month change into a trend without enough periods.

Output:
1. 90-second spoken script;
2. number-to-source verification table;
3. three client questions;
4. claims the agent must review.

REPORT:
[paste or attach approved report]

Human approval: verify every statistic and add the local explanation. A market report is not an appraisal or promise.

Prompt 10

Repurpose your own video without replacing your point of view

Use when: you recorded a useful market, buyer, seller, or business explanation and want several drafts from the same original source.

Repurpose my transcript below. My spoken ideas are the source. Preserve my point of view, examples, uncertainty, and plain language.

Do not add a statistic, property fact, client story, testimonial, result, legal claim, market claim, or personal experience that I did not say. Do not turn a cautious statement into a promise. Flag any sentence that needs a source before publication.

Create:
1. three short-video hooks that honestly match the transcript;
2. one 45-to-75-second script using my original wording where practical;
3. one LinkedIn post;
4. one email paragraph;
5. five FAQ questions and source-faithful answers;
6. a list of factual claims and publication checks.

Use short sentences. Remove filler, not personality. Do not make me sound like an AI account. Ask me for the audience and CTA if they are missing.

TRANSCRIPT:
[paste your transcript]

Human approval: Adam or the agent approves the hook, claims, tone, platform fit, disclosures, and final publication.

Prompt 11

Build a one-page meeting prep brief

Use when: you have an upcoming client, prospect, vendor, team, or recruiting meeting and the context is scattered across several approved systems.

Create a one-page meeting prep brief from the supplied calendar, email, CRM, notes, and documents.

Include only information that helps me walk into this meeting prepared:
1. meeting purpose and desired outcome;
2. who is attending and their confirmed role;
3. last meaningful interaction, with source and date;
4. open promises, decisions, objections, and unanswered questions;
5. relevant property, transaction, or business facts, each with source;
6. likely agenda in priority order;
7. five questions I should ask;
8. documents or facts I should have open;
9. what must not be assumed.

Do not merge people with similar names. Do not infer motivation, relationship, budget, authority, or agreement. If sources conflict or identity is uncertain, show it at the top. Keep private information to the minimum needed for this meeting.

SOURCES:
[paste approved context]

Human approval: review identities, relationship history, promises, confidential details, and meeting goal before relying on the brief.

Prompt 12

Turn a walkthrough into an SOP and AI employee job map

Use when: a person knows how the work happens but the process is not written, which is usually where automation breaks.

Interview me to document one repeated real estate job. Ask one question at a time. Do not design a tool until the current work is clear.

You must learn:
- trigger and finish condition;
- person accountable;
- source of truth for every input;
- exact steps and decision points;
- exceptions and stop conditions;
- private or regulated data involved;
- messages, records, money, publishing, deletion, and account actions;
- current frequency, time, misses, and review burden;
- definition of a correct result.

Then produce:
1. current SOP;
2. gaps, conflicts, and missing ownership;
3. proposed AI role using Context, Connections, Capabilities, and Cadence;
4. authority ladder: read, organize, draft, recommend, update, send, publish;
5. past-work test set including normal, missing, conflicting, sensitive, and adversarial cases;
6. failure and recovery plan;
7. first narrow version worth testing.

Do not recommend automation where the source, rule, owner, or approval is unclear.

Human approval: the business owner approves the SOP, access, authority, tests, owner, and kill rule before any build starts.