Workflow card WC-12.5: Starter automation 5: weekly seller update draft
From AI for Real Estate Agents (2026 Edition). Facts in, draft out, licensee signs.

Time: estimate: about 60 minutes to build, 5 minutes per listing to approve

Trigger. A schedule: every Monday at a set hour, for every listing marked active in your CRM or listing sheet.

Inputs.

- A listing sheet or CRM view with one row per active listing: seller first name(s), property city, list date, current price, days on market, this week's showing count, showing feedback (copied from your showing service), online views if you track them, open house dates
- The columns must be filled by Sunday night; the automation reads what is there and nothing else
- Your voice file and license disclosure line
- An approval place: one draft email per listing in your drafts folder, flagged "seller update"
- Steps once wired: (1) schedule fires; (2) platform reads each active row; (3) AI drafts one update per listing; (4) drafts saved to your drafts folder; (5) you add the judgment (what the numbers mean, what you recommend), then send

Brief. (paste everything between the lines)

------------------------------------------------------------
Role: You are drafting a weekly status update from a licensed residential agent to a seller client. You only use facts I give you. If a fact is missing, write [MISSING: what you need] and do not guess. Ask instead of guessing.
Facts: Seller first name(s): [name field]. City: [city field]. List date: [date]. Current price: [price field]. Days on market: [days field]. Showings this week: [count field]. Feedback received: [feedback field]. Online views: [views field, or "not tracked"]. Upcoming open house: [date or "none"].
Audience: A seller who checks the listing every day and wants to know what is happening and what it means.
Voice: [paste voice file, or: "Calm, factual, direct. Numbers first, then what they mean. No cheerleading."]
Rules: Use only facts I give you; ask instead of guessing. Report the facts in the order given. Do not interpret the numbers, do not recommend a price change, and do not predict when the house will sell; leave a line that says [AGENT: your read on the week and your recommendation] for me to fill. Quote feedback neutrally; do not soften or sharpen it. Nothing about who should live here or who the neighbors are. No schools, churches, safety, or demographics. Include this line exactly at the end: "[license disclosure line]".
Format: One email, under 150 words, subject line "Weekly update, [city], week of [date]". Facts as a short list, then the [AGENT] line, then a one-line close. After the output, list every fact you used and which input it came from.
------------------------------------------------------------

Check.

- Compare every number in the draft to the row. Showings and days on market are the two sellers remember.
- Fill the [AGENT] line yourself, every time. An update with no judgment in it tells the seller you are not paying attention.
- Read the feedback quotes against the source. The AI must not have improved them.
- Failure signals: a draft for a listing that went pending last week (update the status column); a Monday with no drafts; identical numbers two weeks running when you know showings happened.

Ship. Send from your own email on Monday, after the judgment line is filled. Save the brief as "Automation 5, weekly seller update, v1."

Compliance check. Ch. 4.4 (pricing opinions and recommendations are yours, never the automation's), 4.5 (seller's bottom line and offer details never go in the sheet the automation reads), 4.3 (license disclosure). The draft is a fact sheet. You add the advice.
