# Contractor Storm Estimate Follow-Up Script Pack

Use these scripts after storm inspections, estimates, tarp requests, insurance-process questions, proof gaps, restoration-risk leads, and no-show risks.

## Day 0 — confirmation
“Thanks for talking with us today. I have your storm damage notes as: [roof leak / active leak / tarp request / storm inspection / insurance question]. The next step is [inspection / estimate / photos / proof link / dispatch]. We’ll follow up by [time].”

## Day 1 — proof
“Here are a few examples, reviews, and insurance-process notes so you can see how we handle storm damage jobs like this. Want us to hold the inspection/estimate window?”

## Day 3 — estimate follow-up
“Checking in on the storm estimate. Do you want us to adjust scope, answer insurance questions, review financing/warranty options, or schedule the next step?”

## Day 7 — no-show control
“We can keep a spot open if this is still active, but storm inspection windows are moving quickly. Reply YES and we’ll confirm timing; reply LATER and we’ll send a proof link instead.”

## Day 14 — reactivation/review/referral
“If the storm issue is handled, glad you’re safe. If you still need help, reply with photos or a callback time. If we completed the job, this is the right moment to ask for a review or referral.”

## Product-fit notes
Webzaz fits only when storm estimate follow-up needs service-page proof, quote-form clarity, reviews, photos, financing, warranty, FAQs, insurance-process copy, or city/service coverage. LocalKit fits only lightweight local-action/profile routing. AI answering, scheduling, dispatch, estimate ownership, tarping, inspections, reviews, referrals, and no-show controls stay separately measured.