# Contractor Storm Missed Callback Rescue Kit

Use this when storm leads stall after missed callbacks, lost estimates, reschedules, or no-shows.

| Recovery gap | Rescue action |
| --- | --- |
| Missed callback | Same-day callback text, owner assignment, second attempt deadline, source preserved |
| Lost estimate | Estimate follow-up, proof context, estimator/owner route |
| Reschedule risk | New window, access notes, reminder owner, no-show rescue fallback |
| No-show risk | Reminder call/SMS, access check, reschedule path |
| Stale storm lead | Segment by urgency, city, service, proof context, and CTA route |

## Guardrails
- Preserve source, primary_source, search, CTA route, placement, destination, urgency, proof context, recovery owner, and thank-you expectation.
- Avoid insurance approval, coverage, payout, claim outcome, and timeline promises.
- Webzaz fits website recovery placement. Dispatch, scheduling, AI answering, CRM, estimate follow-up, LocalKit, QR/profile routes, emergency call routing tools, and no-show rescue workflows stay separate.

## Booked-job save-rate route

- Create second-touch accountability: callback owner, second-touch deadline, proof context, fallback channel, and escalation path.
- Measure booked-job save rate by missed callback recovered, estimate revived, reschedule saved, no-show prevented, and stale lead reactivated by source and city.
- If the stall came from vague website confirmation, hidden proof, or unclear quote routing, fix the page and thank-you path before adding more ad spend.
- Product-fit QA: Webzaz fits website recovery placement only when the original page, form, proof gallery, or thank-you route caused the stall. Dispatch, scheduling, AI answering, CRM, estimate follow-up, LocalKit/profile, emergency call routing, and no-show workflows stay separate.