Contractor Storm Review and Referral Ask Pack
A contractor storm review/referral ask pack for post-storm review requests, referral asks, testimonial permission, review QR handoff, insurance-process proof, service-page proof, and reputation routing.
Owner preview
Who it is for
Roofers, restoration teams, HVAC companies, plumbers, electricians, emergency trades, owners, office managers, dispatchers, estimators, techs, and crew leads asking for post-storm reviews, referrals, testimonials, QR reviews, and proof permission.
What you leave with
A saveable contractor storm review/referral ask pack that captures proof after storm jobs without blending Webzaz, LocalKit, estimate follow-up, emergency routing, AI answering, scheduling, dispatch, or no-show analytics.
What is inside
- ✓Ask for a post-storm review after roof repair, restoration, HVAC recovery, plumbing repair, electrical repair, tarp removal, inspection closeout, or completed estimate win.
- ✓Use separate scripts for storm referral ask, storm testimonial request, storm review QR handoff, insurance-process proof capture, and service-page proof routing.
- ✓Preserve source fields from storm reviews/referrals, storm estimate follow-up, storm damage leads, storm follow-up, storm calls, GBP, QR, invoice, referral, social, and website traffic.
- ✓Keep Webzaz service-page proof, LocalKit profile routing, estimate follow-up, emergency routing, AI answering, scheduling, dispatch, and no-show controls separately measured.
- ✓Give owners, office managers, dispatchers, techs, estimators, and crew leads one safe post-storm proof capture cadence.
Storm proof checklist
Build a storm proof library checklist →Proof routing
Storm proof library →Post-storm proof
Storm reviews/referrals resources →Review SOP
Review follow-up SOP →Testimonial ask
Testimonial request template →Review QR
Review QR card template →Reputation path
Reputation resources →Service-page proof
Website proof resources →Trust note
Built from ProTradeHQ field guides, calculators, and trade-specific growth paths. No vendor ranking pay-to-play.
When a product fits: Webzaz fits only when post-storm proof belongs on service pages, city pages, galleries, FAQs, and quote forms. LocalKit fits only lightweight review QR, referral, GBP, invoice, social, and local-action routing. Estimate follow-up, emergency routing, AI answering, scheduling, dispatch, tarping, inspections, and no-show controls stay separately measured.
Get the download
Tell us where to send it. If we ask one extra question, it is only to point you to the most useful next checklist or guide.
Or open the PDF nowOwner growth route
Turn a finished storm job into the next qualified lead.
This pack is for owners and office teams who need a safe, repeatable way to ask happy storm customers for reviews, referrals, testimonials, and proof permission without sounding desperate or mixing up the channel that should get credit.
Product fit: Webzaz belongs where approved proof improves service pages, city pages, galleries, FAQs, and quote forms. LocalKit belongs on lightweight review QR/profile/referral handoffs. Everything else stays operationally separate.
Storm review/referral ask QA
Use the right ask for the proof moment.
Post-storm review request: ask when the customer is safe and the repair or inspection outcome is clear.
Storm referral ask: ask when neighbors are likely affected and referral source can be preserved.
Storm testimonial request: capture city, service, insurance-process proof, photos, and permission.
Storm review QR handoff: use QR only when lightweight LocalKit-style profile routing is enough.
Storm review/referral script keyword map
Match the script to the proof route, not just the happy customer.
post-storm review request script: use after completion, inspection closeout, tarp removal, mitigation handoff, or estimate win when the homeowner can speak to response, communication, and outcome.
storm referral ask script: use when neighbors likely have roof leaks, water damage, HVAC recovery, plumbing repairs, or electrical issues and referral source can be preserved.
storm testimonial permission script: capture city, service, storm type, insurance-process proof, before-and-after photos, first-name permission, and service-page proof placement.
storm review QR handoff script: send LocalKit-fit review QR/profile routes only when lightweight profile routing is enough; route Webzaz-fit proof to service pages, city pages, galleries, FAQs, and quote forms.
Final reporting locks
Preserve the source before the ask becomes a review, referral, testimonial, or proof route.
This lock keeps the storm ask pack from blending review scripts, referral QR, website proof, and still-open follow-up into one generic lead magnet result.
Review request source reporting locked
storm-review-ask-review-request-final-reporting-lock
Keep post-storm review timing, trade, city, service, owner, and permission labels neutral until the ask is sent.
Referral and QR source reporting locked
storm-review-ask-qr-referral-final-reporting-lock
Use LocalKit-fit reporting only for review QR, referral cards, invoice links, GBP routes, social bios, profile links, and one-action local routes.
Testimonial website proof reporting locked
storm-review-ask-website-proof-final-reporting-lock
Use Webzaz-fit reporting only when testimonial permission, photo approval, city proof, service proof, gallery, FAQ, quote-form, or thank-you proof placement is ready.
Open storm follow-up boundary reporting locked
storm-review-ask-storm-boundary-final-reporting-lock
Return estimate, tarp, inspection, callback, dispatch, scheduling, insurance-process, AI answering, and no-show work to neutral storm lead reporting.
20:00 review/referral source lock
Keep the review ask, referral ask, testimonial permission, and open storm follow-up in separate lanes.
Preserve completed-job source, trade, city, proof moment, ask type, proof route, owner, and thank-you expectation before this pack gets credit for Webzaz-fit website proof, LocalKit-fit profile actions, or neutral follow-up work.
Storm ask split
Separate the QR review ask from testimonial permission.
04:00 source-qualified closeout
Keep the post-storm ask tied to the proof moment before it becomes a generic review request.
Reader intent lock: use storm_review_referral_ask_0400_reader_intent_lock when the owner needs to choose review, referral, testimonial, QR, or proof placement after a completed storm job.
Source fields: preserve ask_type, proof_moment, customer_sentiment, review_destination, referral_context, testimonial_permission, city, trade, service, source, primary_source, and next_step_route.
Webzaz fit: webzaz_fit_storm_review_referral_ask_0400_website_proof applies only to approved website proof, galleries, service pages, city pages, FAQs, quote forms, storm landing pages, and thank-you proof.
LocalKit boundary: localkit_fit_storm_review_referral_ask_0400_profile_boundary applies only to GBP/profile, QR, review, referral, invoice, social bio, phone, booking, or one-action local routes.
Neutral guard: review automation, CRM, dispatch, scheduling software, AI answering, estimate follow-up, no-show controls, crew operations, claim handling, timing promises, payout promises, and outcome promises stay uncredited unless sourced.
Mobile scan: show the ask type, proof owner, approval need, and next route before deeper proof-loop or reputation resources.