Blog / roofing lead follow-up automation

Storm Season Lead Follow-Up for Roofing Contractors

Joe · ·5 min read

A hail line moves through the west metro on a Tuesday afternoon. By Wednesday morning your phone is ringing, and it keeps ringing for two solid weeks. Then it stops, and you sit down and look at what you actually closed, and the number is smaller than the number of people who called you.

That gap is not a sales problem. Every one of those callers wanted a roof. They wanted it from somebody, and a lot of them stopped waiting.

I'm Joe, based in Minnetonka. I work with owner-operated businesses on the follow-up that stops happening when everybody gets busy, and roofing has one of the sharpest versions of this problem I've come across. Most trades deal with a steady trickle of leads. Roofing deals with a wall of them, all at once, at exactly the moment when nobody has a free hand.

The two weeks after a storm are a bad time to be short-staffed

Here's the setup that makes storm season different. Your demand arrives in a spike. Your capacity does not. The people who could return calls are the same people who need to be on roofs, and the people on roofs cannot answer a phone at two in the afternoon in July.

So the calls go to voicemail. The web form sends an email that lands in a crowded inbox. Somebody writes a name and number on the back of an estimate sheet in the truck. Three days later, when there's a breath, half of those leads have already signed with whoever picked up first, including the out-of-state crews who showed up the same week and are working the neighborhood door to door.

I wrote about this pattern more generally in why trades lose jobs to whoever answers the phone first. Roofing is that post with the volume turned all the way up.

The insurance timeline is the part most follow-up systems ignore

The thing that makes roofing leads different from a leaking water heater is that a storm lead is usually not ready to buy when they call. They're ready to start. The adjuster has to come out. The claim has to get approved. That can take a few weeks, sometimes longer after a big event when every adjuster in the state is booked.

So the homeowner calls you, you do the inspection, you send documentation, and then there's a long quiet stretch where nothing happens and nobody talks. That silence is where the lead gets lost, and it's not because the homeowner picked someone better. It's because two weeks went by, they got a knock on the door from a competitor who was standing right there, and you were not in their head anymore.

That waiting period is the single most automatable thing in a roofing business, and almost nobody has anything running in it. A short note at the right moment does the work: a check-in asking whether the adjuster has been out yet, a plain-language explainer on what to expect from the appointment, a reminder that you'll meet the adjuster on site if they want you there. None of that requires a person to remember anything. It requires a sequence that starts when the inspection is logged and keeps going until the claim resolves one way or the other.

What to put in place before the next event

You don't need a system that does everything. From what I've seen across the trades, four pieces cover most of the lost revenue.

Instant acknowledgment with a real next step. Not "thanks, we got your message." A text within a minute or two that says you received the request, gives a realistic window for the inspection, and tells them what happens first. Speed matters more than polish here, and it matters most in the first hour.

After-hours coverage that captures rather than deflects. Storm calls come in at seven at night, because that's when people get home and look at their ceiling. A voicemail box is a decision to let those go. I've written about what missed calls actually cost, and in a two-week spike the math gets ugly fast.

A claim-period sequence. The three to six week nurture described above. This is the one I'd build first if you only build one.

A quote follow-up that runs on its own schedule. You sent the estimate. They said they'd talk to their spouse. That thread deserves three or four touches over the next month, not one. The quote-to-paid follow-up system post walks through the structure.

The leads from last May are still worth something

The other piece that goes unused is the list. Every storm generates a pile of homeowners who got inspected, got a number, and then did nothing. Their claim got denied, or the deductible scared them off, or they just decided to wait.

That roof is still old. It is still going to need replacing, and next spring it is going to hail again. A contractor who sends those people something useful twice a year, an actual note about what the last storm did to the neighborhood or a reminder to check for granule loss, is the contractor they call when they finally move. That is not a marketing campaign. It's a list and a schedule, and it can run without anyone thinking about it.

What I would not automate

The inspection conversation. The claim negotiation. Anything where a homeowner is upset about their house. Automation is good at making sure the right message goes out at the right time when nobody is available to send it. It is not good at reassuring somebody whose kitchen ceiling is stained, and pretending otherwise is how these systems get a bad reputation.

The goal is narrower than it sounds. Keep the leads warm, keep the timeline moving, and free up the hours you're currently spending on callbacks so you can spend them on the conversations that actually close work.

If you want to talk through what this would look like for your business, the audit is free and takes 30 minutes. Get in touch

Want to see where AI fits your business?

Book a free AI audit. We walk through your workflows together and I show you exactly what to automate and why.