How do you get roofing leads after a hail storm in Texas? (the 48-hour playbook)

You run the same seven steps every time, and you run them inside 48 hours. Confirm the swath, pull its addresses, filter out the homes that already re-roofed, load the call queue, canvass with a tracker, log every disposition, and follow up. RoofCRM is built to run that exact sequence — each step below says what the CRM does for it.

Step 1: Confirm the swath

Before anything else, verify where hail actually fell. The Storm Map in RoofCRM draws hail swaths as polygons with date controls, so you can pull up the storm in question and see which counties and streets the track crossed. What RoofCRM does: gives you the radar-derived swath — MRMS MESH estimates anchored by NOAA Storm Events and SPC reports — instead of a screenshot from a group chat.

Step 2: Pull the addresses

Select the swath and import the affected addresses as leads in bulk. What RoofCRM does: each lead card arrives with the hail event attached and a grade badge showing how deep in the swath the property sits, so the list is prioritized the moment it exists.

Step 3: Filter out re-roof permits

A home that already pulled a re-roof permit is not your lead. RoofCRM cross-references the imported properties against permit records through PermitLookup, and the properties with no re-roof permit on file become the working list. What RoofCRM does: turns "everyone under the storm" into "the homes still actually available."

Step 4: Load the call queue

Filtered leads go straight into the call queue. What RoofCRM does: enforces Do-Not-Call at the data layer — DNC numbers are withheld and the call path for those leads is blocked — applies quiet hours, and puts the guided script card in front of the rep on every call. Email remains available for DNC numbers where the phone is not an option.

Step 5: Run door-to-door

Storm response is still a knock business. What RoofCRM does: the canvassing tracker records every stop from the truck — the app is an installable PWA, and the native iOS field app with Face ID lock is in TestFlight — so routes and statuses stay current in the field instead of being reconstructed from memory at the end of the day.

Step 6: Log dispositions

Every contact ends in a status: not home, not interested, inspection set, signed. What RoofCRM does: dispositions are one tap on the lead card and land in the audit log, which is what makes tomorrow's re-route a filter instead of a memory exercise.

Step 7: Follow up

The signed jobs are usually on the second or third touch. What RoofCRM does: follow-ups stay attached to the lead with next-step prompts from the script card, inspections land on the schedule board, and an accepted estimate moves into insurance claim tracking, invoices, jobs, and crews without leaving the CRM.

Why the 48 hours matter

Texas homeowners get canvassed heavily after visible hail. The first companies through a neighborhood set the comparison everyone else is judged against, and doors stop opening once the pitch is familiar. The contractors with a filtered list on day one are the ones still getting doors opened on day two — which is why the whole pipeline, from swath to queue, lives in one place.

Honest limits

• The playbook only works while the data is fresh — a swath from three weeks ago is history, not leads.
• Permit data lags the field slightly; a filtered lead can still turn out to be taken.
• Radar hail sizes are estimates; an inspection confirms real damage.

Metro versions of this playbook: San Antonio, DFW, Austin, and Houston. Buyer's criteria: what to look for in storm leads. Background: swath data with addresses, storm data in the CRM, and the CRM question, with the full feature list.