Workflow card WC-09.2: Build a 12-touch nurture sequence in your voice
From AI for Real Estate Agents (2026 Edition). Facts in, draft out, licensee signs.

Time: estimate: about 60 minutes, once

Trigger. You want a year-long follow-up sequence for new leads, written once, where every touch has a stated reason to exist and the facts that change per lead are left as fill-in fields.

Inputs.

- The 12-touch schedule from T-09.1 (day numbers and channels)
- Your voice file and standing instructions (Chapter 3)
- Your license disclosure line
- Three to five resources you actually have and can send (for example, your one-page guide to how offers work in your county)
- The market facts you can supply per lead from your MLS, listed as field names, not numbers
- Your consent and opt-out wording from T-09.2

Brief. (paste everything between the lines)

------------------------------------------------------------
Role: You are helping a licensed residential agent write a 12-touch follow-up sequence for new buyer and seller leads. You only use facts I give you. If you need a fact I have not given, ask instead of guessing. You never invent a market number, a statistic, or a resource.
Facts: Schedule: [paste T-09.1 day and channel list]. Resources I can send: [list]. Market facts I will supply per lead, as field names: [for example: [recent sale near their property], [days on market in their range]]. My name and brokerage: [name, brokerage]. Disclosure line: "[license disclosure line]". Opt-out wording: "[opt-out wording]".
Audience: A lead who contacted me once about a property or about buying or selling, has not committed to working with me, and may be months from a decision.
Voice: [paste voice file, or: "Plain, specific, warm. Short. Sounds like a person who does this every day and is not in a hurry."]
Rules: Use only facts I give you; ask instead of guessing. Every touch states its reason in one line above the message (a market fact, a resource, or a question) and the message is built on that reason; no touch may be "checking in." Market numbers appear only as square-bracket fields I will fill. Each touch ends with one question or one clear next step, never both. No language about who should live anywhere or who the neighbors are. No references to schools, safety, churches, or demographics. No pressure language. Every text touch ends with the opt-out wording. Every email touch ends with "[license disclosure line]". The phone call touch is a short list of talking points for me, not a script to read. The mail touch is a note of under 60 words.
Format: Twelve numbered touches in schedule order. For each: the day number, the channel, the reason line, then the message. Texts under 320 characters. Emails under 120 words with a subject line under 6 words. After the twelve, a short list of every square-bracket field used, so I can map them to my CRM. After the output, list every fact you used and which input it came from.
------------------------------------------------------------

Check.

- Read every reason line. If a reason is vague ("to stay in touch"), rewrite the touch or cut it.
- Confirm no number appears outside a square-bracket field, and every resource named is one you actually have.
- Confirm opt-out wording on every text and the disclosure line on every email.
- Run the Fair Housing scrub (P-04.1) on the full sequence.
- Load one touch into your sending tool and send it to yourself. Check the fields render and the STOP reply works.

Ship. Load the sequence into your CRM or email tool. Map every bracket field to a CRM field or mark it "fill by hand." Save the brief to your brief library as "Nurture, 12 touches, v1," and keep the output as your sequence master copy.

Compliance check. Ch. 4.6 (calls, texts, and bots), 4.3 (license disclosure), 4.1 (Fair Housing). Treat every automated marketing text as needing prior express written consent and a working opt-out before the first send (T-09.2); the call touch is made by you, not a voice agent.
