Review point 1
What the first message needs to do
A homeowner who requests an estimate after hours does not need a long sales sequence. They need to know the request reached the roofer and what happens next.
Keep the message short. Acknowledge the request, state when the office will follow up, and ask one qualifying question that helps the team prepare. Do not imply that a person is available when the office is closed.
Operational checklist
- Confirm receipt without promising an immediate inspection.
- State the real office-hours handoff.
- Ask one relevant question, such as whether the request is about an active leak or a planned estimate.
- Give the homeowner a clear way to reply.
Review point 2
Build the morning handoff before sending anything
The after-hours message is only useful when the next owner is known. The request should appear in a queue with a named office or sales owner, the original context, and the promised follow-up window.
The next-business-morning call or email should continue the same conversation. It should not force the homeowner to repeat the details already supplied.
Review point 3
A bounded after-hours sequence
The captured LumioForge workflow uses a simple sequence: an immediate confirmation and question, a same-night acknowledgement when the homeowner replies, a next-morning human call or email, and a same-day follow-up if the first human attempt does not connect.
Automation stops when the homeowner replies, books, declines, or asks not to be contacted. Exceptions stay visible for a person to handle.
Review point 4
What to review each week
Review whether every after-hours request received the approved confirmation, whether a real owner took over at the promised time, and whether replies stopped the remaining sequence. A missed handoff is an operating issue, not a reason to add more messages.
Review point 5
Use a four-part handoff checklist
Before an after-hours message is enabled, write down the visible state change at each boundary. The checklist should be understandable without relying on a dashboard animation or a person remembering an unwritten rule.
Operational checklist
- Source: which approved form, inbox, or booking path created the request?
- Owner: who is the current handler, and who is the backup?
- Stop: which supported reply, booking, decline, or opt-out ends eligible follow-up?
- Alert: where does a failed or overdue action become visible to a person?
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)