Review point 1
Use a cadence as a starting point, not a quota
There is limited public, roofing-specific evidence for one perfect follow-up count. Treat the cadence as an operating starting point, then review your own response and booking records.
The immediate response should confirm receipt and explain the next step. Later touches should add context or make the next action easier; they should not repeat the same generic message.
Review point 2
Give each channel a clear role
Use email for context that the homeowner may need to revisit. Use a phone call when a person can clarify urgency, property details, or scheduling. Only use other channels when authorization, technical fit, and the company process support them.
New inquiries and post-estimate follow-up are different workflows. The owner, message, timing, and stop conditions should reflect the stage of the roofing request.
Review point 3
Stop rules matter more than message volume
Stop the sequence when the homeowner replies, books, declines, or opts out. A reply should create a visible human task instead of allowing the next scheduled message to continue.
If a reply does not have a current handler, adding another automated touch does not resolve the ownership decision.
Review point 4
Measure the handoff
Track first-response timing, touches completed, replies, booked inspections, opt-outs, and requests with no owner. Review the workflow before changing the cadence.
Review point 5
Write the cadence as decisions, not just dates
A useful cadence worksheet records why each touch is allowed and what changes the plan. The number of messages is less important than whether the sequence can stop, hand off, and expose an exception safely.
Operational checklist
- Touch purpose and approved message owner.
- Eligible channels, with email as the baseline and SMS only when separately supported.
- Current handler and backup at that point in the sequence.
- Reply, booking, decline, opt-out, pause, and takeover stop conditions.
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)