# Contractor Storm Damage Follow-Up Sequence

Use this sequence after the first storm callback so roof leak calls, active leaks, no-heat/no-cool calls, electrical hazards, tarp requests, storm damage inspections, restoration-risk leads, insurance-process questions, diagnostics, estimates, and no-show risks do not disappear after triage.

## Day 0 — confirm the route
- Confirm the emergency signal: roof leak, active leak, no heat, no cooling, electrical hazard, lockout, restoration risk, tarp request, storm damage inspection, or repeat-customer risk.
- Confirm the first callback result: dispatch, tarp, diagnostic, inspection, estimate, photos requested, proof-first, AI answering handoff, scheduling, or no-show-control route.
- Preserve source: GBP, LSA, website phone, form, text, referral, QR, invoice, voicemail, social profile, repeat customer, or storm resource path.

## Day 1 — send proof and next step
- Send city/service-page proof, reviews, storm damage photos, FAQs, insurance-process notes, financing, warranty, and quote-form clarity when trust is the blocker.
- Keep Webzaz demand separate: use it only when service-page proof or quote-form readiness is the actual issue.

## Day 3 — estimate and inspection follow-up
- Confirm estimate status, inspection timing, photos, decision-maker, access, and urgency.
- Route low-commitment inspections through no-show controls before scheduling more capacity.

## Day 7 — no-show and reactivation
- Reactivate no-answer leads with one clear callback option and one proof link.
- Keep AI answering, scheduling, dispatch, callback ownership, tarping, inspection, and no-show-control decisions separately measured.

## Day 14 — review, referral, or nurture
- Ask completed storm jobs for reviews and referrals.
- Move unconverted but qualified leads into seasonal storm-damage nurture.
- LocalKit fits only for lightweight GBP, QR, social, invoice, referral, review, and local-action routing.