# Turn Parade conversations into follow-up buyers can use

Parade follow-up works when every reply starts with the visitor's actual question. Reconcile sign-ins and host notes, sort contacts by stated intent, assign one next action and send the most relevant project or process material. Use the visitor's recorded contact choices for later messages, and route plan and lot questions for review and representation questions to your listing agent.

## What has to happen before anyone sends a follow-up?

Reconcile the event record. A visitor may scan a project code, talk with a host and submit a form later. That is not automatically three people. Match records carefully using what the visitor supplied, keep the known source details and leave uncertain matches uncertain.

Bring host notes into the same review. A form may say "building information," while the host wrote that the visitor owns a narrow [infill lot](/glossary/infill-lot/) and asked about garage access. The second detail changes the reply. Keep useful business context only. Personal observations do not belong in a lead record.

This depends on a clean collection system. Use the [builder event sign-in guide](/articles/events-and-showings/builder-event-sign-in/) to decide which fields, notices and staff notes belong in the workflow.

## How should Parade contacts be sorted?

Sort by the next information need, not by how enthusiastic someone sounded in a crowded kitchen. A quiet lot owner with a specific site question may be ready for a substantive conversation. An excited visitor may only be collecting finish ideas. Both deserve a useful reply. They do not need the same sequence.

### Use intent lanes the team can act on

| Known signal | First useful response | Internal owner |
| --- | --- | --- |
| Owns or controls a lot | Site-review inputs and service-area fit | Preconstruction or site review |
| Asked about a plan | Current plan page and reviewed option notes | Sales with design review |
| Asked about allowances or selections | Process explanation from current documents | Selections or sales |
| Asked about a model or spec | Accurate status and showing path | Sales |
| Visitor has a buyer's agent | Reply through your listing agent, with the buyer's agent included | Listing agent |
| General design interest | Project story or relevant educational page | Nurture owner |

Do not build a score from body language or a host's memory of clothing, vehicle or perceived spending power. Use disclosed project facts, questions and actions. Leave unknown project details blank and assign a clarifying question when the next action depends on them.

## What should the first message contain?

The first message proves the team listened. Name the house or feature discussed, answer what approved material can answer and state the next step for anything that needs review. One useful link beats a folder of brochures.

### Build the message in four parts

1. **Context:** name the Parade house or conversation so the visitor knows why the message arrived.

2. **Answer:** address the specific plan, lot, selection or process question with current facts.

3. **Boundary:** say when a request needs plan, field, estimating or contract review.

4. **Next action:** offer one sensible step: send a lot record, review a plan page, schedule a process discussion.

Skip the fake familiarity. Hosts met many people during the open period, and visitors know it. Specific project context is credible. Check the original host note before you refer to a specific conversation.

## Which questions need a person before a reply goes out?

Anything that can create a construction, schedule, representation or contract expectation. A saved response can explain how the process works. It cannot decide whether a wall can move, whether an allowance applies, whether a lot works, or any representation question.

Route plan changes to design and estimating. Route site questions to the lot-review owner. Route current inventory and showing details to the person who maintains status. Route representation questions to your listing agent, who handles them under the listing agreement and the brokerage's process. When the Parade house is listed, send the listing agent the same reconciled questions, so the MLS listing and your follow-up say the same thing. The [listing agent guide](/guides/listing-agent-for-custom-builders/) covers that partnership.

### Use AI for drafting, not for commitments

The Claude and Codex agents we run organize approved notes, suggest a reply based on the visitor's question and check that the right project link is included. A person reviews the source record, the current status and any promise before sending. No agent infers plan feasibility or contract meaning from a hurried event note.

## How does follow-up continue without becoming noise?

Let the visitor's stage set the cadence. Someone who asked for a lot review needs a clear [handoff](/process/handoff/) and a visible owner. A visitor comparing plans may want a related plan explanation. An early browser can get occasional project or process material that matches the stated interest.

Stop a sequence when the contact replies, asks for no more messages or moves into a person-led conversation. Automated messages should not keep talking past an active discussion. Record the change so another campaign does not restart the same introduction.

### Keep every touch tied to a reason

- Send a reviewed answer when the team promised one.

- Send a project update when it changes the visitor's stated decision.

- Send a process page when it resolves a repeated question.

- Ask for a next step when the prior exchange supports it.

- Close the active task when no further action was agreed.

For the house-side setup that produces clean notes, see [Parade planning](/articles/events-and-showings/parade-of-homes-planning/). For a disciplined performance review, use [event return measurement](/articles/events-and-showings/measuring-event-roi-without-guessing/).

### How do you verify that promised replies went out?

Inspect records, not impressions. Confirm that promised answers were assigned, that replies came from the correct owner and that next actions were updated. Separate delivery activity from meaningful movement. A sent email is not a plan conversation, a site review or a scheduled meeting.

The [Lead attribution stage](/process/lead-attribution/) connects the event source, the form, the call route and the CRM you own. Keep the Parade house, the open period, the known campaign path, the visitor interest and the later status. If a visitor first found you somewhere else, keep that nuance instead of forcing the event to take full credit.

After review, feed repeated questions back into the project page and the host notes. Keep the reconciliation of promised replies in this workflow, and send broader source-performance decisions to the event measurement review. If many visitors misread what was standard, optional or selected for the display house, fix the explanation before the next event. The connected planning, capture and measurement workflows are in the [events and showings library](/articles/events-and-showings/).

## What do builders ask about Parade follow-up?

### Should every Parade contact get the same sequence?

Match Parade follow-up to each visitor's stated interest and agreed next action. Lot owners, plan shoppers, represented buyers and design browsers need different information.

### Can an AI agent send replies automatically?

Use AI agents to draft Parade replies from approved records. Have a person review context, project status and commitments before any event follow-up goes out.

### What if the host notes and the form disagree?

When Parade host notes conflict with a form, keep both sources and check the underlying records. Ask a clarifying question instead of replacing submitted information with an assumption.

### When should a contact leave the event sequence?

Stop a Parade follow-up sequence when a contact opts out, enters a person-led conversation or completes the agreed step. Record the change so another campaign does not restart the introduction.