Review point 1

Map the response path

Write down where each request arrives, who sees it first, who owns the next action, and how that owner knows the homeowner replied. A workflow without a named owner is only a list of intended messages.

The first response should be immediate and honest. It can confirm receipt and the next step without pretending that a salesperson is available around the clock.

Review point 2

Use a short, visible follow-up sequence

The captured source uses a practical five-touch example: immediate confirmation, another useful touch within one to three hours, next-business-morning follow-up, a check-in around day two, and a final useful touch around days five to seven.

This is a planning example, not a universal promise. Each touch needs an owner, an approved message, and a stop rule.

Review point 3

Treat every reply as a handoff

When the homeowner responds, the remaining sequence should stop and the reply should move to a person. The person needs the original request, prior messages, and the next action in one place.

Calculator and website inquiries need the same treatment. The calculation can provide useful context, but it does not replace a human inspection or a clear follow-up owner.

Review point 4

Review the exceptions weekly

Look for requests with no owner, replies without a human response, scheduled touches that continued after a reply, and booked inspections without a clean closeout. Repair those operating gaps before adding volume.

Review point 5

Separate the public route from the internal handoff

For each request source, record public evidence and internal operating decisions in separate columns. That prevents a visible form or phone number from being treated as proof of what happens after a homeowner uses it.

Operational checklist

  • Public route: the visible form, phone, email, chat, or booking path.
  • Internal receipt: the approved system or inbox that receives it.
  • Current handler and backup: the people responsible for the next action.
  • Reply stop and alert: the tested state change and fallback path.
Method and source notes

This guide was materially reviewed against the approved LumioForge source package. No customer results, fabricated benchmarks or unsupported product claims were added.

  • Current-site article capture and metadata inventory: evidence/phase-0/crawl.json and evidence/phase-0/metadata-inventory.csv
  • Approved current-site source register: docs/website-plan/sources.md (S05)