Modeled Playbook: Processing a 400-Lead Roofing Storm Week Without Losing Follow-Up

The short answer

The modeled storm-week system validates serviceability, classifies urgency and property context, acknowledges every eligible inquiry, routes against real inspection capacity, and keeps an overflow queue visible. It protects the customer promise by refusing to fabricate appointment availability.

Modeled scenario

A storm produces 400 inquiries in seven days across several ZIP codes while inspection capacity is limited. The goal is orderly response and prioritization, not pretending every lead can be served immediately.

Declared assumptions

Replace every input with verified business data before making a forecast or investment decision.

• 400 raw inquiries arrive across phone, web, and partner sources.
• Service area, lead source, property type, and contactability can be validated.
• Daily inspection capacity and overflow policy are supplied by operations.
• Duplicate and existing-customer rules are defined.
• Priority criteria do not discriminate unlawfully or misrepresent emergency status.

Playbook architecture

Create one eligible cohort, preserve source and consent, assign an owner, use event-based follow-up, stop on response or outcome, and surface exceptions. The roofing team—not the workflow—owns judgment and commitments.

Calculation method

Capacity gap = qualified demand − available inspection slots. Report response, qualification, scheduling, overflow aging, and loss by source rather than assigning revenue to automation without a matched baseline.

Customer journey

Acknowledge context, make one clear next step, vary follow-up by intent, stop irrelevant sequences immediately after response, and retain an easy human path. Escalate high-value, sensitive, or ambiguous situations.

Operating dashboard

Track eligibility, contactability, response, appointment or next-step conversion, completion, value, time to action, opt-outs, complaints, exceptions, and cohort age.

• Time to acknowledgement
• Qualified leads per service area
• Inspection capacity utilization
• Overflow queue age
• Inspection-to-estimate rate
• Contract rate by storm cohort

Guardrails

Publish truthful capacity and escalation rules; do not use disaster anxiety, false scarcity, insurer implication, or guaranteed claim language. Storm marketing, insurance discussions, canvassing, and financing may carry local rules. Preserve consent and source, review claims, and ensure operational capacity matches automated promises.

Pilot and scale

Test on a small, representative cohort. Compare against a baseline or holdout where practical, review conversations and exceptions, correct the system, then scale in measured waves.