# Contractor Storm Form Confidence Checklist

Use this worksheet before sending storm traffic to a vague quote or inspection form. The goal is not more form fields. The goal is a form that tells homeowners what happens next and keeps the lead source visible to the team.

## Form-confidence fields

- **Form type:** emergency help, inspection request, quote request, documentation help, estimate follow-up, or repair scheduling.
- **Confidence note:** one sentence beside the form explaining who responds, when they respond, and what happens after submit.
- **Callback expectation:** same-day, after-hours, next-business-day, or emergency escalation without promising guaranteed repair, insurance outcome, payout, or repair timeline.
- **Proof context:** city proof, service proof, before-and-after photo, review proof, testimonial proof, insurance-process note, or source screenshot.
- **Source attribution:** source, primary_source, search query, CTA route, storm job type, city, service, urgency, proof owner, and thank-you expectation.

## storm form confidence checklist

1. Match the form to one clear intent: emergency help, inspection request, quote request, documentation help, or estimate follow-up.
2. Add the form-confidence note directly above or below the button.
3. Remove fields that do not change triage, callback priority, proof routing, or estimate quality.
4. Attach the approved proof that made the CTA believable.
5. Preserve source and primary_source through the thank-you route.
6. Show the homeowner what happens after submit.
7. Keep Webzaz-fit website fixes separate from LocalKit, GBP/profile, review, referral, CRM, dispatch, scheduling, AI answering, estimate follow-up, and no-show workflows.

## Product-fit boundary

Webzaz fits website form placement, CTA copy, proof hierarchy, storm landing pages, quote-form confidence copy, and thank-you page routing. LocalKit fits profile-style routing. CRM, dispatch, scheduling, AI answering, estimate follow-up, and no-show tools stay separately measured.

## 17:00 ET growth-route QA notes

- Internal-linking QA: route homepage, footer, Start Here, storm website proof hub, website resources, related downloads, and contextual website/form articles here only when the reader needs storm quote form confidence, callback expectation clarity, proof beside the form, or a source-preserved thank-you route.
- Human copy QA: preserve contractor storm form confidence checklist, storm quote form confidence, what happens after submit, callback expectation, proof beside the form, and source-preserved thank-you route language.
- Product-fit QA: Webzaz fits only for form placement, CTA copy, proof hierarchy, storm landing pages, quote-form confidence copy, and thank-you-page routing. LocalKit/profile, reviews, referrals, CRM, dispatch, scheduling, AI answering, estimate follow-up, no-show automation, and insurance claim workflows stay separate. No exact Webzaz price points.