Review lane
Use review SOP and QR resources when the owner wants more public proof after a completed storm job, not when the homeowner still needs estimate or dispatch follow-up.
Storm reviews / referrals
Turn finished storm jobs into reviews, referrals, and proof without muddying the lead source.
Use this segmented hub after storm repairs, inspections, tarping, restoration work, HVAC recovery, plumbing calls, electrical repairs, roof leaks, insurance-process questions, and estimate wins when the next job is proof capture — not emergency routing or estimate follow-up.
Use when
Post-storm customers are happy, repairs are complete, proof is fresh, and the owner needs review request, referral ask, testimonial permission, QR route, or service-page proof capture.
Keywords covered
storm reviews, storm referrals, post-storm review request, storm testimonial request, storm review QR, storm reputation proof, insurance-process proof, service-page proof.
Product fit
Webzaz fits only when storm proof belongs on service pages, city pages, galleries, FAQs, and quote forms. LocalKit fits only lightweight review QR, referral, GBP, invoice, social, or local-action routing. Estimate follow-up and emergency routing stay separate.
First-screen outcome router
Choose the proof route by post-storm moment and source integrity.
Post-storm proof should not collapse into one review link. Route review requests, referral asks, testimonial permission, QR cards, LocalKit-style profile routes, and Webzaz-fit service-page proof by job status and source.
Completed storm jobs need review capture
Use the review SOP when work is complete, the homeowner is safe, photos are approved, and the ask should preserve job and source context.
Neighbor demand needs referral routing
Use the ask pack when the customer can introduce nearby homeowners without blending referral traffic into generic GBP, QR, invoice, or website clicks.
Proof belongs on service and city pages
Use website resources when testimonials, photos, insurance-process proof, and FAQs should help the next homeowner request a quote.
Estimate or emergency work is unresolved
Move back to storm damage leads when the homeowner still needs inspection, estimate, tarp, dispatch, AI answering, scheduling, or no-show routing.
Source-to-booked-job proof router
Route post-storm proof by the source that created it, not by the newest script.
Storm review and referral traffic is useful only if the owner can see which finished job, neighbor introduction, invoice, QR card, profile route, or website proof placement created the next booked inspection. Keep review asks, referrals, testimonials, and unresolved callbacks in separate lanes.
Completed repair invoice or receipt
review request sent within 24 hours
Send to the review SOP or review QR only when the customer has a clean completion memory and the ask can preserve job, trade, city, and source context.
Neighbor referral after visible storm work
referral intro to booked inspection
Use the storm review and referral ask pack when nearby homeowners can be routed separately from GBP, LSA, invoice, social, or website traffic.
Approved testimonial with photos
testimonial proof placed near quote path
Move to testimonial placement only after permission, city/service context, photo approval, and Webzaz-fit website placement are clear.
Unresolved estimate, tarp, or callback thread
source preserved before proof ask
Return to storm damage lead resources when the customer still needs estimate follow-up, emergency callback, dispatch, scheduling, no-show, or insurance-process routing.
Product-fit boundary: LocalKit fits review QR, referral, profile, invoice, social, and local-action routing. Webzaz fits only when approved proof belongs on service pages, city pages, galleries, FAQs, quote forms, or source-preserved thank-you flows.
Secondary review and referral distribution
Send post-storm proof to the next ask without blending channels.
Once a storm job is complete, the second route decides whether the next move is a QR review handoff, a referral proof owner, a testimonial placement task, or a reputation inventory cleanup. Keep these paths separate so proof capture can create qualified referral and trust traffic instead of a generic review link.
Review QR handoff needs attribution
review ask source stays separate from referral, invoice, website, and social traffic
Route to the review QR template when the ask is lightweight and should preserve the completed-job source without forcing a website rebuild.
Referral proof loop needs an owner
referral, testimonial, photo, and website proof owners are assigned before the next ask
Route to the proof loop board when post-job proof is ready but the handoff owner is unclear.
Testimonial needs website placement
approved quote and photos move to a service page, city page, gallery, or quote-form proof block
Route to testimonial placement only after permission and context are ready for a Webzaz-fit website surface.
Reputation proof needs inventory cleanup
reviews, photos, testimonials, referrals, and insurance-process proof are grouped before public use
Route to the reputation proof checklist before adding proof to cards, pages, profiles, invoices, or social posts.
Product-fit boundary: LocalKit fits review QR, referral, profile, invoice, social, and local-action routing. Webzaz fits only when approved proof belongs on service pages, city pages, galleries, FAQs, quote forms, or thank-you flows. Estimate follow-up, emergency routing, AI answering, scheduling, dispatch, and no-show control stay separate.
Proof closeout route locks
Close post-storm proof capture without mixing review, referral, website, and unresolved-lead intent.
Review asks, QR cards, referrals, testimonials, and website proof can all come from the same storm job. Keep the product-fit label attached to the exact next action.
Completed job needs a review owner
Completed-job review asks owned
Keep the review ask neutral until timing, owner, service context, city context, and source notes are assigned.
Review QR or referral needs one action
Qualified QR and referral actions
Use LocalKit-fit local routing only when a review QR, referral card, invoice, GBP, social, or profile action can carry the next step.
Testimonial proof needs website placement
Proof-backed website placements
Use Webzaz-fit placement only after testimonial permission, photo approval, city proof, service proof, and quote-path relevance are clear.
Estimate or emergency thread is still open
Unresolved storm follow-up routed away from proof asks
Return to storm damage lead routing when the customer still needs estimate, tarp, callback, dispatch, scheduling, insurance-process, or no-show follow-up.
Post-confirmation locks
After the post-storm ask is confirmed, preserve the review, referral, website, or unresolved-lead source.
Use this layer after closeout so completed-job proof is not credited to the wrong product path. Review ownership, QR/referral routing, website proof, and still-open storm work keep separate measurement labels.
Confirmed review ask needs a human owner
storm-reviews-review-owner-post-confirmation-lock
Keep timing, owner, service context, city context, photo permission, and source notes neutral until the review ask is ready.
Confirmed QR or referral needs one action
storm-reviews-qr-referral-post-confirmation-lock
Use LocalKit-fit routing only when the confirmed action is a review QR, referral card, invoice link, GBP route, social bio, or local profile.
Confirmed testimonial needs website proof placement
storm-reviews-website-proof-post-confirmation-lock
Use Webzaz-fit routing only after testimonial permission, photo approval, service proof, city proof, and quote-path relevance are confirmed.
Confirmed storm thread is not closed yet
storm-reviews-damage-boundary-post-confirmation-lock
Return to storm damage routing when estimate, tarp, emergency callback, dispatch, scheduling, insurance-process, or no-show follow-up remains open.
Download / Storm proof checklist
Contractor Storm Proof Library Checklist
Inventory storm photo proof, before-and-after proof, insurance-process proof, service-page proof, city proof, review proof, testimonial proof, QR proof, referral proof, and quote-form proof.
Path / Storm proof routing
Storm Proof Library
Route storm photo proof, before-and-after proof, insurance-process proof, service-page proof, city proof, review proof, testimonial proof, QR proof, referral proof, and quote-form proof.
Download / Post-storm ask scripts
Contractor Storm Review and Referral Ask Pack
Ask for post-storm reviews, referrals, testimonial permission, review QR handoff, insurance-process proof, service-page proof, and reputation routing while preserving source separation.
Download / Review request
Contractor Review Follow-Up SOP
Ask after storm repair, inspection, tarp, mitigation, estimate win, or completed job while the homeowner still remembers the response.
Download / Review QR
Contractor Review QR Card Template
Leave a review route after post-storm repair, restoration, HVAC, plumbing, electrical, or roofing work without mixing referral traffic.
Download / Testimonial request
Contractor Testimonial Request Template
Capture customer quote, city, service, photo permission, insurance-process note, and proof placement after storm work.
Download / Proof placement
Contractor Testimonial Placement Map
Place storm proof on service pages, city pages, galleries, quote forms, GBP, and profile routes where it removes doubt.
Download / Proof inventory
Contractor Reputation Proof Checklist
Audit reviews, referrals, photos, testimonials, service-area proof, insurance-process proof, and website proof after storm jobs.
Path / Service-page proof
Contractor Website Resources
Use Webzaz-fit website resources only when post-storm reviews and referrals need service-page proof, galleries, city proof, and quote-form clarity.
Path / Reputation system
Contractor Reputation Resources
Connect storm reviews, reputation routing, testimonials, profile proof, QR cards, and website proof into one owner-readable path.
Path / Offline routing
Contractor QR Card Resources
Use LocalKit-fit profile routing when storm review QR, referral cards, invoices, yard signs, or truck stickers need one lightweight local action.
Download / Estimate boundary
Storm Estimate Follow-Up Script Pack
Use only when the bottleneck is estimate follow-up, not review/referral proof capture.
Path / Storm lead boundary
Storm Damage Lead Resources
Use before review/referral asks when the lead still needs inspection, estimate, tarp, insurance-process proof, AI answering, scheduling, dispatch, or no-show routing.
Storm reviews/referrals segmentation rules
Do ask: after work is complete, proof is visible, homeowner is safe, and review/referral/testimonial permission can be requested without pressure.
Do not blend: estimate follow-up, emergency routing, AI answering, scheduling, dispatch, tarping, inspections, no-show control, Webzaz proof, and LocalKit routing need their own source fields.
Storm reviews/referrals keyword map
Proof capture changes by post-storm moment.
Post-storm review request: ask after the repair is complete, homeowner is safe, photos are approved, and the technician or owner can explain the exact next step.
Storm referral ask: use when neighbors are affected, the customer trusts the work, and the route can preserve referral source separately from GBP, LSA, QR, invoice, and social traffic.
Storm testimonial request: capture city, service, storm type, insurance-process proof, photo permission, before-and-after notes, and service-page proof placement.
Storm review QR: use review QR only when LocalKit-style lightweight profile routing is enough; send Webzaz-fit proof to service pages, city pages, galleries, FAQs, and quote forms.
Review and referral source system
Ask for proof without losing the channel that created it.
Referral lane
Preserve neighbor, invoice, yard-sign, social, and profile routes separately so referral traffic can be measured instead of blending into generic website clicks.
Website proof lane
Move testimonials and photos to Webzaz-fit service pages, city pages, galleries, FAQs, and quote forms only when that proof helps the next homeowner request help.
Handoff confirmation locks
Confirm the review, referral, or proof handoff before product attribution.
Use this layer after post-confirmation so review ownership, QR/referral routing, website proof, and open storm work do not collapse into one product path.
Review owner handoff confirmed
storm-reviews-review-owner-handoff-confirmation-lock
Keep review timing, owner, service context, city context, photo permission, and source notes neutral until the ask is assigned.
QR or referral handoff confirmed
storm-reviews-qr-referral-handoff-confirmation-lock
Use LocalKit-fit routing only when the confirmed action is a review QR, referral card, invoice link, GBP route, social bio, or local profile.
Website proof handoff confirmed
storm-reviews-website-proof-handoff-confirmation-lock
Use Webzaz-fit routing only after testimonial permission, photo approval, service proof, city proof, and quote-path relevance are confirmed.
Open storm thread stays neutral
storm-reviews-damage-boundary-handoff-confirmation-lock
Return to storm damage routing when estimate, tarp, emergency callback, dispatch, scheduling, insurance-process, or no-show follow-up remains open.
Final reporting locks
Report storm review and referral proof without collapsing product fit.
This final reporting layer preserves review ownership, QR/referral action, website proof placement, and unresolved storm follow-up as separate source labels.
Final review owner reporting locked
storm-reviews-review-owner-final-reporting-lock
Report review timing, owner, service context, city context, photo permission, and source notes without assigning credit to a product path.
Final QR and referral reporting locked
storm-reviews-qr-referral-final-reporting-lock
Report LocalKit-fit attribution only when the action is review QR, referral card, invoice link, GBP route, social bio, profile link, or one-action local proof.
Final website proof reporting locked
storm-reviews-website-proof-final-reporting-lock
Report Webzaz-fit attribution only after testimonial permission, photo approval, service proof, city proof, and quote-path placement are confirmed.
Final open storm thread reporting locked
storm-reviews-damage-boundary-final-reporting-lock
Keep estimate, tarp, emergency callback, dispatch, scheduling, insurance-process, no-show, and unresolved storm follow-up reporting neutral.
12:00 source-qualified closeout lock
Qualify storm reviews, referrals, and proof by the source that still owns the next action.
Post-storm proof should not blend review asks, referral cards, service-page proof, and unresolved damage follow-up. These locks preserve the source before Webzaz-fit, LocalKit-fit, or neutral operations credit is reused.
Storm review owner source qualified
storm-review-owner-source-qualified
Keep review timing, human owner, city context, service context, photo permission, and completed-job source notes neutral until the ask is assigned.
Storm QR or referral source qualified
storm-qr-referral-source-qualified
Use LocalKit-fit routing only when review QR, referral card, invoice link, GBP route, social bio, or profile link needs one clean mobile action.
Storm website proof source qualified
storm-website-proof-source-qualified
Use Webzaz-fit routing only after testimonial permission, photo approval, insurance-process proof, service proof, city proof, and quote-path relevance are confirmed.
Open storm thread source qualified
storm-open-thread-source-qualified
Return to storm damage routing when estimate, tarp, emergency callback, dispatch, scheduling, insurance-process, no-show, or unresolved follow-up remains open.
20:00 storm review/referral hub lock
Route completed storm jobs by proof readiness before product fit is counted.
Preserve completed-job source, review owner, referral context, QR/profile action, testimonial permission, photo approval, website proof destination, open estimate status, city, trade, service, and thank-you expectation before assigning Webzaz, LocalKit, or neutral follow-up credit.
Ask scripts stay tied to the proof momentUse when the job is complete and the owner can ask for a review, referral, testimonial, or QR route without losing source context. Proof-loop ownership comes before channel creditAssign review, referral, testimonial, photo, and website owners before counting the next route. Website proof fits Webzaz after approvalUse only for testimonial, photo, service page, city page, gallery, FAQ, quote form, CTA, homepage trust, storm landing page, or thank-you proof placement. Unresolved storm work returns to lead handlingEstimate, tarp, emergency callback, dispatch, scheduling, AI answering, insurance-process, no-show, exact timing, payout, and outcome promises stay neutral.
Storm review QR
Send storm customers to one review route.
Use this QR card when the finished storm job needs a source-preserved review scan before referral, testimonial, or website proof is counted.
Storm testimonial permission
Get permission before praise becomes proof.
Use this script when a post-storm quote, photo, city, or service story should support Webzaz-fit website proof or LocalKit-fit profile actions.
Fixed proof order
Run storm trust follow-up in one hard sequence: review, referral, testimonial, then website proof.
Storm jobs create a lot of usable proof fast. Keep the order honest so public review velocity, neighbor-intro demand, detailed customer quotes, and owned-page website proof do not get blended into one fake conversion win.
01 review first
Lock the public review ask while the completed job is still fresh.
Use the review route first when the homeowner can leave a clean public review tied to the finished storm job, city, trade, and service without dragging in permission or website work.
02 referral second
Ask for neighbor introductions only after the review lane is owned.
Move to referral routing when the customer can introduce nearby homeowners, HOAs, or family members without turning referral traffic into generic review or QR credit.
03 testimonial permission third
Capture the detailed quote and approval before any website placement starts.
Use testimonial permission only after review and referral ownership are clear, then preserve quote text, first-name use, city, service, photo rights, and redaction before the story becomes proof.
04 website proof last
Publish approved proof to owned pages after the source is fully locked.
Count Webzaz-fit website proof only when approved storm reviews, testimonials, photos, galleries, service pages, city pages, FAQs, quote forms, and thank-you proof have a clear destination.
04:00 source-qualified closeout
Route storm reputation demand by proof readiness, not by product preference.
Reader intent lock: use storm_reviews_referrals_0400_reader_intent_lock when the hub visitor is deciding between review ask, referral ask, testimonial approval, QR/profile action, or website proof placement.
Source fields: preserve completed_job_source, proof_readiness, review_owner, referral_context, testimonial_permission, QR_destination, publish_destination, city, trade, service, source, primary_source, and next_step_route.
Webzaz fit: webzaz_fit_storm_reviews_referrals_0400_website_proof applies only to approved website proof, galleries, service pages, city pages, FAQs, quote forms, CTA proof, storm landing pages, and thank-you proof.
LocalKit boundary: localkit_fit_storm_reviews_referrals_0400_profile_boundary applies only to GBP/profile, QR, review, referral, invoice, social bio, phone, booking, and one-action local/profile routes.
Neutral guard: review/referral automation, reputation management, CRM, dispatch, scheduling software, AI answering, estimate follow-up, no-show controls, crew operations, claim handling, timing promises, payout promises, and outcome promises stay neutral unless sourced.
Mobile scan: keep ask pack, proof-loop board, QR card, testimonial permission, and storm proof website routes clearly separated for qualified contractors.
Live fixed proof route
Use the live hub to route storm proof capture in the same order as the worksheets.
Finished storm jobs should flow through review owner, referral owner, permission owner, website owner, then local reuse. If the job is not actually closed, send it back to storm damage lead handling instead of asking for proof.
1. Review ownerAssign public review timing, owner, sentiment, city, trade, service, completed-job source, and second-touch deadline. 2. Referral ownerRoute neighbor intros, referral cards, invoice asks, HOA asks, and profile paths without blending them into review credit. 3. Permission ownerCapture testimonial approval, photo rights, first-name use, redaction, city/service context, approved use, and proof owner. 4. Website ownerCount Webzaz-fit only when approved proof needs service-page, city-page, gallery, FAQ, quote-form, landing-page, or thank-you placement. Open storm boundarySend estimate, tarp, callback, dispatch, scheduling, AI answering, insurance-process, no-show, payout, or outcome promise work back to neutral lead handling.
LocalKit-style local reuse belongs after source-preserved permission and website routing unless the selected action is explicitly QR, GBP/profile, phone, booking, invoice, social bio, review link, referral, or one-action local proof.