# Contractor Storm Quote CTA Routing Map

Use this before publishing storm quote buttons, emergency call blocks, inspection request forms, documentation help CTAs, and thank-you routes.

| CTA route | Use when | Proof required | Destination |
| --- | --- | --- | --- |
| Emergency call CTA | Active hazard, urgent damage, no-heat/no-cool, electrical risk, water intrusion | Service proof, city proof, response expectation | Phone route |
| Inspection request CTA | Visitor needs damage checked or documented | Before-and-after photos, review proof, insurance-process boundary | Form or calendar |
| Quote request CTA | Visitor knows the repair scope | Testimonials, project proof, quote-form fields | Quote form |
| Documentation help CTA | Visitor needs photos, notes, or scope documentation | Photo proof, permission status, FAQ language | Form / FAQ / callback |
| Follow-up CTA | Visitor already requested help | Thank-you route, next-step expectation | Thank-you / email / SMS follow-up |

## Owner growth route

- Use emergency call CTAs when active hazards need speed.
- Use inspection request CTAs when damage is unclear and proof/context matters.
- Use quote request CTAs when the repair scope is known and city/service proof can support conversion.
- Preserve source, primary_source, route intent, destination, and thank-you expectation across the click.
- Webzaz fits only when the CTA, proof, form, gallery, or thank-you route belongs on the website.

## Guardrails

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