Roofing leads after a storm: triage the request and set honest expectations

Capture what the homeowner can safely observe

Ask where the damage appears to be, when it was noticed, whether water is entering the home, and how the customer can be contacted. A photo may help if the homeowner can take it from a safe place. Never ask someone to climb onto a roof or enter an unsafe area to gather more information.

Record the report as a report, not a verified finding. “Customer sees a ceiling stain after the storm” preserves what is known; “roof leak at the flashing” implies an inspection that has not happened.

Set priority rules before the next storm

Decide which requests need immediate human review, which can be scheduled for assessment, and which require a referral or a later appointment. Base that decision on your actual service coverage and staffing. A form response cannot create inspection capacity that is not available.

If a customer reports immediate danger, advise them to contact appropriate emergency services and follow your company’s escalation policy. Be careful with statements about insurance, coverage, or repair outcomes; those depend on facts your intake team may not have.

Make the queue workable

Group requests by location, reported urgency, and whether water intrusion is ongoing. Assign an owner to each request and record the next promised contact. If you expect delays during a surge, tell customers what you can commit to and update them when that changes.

After the event, compare inquiry volume, completed inspections, no-contact cases, and jobs accepted. That review can help you plan future coverage and communicate clearly. It should not be used to invent a response-time statistic or guarantee the same result next time.