# Contractor Storm Lead Handoff Checklist

Use this after a storm CTA click so source, urgency, proof context, and next action do not disappear.

| Handoff field | Capture |
| --- | --- |
| Source attribution | source, primary_source, search query, landing page, CTA route, placement, destination |
| Urgency | emergency call, inspection request, quote request, documentation help, follow-up |
| Proof context | before-and-after photos, review/testimonial proof, city proof, service proof, documentation context |
| Owner | CSR, owner, estimator, dispatcher, technician, marketer |
| Thank-you expectation | response window, next step, what to prepare, documentation boundary |
| Follow-up route | phone, form, email, SMS, CRM, calendar, thank-you page |

## Guardrails

- Do not imply insurance claim approval, coverage, payout, claim outcome, or timeline promises.
- Preserve source, primary_source, search query, route intent, placement, destination, and thank-you routing.
- Webzaz fits website handoff placement across service pages, city pages, landing pages, quote forms, FAQs, galleries, homepage trust sections, and thank-you routes.
- LocalKit, QR/profile routes, emergency call routing tools, AI answering, scheduling, dispatch, estimate follow-up, CRM, and no-show controls stay separate.

## Owner growth route

- Preserve source-preserved handoff proof: source, primary_source, search query, CTA route, proof context, thank-you expectation, urgency, and destination.
- Assign next-owner accountability before the lead reaches the inbox: callback owner, inspection owner, estimate owner, second-touch deadline, and escalation path.
- If the handoff breaks because the website hides proof, buries the form, or sends vague confirmation copy, route to website proof and lead-response fixes before buying more traffic.
- Product-fit QA: Webzaz fits only when the website must preserve lead source, proof, CTA route, form trust, and thank-you expectations. LocalKit/profile, CRM, dispatch, scheduling, AI answering, review/referral, no-show, and insurance-claim workflows stay separate.