How do I get roofing leads after a hail storm in San Antonio?

Work the swath, not the rumor. When a hail storm crosses Bexar County, pull that storm's hail swath, import the property addresses under it as leads, and cross-reference roofing permits so the homes with no re-roof permit on file become your working list. RoofCRM runs all three steps in one place, so your canvass can start the same morning the storm clears.

Step one: see the swath over San Antonio

The Storm Map in RoofCRM draws hail swaths as polygons on an interactive map with date controls, so you can pull up the night a storm came through and see exactly which neighborhoods it crossed — Stone Oak, Alamo Heights, the I-35 corridor up toward New Braunfels. The swath comes from radar-derived hail data rather than a spotter's anecdote, so you know which streets were actually under the storm track and which just heard about it secondhand. Where that data comes from is covered on the swath-data page.

Step two: import the addresses as leads

With the swath on screen, select it and import the affected addresses into RoofCRM as leads in bulk. No CSV wrangling, no copy-pasting between a hail map and a spreadsheet: the properties land on your lead list with the hail event already attached to each card, and a grade badge surfaces the leads that sat in the hardest-hit part of the swath.

Step three: the permit cross-reference

Imported addresses alone are not leads — some of those homeowners have already signed with another roofer. RoofCRM cross-references the properties in the swath against permit records through PermitLookup: a house inside the swath with no re-roof permit on file is a live opportunity, and a house that already pulled one is a knock you can skip. What is left after that filter is your actual San Antonio lead list, across Bexar, Comal, and Guadalupe counties.

Why the first 48 hours decide the job

After a visible hail storm, every roofer in the metro is door-knocking the same subdivisions. Homeowners take their first few knocks, compare the first two or three companies they meet, and stop answering the door after that. The contractors who have routes built and the call queue loaded inside two days work the neighborhood while their pitch is still new information; the ones who import a list the following week are working leftovers. Speed is the entire advantage, which is why the swath-to-leads pipeline lives inside the CRM instead of a separate tool.

Outreach that stays DNC-safe

Storm-response selling has real compliance constraints. In RoofCRM, Do-Not-Call is enforced at the data layer: numbers on the DNC list are withheld and the call path for those leads is blocked, so a rep physically cannot dial them from the call queue. Email is still allowed for DNC numbers, and quiet hours plus opt-out handling cover the rest of the guardrails, with a full audit log behind every action.

Honest limits

• Storm coverage is strongest in Texas, and San Antonio sits well inside that focus — but no dataset catches every hail cell, and radar-derived hail sizes are estimates until someone puts a ladder up.
• The permit cross-reference is only as current as the permit records it mirrors; a permit pulled yesterday can take time to appear.
• A filtered address is a lead, not a signed job. Somebody still has to knock, call, and inspect. RoofCRM organizes that work; it does not remove it.

The same drill is written up for DFW, Austin, and Houston, and the state-wide version is the 48-hour playbook. Feature details live on the features page and the storm-data page.