How to Qualify a Storm Lead Before Sending an Inspector

Every storm restoration company has a number it does not like to look at: the cost of a truck roll that produces nothing. An inspector loads a ladder, drives twenty-five minutes, climbs onto a roof that turns out to be four years old with no functional damage, writes nothing, and drives back. The homeowner was friendly. The appointment was real. And the visit was a loss before it started.

Qualifying a storm lead is the discipline of finding out, before that truck moves, whether the address has a plausible claim, whether the homeowner is a decision-maker who will actually sit through an inspection, and whether the timing still fits inside the window where an insurer will entertain the conversation. Done well, it is the highest-leverage thing a storm sales operation does. Done badly — or skipped entirely because "we inspect everything" — it quietly eats your margin one wasted afternoon at a time.

What follows is the workflow practitioners actually use: the phone script, the desk research, the weather verification, the scoring system, and the edge cases that trip up crews who only learned to qualify by getting burned. None of it requires you to make promises about coverage, deductibles, or outcomes. All of it is about whether the visit is worth making.

Why qualification is a margin decision, not a courtesy

Start with the math, because the math is what makes a sales manager change behavior.

A fully loaded inspection — the inspector's time, vehicle, fuel, the appointment-setter's time, the no-show buffer, and the opportunity cost of not being on a better roof — is not free. Build your own number, but most crews who actually total it land somewhere in the range of a couple hundred dollars per completed inspection, and meaningfully more once you account for the inspections that no-show or fall apart on arrival.

Now apply a close-rate lens. Suppose your inspectors sit on roofs and convert qualified, damaged, in-window leads into signed contingency agreements at a healthy rate. The unqualified leads convert at a fraction of that — not because your inspectors are worse, but because the roof was never going to file, the person was never going to sign, or the claim was already past its useful window. Every unqualified inspection you run dilutes the average. The fix is not to inspect harder. It is to inspect fewer, better-chosen roofs.

Here is the framing that lands with owners: qualification does not reduce your sales. It reallocates your most expensive resource — a trained inspector's day — toward the roofs that can actually pay for it. An inspector who runs five qualified appointments will out-produce one who runs eight random ones, and will be less burned out doing it.

What "qualified" actually means

A storm lead is qualified when four things are simultaneously true. Miss any one and the inspection is a gamble:

1. Peril plausibility — a wind or hail event of meaningful intensity actually crossed that address, within a date range that matters.
2. Roof susceptibility — the roof is old enough, or of a material vulnerable enough, that the event could have produced functional damage worth documenting.
3. Decision authority and intent — the person you are talking to owns the home (or is the spouse who co-decides), can be present, and is open to a real inspection rather than "just a quote."
4. Claim window viability — enough time remains under the policy's notice requirements and the practical patience of the carrier that filing is still realistic.

The rest of this is how to check each of those four cheaply, fast, and over the phone or at a desk — before anyone climbs anything.

The five lead sources and how dirty each one is

You cannot design a qualification process without knowing the failure mode of where the lead came from. Each source lies to you in a different, predictable way.

The practical takeaway: a canvassed "yes" and a referral are not the same lead and should not get the same qualification weight. The canvassed yes needs its intent stress-tested. The shared digital lead needs its recency and address scrubbed before anyone dials. Treat them identically and you will burn inspectors on the worst of each.

A note on shared and aged leads

If you buy leads, know what you bought. Shared leads are sold to multiple contractors, and the homeowner often does not know that — they think they raised their hand for one company. Aged leads (resold after the original buyer cooled on them) are cheaper for a reason. Neither is disqualifying on its own, but both shift your qualification effort toward speed and exclusivity: the first credible contractor to get a real appointment booked usually wins, and the third one to call is wasting fuel. The U.S. Federal Trade Commission's guidance on telemarketing and the rules around calling consumers (including the Do Not Call registry) matter here too — your appointment-setters need to be operating inside those rules regardless of how warm the lead feels.

Step 1: The pre-call desk check (do this before you dial)

The single biggest mistake in storm sales is dialing a lead before looking at the address. Two minutes at a desk changes the entire phone conversation, because you walk in already knowing whether the story can be true.

Before the phone rings, pull up the address and answer four questions:

Did weather actually hit here? Open the storm history for that location and date range. You are looking for a hail report or a damaging-wind report near the address, not in the next county. The National Weather Service Storm Prediction Center maintains a public storm reports archive, and NOAA's Storm Events Database lets you search confirmed events by location and date. If you canvass after storms, you should already have a map of which streets the cell crossed — the desk check is just confirming this specific roof sits inside it.

How old does the roof look? Aerial and street-level imagery will tell you a lot before anyone climbs. A roof with crisp, uniform granules and sharp ridgelines reads newer; one with patchy color, visible repairs, moss, or cupping reads older. You are not grading it — you are deciding whether "this roof could plausibly have functional storm damage" is even on the table.

What is the roof made of and how steep is it? Material drives both vulnerability and your cost to inspect. Asphalt shingle behaves differently from metal, tile, or wood shake under hail. Steep and complex roofs cost you more inspector time and carry more safety exposure (OSHA's fall-protection requirements are not optional, and a 12/12 with no anchor points is a real planning factor). Knowing this before the visit lets you staff and price the appointment correctly.

Has this address been worked recently? Permit records, your own CRM, and visible signs of a new roof in imagery all matter. A roof replaced eighteen months ago is almost never a storm claim today, no matter how convincing the homeowner sounds.

The desk-check scorecard

Write the answers down in a fixed format so anyone on your team can read them at a glance:

ADDRESS: 144 Birchwood Ln
EVENT: Hail reported 1.25" ~0.8 mi from address, 14 days ago (SPC report)
ROOF AGE (visual estimate): older — patchy granule loss, likely 15-20+ yrs
MATERIAL / PITCH: 3-tab asphalt, moderate pitch (~6/12)
PRIOR WORK: no permit found, no new-roof signature in imagery
DESK VERDICT: PROCEED TO CALL — peril + age both plausible

The verdict line is the point. By the time you dial, you should already be able to say PROCEED, HOLD, or DROP. A HOLD means something is missing — maybe the event date is fuzzy, maybe the roof looks brand new — and you call to resolve that one thing rather than to set an appointment.

Step 2: The qualifying phone call

The call has one job: turn a name and an address into a confident PROCEED or a clean DROP, and book a real appointment only if it earns one. It is not a pitch. The biggest error appointment-setters make is selling the inspection so hard that they book unqualified roofs just to hit a booking quota.

Structure the call in five moves.

Move 1: Confirm the peril and the timeline

You already know from the desk check whether weather hit. Now you confirm the homeowner experienced it and pin the date.

• "When the storm came through, do you remember roughly what day that was?"
• "Did you have hail on the ground, or was it more of a wind event — branches down, fence sections, that kind of thing?"
• "Have you noticed anything since — granules in the gutters or by the downspouts, a stain on a ceiling, a piece of flashing or shingle in the yard?"

What you are listening for: a date that matches a real event, and at least one concrete observation. "My neighbor got a new roof" is a useful tell — adjusters and contractors both know storm damage clusters by street. "I just want to get it checked, it's been a while" is a different signal entirely; that is a wear-and-tear inspection wearing a storm costume.

Move 2: Establish roof age as a range

You do not need an exact install date, and you usually cannot get one. You need a range good enough to judge susceptibility.

• "Do you know roughly how old the roof is — did it come with the house, or did you replace it?"
• "Any idea if a previous owner did work on it?"
• "Has it ever been repaired or had a claim before?"

A homeowner who says "it's original, we've been here twelve years and it was here when we bought it" has just handed you a roof that is plausibly fifteen-plus years old. That is exactly the susceptibility profile where a real hail event produces a documentable, file-worthy condition. A roof the homeowner replaced four years ago is a much harder conversation, and you should be honest with yourself about that before you drive.

Move 3: Confirm decision authority and presence

This is where soft leads die, and you want them to die on the phone, not on the roof.

• "When we come out, the inspection takes about 45 minutes and I'll want to walk you through what we find at the end — is there a time that works when you and anyone else who'd be part of the decision can both be there?"
• "Are you the homeowner, or is this a rental?"

Two things happen here. First, you flush out the "my husband handles that" situation before you arrive to a spouse who will not engage. Second, asking for both decision-makers to be present is itself a qualification filter — a homeowner who will not commit to being there for 45 minutes is telling you their intent is soft. Rentals and absentee owners are not automatic disqualifiers, but they change who needs to be on the call and reset your expectations about same-day decisions.

Move 4: Set honest expectations (and disqualify the wrong fit)

Say plainly what the inspection is and is not. This protects you legally and filters out homeowners shopping for something you do not sell.

• "What we do is a thorough inspection. We document the actual condition of the roof and put together what we see. If there's storm-related damage, we'll show you exactly what it is and explain your options. We don't decide what's covered — that's between you and your insurer — but we make sure you've got clear documentation to work from."

Notice what is absent: no promise of a "free roof," no claim that insurance will pay, no guarantee about a deductible. Those promises are how contractors get into trouble with state insurance regulators and consumer-protection law, and they attract exactly the homeowners who will waste your time chasing a free roof that the inspection cannot deliver. The honest framing — you document, the insurer decides, the homeowner owns the claim — is both safer and a better filter.

Move 5: Book, hold, or drop

Close the call with a decision:

• Book if peril, age, authority, and intent all came back clean. Lock a specific time with decision-makers present.
• Hold if one factor is genuinely uncertain and a callback or a piece of info would resolve it. Put it on a tickler, not on a truck.
• Drop, politely, if the roof is too new, the "storm" is clearly wear, or the person plainly wants a free roof and nothing else. A clean drop is a win — you just saved an inspection.

Step 3: Verifying the weather event yourself

Homeowner memory is not evidence, and you should never set your route based on it alone. The good news is that storm verification is mostly free and public.

Hail

For hail, two questions matter: did hail of meaningful size fall here, and when. The SPC storm reports archive and NOAA's Storm Events Database give you confirmed and reported events by date and location. Radar-derived hail estimates (the products many contractors buy as "hail maps") add resolution but are estimates — the energy aloft that radar sees is not the same as ice on a specific roof, and the difference is exactly why you still have to inspect. Hail size correlates with the likelihood of functional damage to asphalt shingles, but the relationship is not a switch; small hail on an old, brittle roof can still bruise it, and large hail glancing a steep slope can leave one side untouched.

A practical threshold many crews use: meaningful hail reports (commonly around one inch and up) within roughly a mile of the address, in a date range that still fits the claim window, justify a visit on the peril axis. Smaller or farther reports do not disqualify, but they raise the bar on the other three factors.

Wind

For wind, the National Weather Service issues warnings and confirms severe events, and the Storm Events Database records damaging wind and tornado tracks. Wind damage on roofs is about uplift and the condition of the shingle seal: older shingles whose self-seal strip has weakened lift and crease at lower speeds than a properly sealed new roof. That is why the same gust that does nothing to a three-year-old roof tears tabs off a sixteen-year-old one on the same street. The Insurance Institute for Business and Home Safety (IBHS) publishes well-regarded research on how roofs fail under wind and hail, and it is worth a sales manager's time to understand the basic failure modes well enough to ask better qualifying questions.

The verification mini-table

Keep a simple internal standard for what "verified" means, so two appointment-setters score the same lead the same way:

Step 4: Where per-roof data changes the qualification

Everything so far is something a disciplined team can do with public weather archives, imagery, and a phone. The limit of that approach is throughput and precision. After a regional storm you might have hundreds of addresses across dozens of streets, and the desk check — while cheap per lead — does not scale to triaging a whole territory in an afternoon. It also leans on a visual age guess and a "near enough" read of where the cell tracked.

This is the gap RoofPredict is built to close. Instead of you eyeballing imagery for each roof, it estimates a roof-age range per address from aerial imagery and models storm exposure per individual roof rather than per ZIP code or per generalized hail polygon. The output is a ranked list: which roofs on which streets are most likely to have been worn out by the specific events that crossed them, and which roofs are simply aging into the susceptible zone on their own.

What that does to qualification is concrete:

• It pre-scores the peril and susceptibility axes at territory scale. The two desk-check questions that take the most judgment — how old is this roof, and did the storm really cross it hard enough to matter — get a data-backed estimate before a human touches the lead. Your appointment-setters then spend their phone time on the two human axes: decision authority and intent.
• It ranks routes so inspectors run dense, high-probability days. Rather than eight scattered appointments, you build a route down the streets where the model says the roofs are most likely due, cutting windshield time and raising the hit rate.
• It separates storm-worn from age-worn. A roof that is simply old is a legitimate replacement conversation, but it is not a storm claim. Seeing both signals side by side keeps your team from forcing a storm narrative onto a wear-and-tear roof — which is precisely the move that gets contractors crosswise with adjusters and regulators.

Be clear about the limits, because honest limits are what make a tool usable in qualification rather than a liability. Roof age comes back as a range, not an install date — imagery cannot read a permit. The storm model gives odds, not proof: it tells you a roof was likely exposed and likely worn, not that a covered loss occurred. Nothing it produces decides coverage; the inspector still has to climb the roof and document the actual condition, and the insurer still decides the claim. Used correctly, per-roof data does not replace the inspection — it decides which inspections are worth running, which is exactly the qualification problem. It sharpens steps 1 and 3; it does not touch the homeowner conversation in step 2 or the claim-window judgment in step 5.

Think of it as a better desk check that runs across your whole territory at once, ranks the roofs, and frees your inspectors to spend their days on roofs the data already says are due.

Step 5: The claim-window and policy reality check

A roof can have real, documentable storm damage and still be a bad lead — because the window to do anything useful about it has closed. This is the qualification factor crews skip most often, and it produces the most frustrating dead ends: a perfect inspection on a claim no carrier will seriously entertain.

You are not the homeowner's insurance advisor and you should never pretend to be. But you do need to ask enough to know whether filing is realistic:

• "Have you already filed anything with your insurance for this, or talked to an adjuster?"
• "Roughly how long ago was the storm — are we talking weeks, or has it been longer?"
• "Do you know if you've had any other claims on the home recently?"

Three realities sit behind those questions:

Notice requirements. Property policies generally require "prompt" notice of a loss, and many carriers apply practical time limits on how long after a storm they will entertain a new claim. The exact terms live in the policy, not in your head, so you frame it as a timing question, not legal advice. A storm that is well outside any reasonable notice window is a roof you may still replace as a retail job — but it is not a storm claim, and pretending otherwise wastes everyone's time.

Prior claims and history. A homeowner who has filed multiple recent claims is in a more complicated position, and that complexity belongs to them and their carrier, not to your inspector standing on the roof. You are simply noting that the path may be harder.

Already-filed or already-inspected. If a carrier's adjuster has already been out and the claim is in motion, the conversation changes — you may be doing a supplement-style documentation visit, not an originating inspection. That is a legitimate visit, but qualify it as what it is so the inspector arrives prepared, not surprised.

The point is not to play insurance expert. The point is to avoid sending an inspector to document a beautiful, dead-on-arrival claim because nobody asked one timing question on the phone.

Reading hail size and material against susceptibility

Qualification gets sharper when your team understands, at a working level, why some roofs take damage and identical-looking roofs next door do not. You do not need to be a meteorologist or a materials engineer, but the appointment-setter who grasps the basics asks better questions and scores leads more accurately.

Hail damage to asphalt shingles is a function of stone size, density, fall speed, impact angle, and — critically — the age and condition of the shingle being hit. A larger stone carries more energy and is more likely to fracture the mat and dislodge the granule layer that protects the asphalt from UV. But size is not the whole story. A fresh, pliable shingle can absorb an impact that would bruise or crack a brittle, sun-baked one of the same product fifteen years later. That interaction is exactly why peril and susceptibility are two separate axes in your score rather than one: a modest event on an old roof and a violent event on a new roof can both produce a borderline lead, for opposite reasons.

Impact angle matters more than crews expect. Hail rarely falls straight down in a strong storm; wind drives it at a slant, which means one slope of a roof can be peppered while the opposite slope is nearly untouched. When a homeowner says "it doesn't look bad from the ground," remember they are usually looking at the wrong slope. This is also why a single ground-level glance is never a substitute for an inspection — and why a roof that the data flags as exposed still has to be climbed and documented.

A rough susceptibility reference

Use a reference like this to calibrate the susceptibility axis on your score, adjusting for your local climate and the products common in your market:

The value of this table in qualification is not precision — it is consistency. Two setters looking at the same roof age and the same hail report should land on the same susceptibility read, and a shared reference makes that happen.

Wind speed and the seal-strip story

Wind qualification has its own logic. A shingle resists uplift mainly through its self-seal adhesive strip, which bonds each course to the one below. That bond degrades with age, heat cycling, and prior wind events. So the question "how old is the roof" is, for wind, really the question "how good is the seal." A confirmed severe wind event over an older roof is a stronger lead than the same wind over a new one, because the failure threshold is lower. When a homeowner reports lifted or creased tabs, missing shingles along a rake or ridge, or debris in the yard, those are the visible signatures of seal failure — and they are worth capturing on the qualifying call as corroboration.

Capturing the qualification so it does not evaporate

A qualification process is only as good as what survives the phone call. If your setters do brilliant desk checks and ask perfect questions but write three words in a CRM note, the inspector arrives blind and the data is useless for tuning your score later. Treat the captured record as a deliverable.

At minimum, every qualified lead should carry a structured record the inspector reads before leaving the shop:

LEAD: 144 Birchwood Ln — SCORE 18 (BOOK)
PERIL: 1.5" hail, SPC report 0.5 mi, event 3 wks ago
ROOF: ~18 yr est, 3-tab asphalt, ~6/12, granule loss visible
ACCESS/SAFETY: single-story, clear east-side ladder set
HOMEOWNER: owner 14 yrs, spouse attending Sat 10am
WINDOW: nothing filed yet; within window
NOTES: neighbor two doors down already replaced
INSPECTOR PREP: bring documentation kit; both slopes; check NE slope first (wind-driven)

Three benefits follow from capturing this well. The inspector arrives prepared instead of surprised, which raises both conversion and safety. The homeowner experiences a company that already knows their situation, which builds trust before the ladder goes up. And — the quiet long-term payoff — you accumulate a dataset of scores versus outcomes that lets you tune your weights from evidence instead of opinion. After a season, you can look back and see which score bands actually converted, and move your thresholds accordingly.

Closing the loop with inspector feedback

The missing half of most qualification systems is the return signal. The inspector who just drove to a roof knows something your setter could not: was this lead worth running? A one-line disposition — worth it, marginal, or should-not-have-rolled, plus a reason — closes the loop. Feed that back into your scoring and your setter coaching. Over a season, this single habit does more to improve qualification accuracy than any script, because it grounds the whole system in what actually happened on the roof rather than what looked good on the phone.

Putting it together: a weighted lead score

Checklists are good; a single number that everyone trusts is better, because it removes the "my gut says go" arguments and makes the qualification consistent across appointment-setters. Build a simple weighted score against the four axes.

Maximum score is 20. Pick your own thresholds and tune them to your close data, but a common starting cut:

• 15-20: Book now. All four axes are strong. This is the inspection that pays for itself.
• 9-14: Conditional. One axis is weak. Resolve it (a callback, a weather pull, a per-roof data check) before booking, or book into a low-cost route slot.
• 0-8: Drop or nurture. Two or more axes failed. Do not roll a truck. If the roof is simply old with no storm, hand it to your retail pipeline instead of your storm pipeline.

Worked example A: the clean book

Canvassed lead, three weeks after a hail event. Desk check finds a 1.5-inch hail report half a mile away, dated to the event. Imagery shows a roof with heavy granule loss, plausibly eighteen years old. On the call, the homeowner confirms hail on the ground, says the roof is original to a house they have owned for fourteen years, agrees to a Saturday slot with their spouse present, and has not filed anything yet.

Score: peril 2x3=6, susceptibility 2x3=6, authority/intent 2x2=4, window 2x2=4. Total 20. Book it. This is the roof your best inspector should be on.

Worked example B: the deceptive inbound

Inbound call, homeowner "heard the neighborhood got hail and wants it checked." Desk check finds no hail report within several miles and no severe wind on the claimed date; imagery shows a roof replaced roughly three years ago (sharp granules, a permit on file). On the call, the homeowner admits the roof is fairly new and they are "just being cautious."

Score: peril 0x3=0, susceptibility 0x3=0, authority/intent maybe 1x2=2, window 2x2=4. Total 6. Drop from storm pipeline. There is no peril and no susceptibility — the two axes that make a storm claim possible. Sending an inspector here is a near-guaranteed zero. The polite move is to thank them and note you will reach out if a real event hits their area.

Worked example C: the borderline that needs one phone call

Shared digital lead, eight days old. Desk check finds a confirmed severe wind event over the area and a roof that looks mid-age. But the lead is shared, so others may already be working it, and you cannot tell from imagery whether the roof is twelve years old or six. The homeowner does not answer on the first try.

Score as-is: peril 2x3=6, susceptibility 1x3=3, authority/intent unknown, window 2x2=4 — roughly 13 with intent unconfirmed. Conditional. This is where a per-roof age range earns its keep: if the data says the roof is likely in the susceptible range, the score firms up and you prioritize a fast callback before competitors lock the appointment. If it comes back likely newer, you let it go. Either way, you did not roll a truck on a coin flip.

The pre-inspection checklist your team can actually run

Print this. Tape it next to the phone. The discipline is in running it the same way every time.

Desk (before dialing):

• Pulled storm history for the address and date range (SPC / NOAA Storm Events)
• Estimated roof age range from imagery (or per-roof data)
• Noted material and pitch (inspection cost, safety, susceptibility)
• Checked permits / CRM for recent work
• Wrote a desk verdict: PROCEED / HOLD / DROP

Phone (the qualifying call):

• Confirmed the homeowner experienced the event and pinned a date
• Captured at least one concrete damage observation
• Established roof age as a range
• Confirmed owner status and that decision-makers will attend
• Set honest expectations (we document; insurer decides; homeowner owns the claim)
• Asked the claim-window timing question
• Scored the lead and made a book / hold / drop call

Booking (only if it scored in):

• Specific time, decision-makers present, 45-minute window communicated
• Inspector briefed on roof age, material, pitch, and safety needs
• Confirmation sent, with a reminder set to cut no-shows

Common mistakes that quietly wreck a storm operation

After enough seasons, the same failures repeat. Naming them is half the fix.

"We inspect everything." This sounds customer-friendly and is actually the most expensive policy a storm company can hold. It treats a brand-new roof in a no-hail ZIP the same as an eighteen-year-old roof under a confirmed 1.5-inch core. Your inspectors are your scarcest, most expensive resource. Spending them indiscriminately is how good crews go broke in a busy season.

Booking to a quota instead of to a score. When appointment-setters are paid or measured purely on appointments booked, they will book unqualified leads to hit the number, and your inspectors absorb the cost downstream. Measure setters on qualified booked appointments — ideally on appointments that the inspector confirms were worth running.

Trusting the homeowner's weather memory. "We definitely got hail" is a starting point, not a verification. People conflate storms, misremember dates, and repeat what a neighbor told them. Pull the record every time. It is free.

Forcing a storm story onto a wear-and-tear roof. An old, worn roof with no storm event is a legitimate retail replacement — and a terrible storm claim. Pushing it as storm damage is the behavior that erodes adjuster trust in your company specifically and draws regulatory attention generally. Qualify the difference and route the lead to the right pipeline.

Ignoring the claim window. A flawless inspection on a claim no carrier will entertain is wasted work. One timing question on the phone prevents it.

Skipping the safety and access read. A steep, cut-up roof or a property with no safe ladder set is a different job than a walkable 6/12, and OSHA fall-protection requirements apply regardless of how routine the inspection feels. Qualifying access and complexity up front lets you staff and schedule correctly instead of sending an inspector who has to abort on arrival.

Letting fast leads decay. With shared and aged leads especially, speed is qualification — the credible contractor who books first usually wins, and the desk-check discipline has to run fast enough to keep up. Build the workflow so a strong lead can go from inbox to booked in minutes, not days.

Edge cases worth a plan

The spouse who "handles the roof." Reschedule rather than inspect into a guaranteed non-decision. Asking for both decision-makers up front prevents most of these.

The rental or absentee owner. The tenant cannot authorize anything and the owner is elsewhere. Qualify who actually decides and book around them; do not inspect into a dead end.

The "just give me a quote" caller. A homeowner who wants a price without an inspection is usually shopping a retail repair, not pursuing a storm claim. That is fine — just route them correctly and do not burn a storm inspector on it.

The neighbor-effect cluster. When several homes on one street report damage, the peril axis firms up for the whole block. This is where route-level, per-roof data turns a single qualified lead into a qualified street, and your inspector runs a dense, high-yield day.

The aggressive free-roof shopper. Someone fixated on a free roof and a covered deductible is both a legal hazard and a poor fit, because you cannot promise either. Reset expectations honestly; if they will not engage on documentation, let them go.

Handling the objections that come up while qualifying

Qualification is a conversation, and conversations have friction. The setters who qualify well are not the ones who steamroll objections — they are the ones who use each objection as a data point about whether the lead is real. A few of the most common, and how to handle them without overpromising:

"I'm just getting a few quotes." This is a retail-shopping signal, not a storm-claim signal. Acknowledge it and probe gently: "Happy to take a look — is this about something specific you noticed, or general pricing?" If it is general pricing on a sound roof, route it to retail and move on. You learn the intent axis in one exchange.

"Just tell me over the phone if I have damage." You cannot, and you should say so plainly: the only way to know is a real inspection, because the visible signatures live on the roof, often on the slope they cannot see from the ground. A homeowner who will not allow an inspection is not a qualified storm lead; they want a verdict you cannot honestly give over the phone.

"My neighbor's company said they'd get me a free roof." This is the moment to be the honest company. Explain that no one can promise a covered claim or a free roof — that depends on the policy and the insurer's decision — but that a thorough inspection and clear documentation give the homeowner the best footing. Some will walk toward the company making bigger promises. Let them. Those promises are how contractors end up in front of state regulators, and the homeowner chasing them is rarely your best account.

"How much is this going to cost me?" The inspection itself and your honest answer about what you do and do not promise are the qualification. Be clear about scope without making coverage claims, and watch whether the homeowner is engaging with the documentation process or only fishing for a free roof.

"Can you come right now?" Urgency can be a strong buying signal or a sign of a homeowner already mid-claim with another contractor. Qualify which: ask whether anyone has already been out or filed. Same-day can be the correct call for a high-scoring lead, but only once it scores.

Reducing the no-show, which is a qualification failure in disguise

A booked appointment that no-shows is, in effect, an unqualified lead that slipped through — the intent axis was weaker than your score said. Several habits tighten it:

• Book decision-makers, not merely a name. The single biggest no-show driver is booking one spouse who never really committed. Securing both up front is qualification and no-show prevention at once.
• Confirm with a reminder. A short confirmation the day before, with the time window and what to expect, catches the soft bookings before they cost you a truck roll.
• Set a real window and respect it. Homeowners who feel a company is precise about time are more likely to show; vague "sometime Tuesday" bookings decay.
• Re-score on confirmation. If, on the reminder call, the homeowner is suddenly vague or cannot confirm attendance, that is new information. It is cheaper to downgrade the lead the day before than to discover it on arrival.

A no-show rate that will not come down is usually a sign your qualification is booking on weak intent. The fix is upstream, in the call, not in the reminder.

A 30-day plan to install this in your shop

You do not need new software to start qualifying well — you need a repeatable habit and a number everyone trusts.

Week 1 — Build the standard. Write your desk-check format and your weighted score. Agree, as a team, on what "verified" means for hail, wind, date, and corroboration. Pick your booking thresholds.

Week 2 — Script and train. Turn the five phone moves into a real script your setters run. Role-play the deceptive inbound and the soft canvassed yes until dropping a bad lead feels normal instead of uncomfortable.

Week 3 — Measure the right thing. Start tracking qualified booked appointments and inspector-confirmed "was this worth running" feedback. Watch your inspection-to-contract rate, not your raw booking count.

Week 4 — Tune and consider scale. Look at where your scores mispredicted — the books that flopped and the drops you regret — and adjust weights. If your territory volume is outrunning manual desk checks, that is the moment per-roof age and storm data earns its place: it pre-scores peril and susceptibility across the whole map so your humans can focus on intent, authority, and timing.

The bottom line

Qualifying a storm lead before sending an inspector is four questions asked in a disciplined order: did a real storm hit this roof, is this roof susceptible enough to have been hurt by it, will a real decision-maker actually sit through the inspection, and is there still a window to do anything useful. Answer those with a desk check, a structured call, free public weather data, and an honest score — and you stop spending your most expensive resource on roofs that were never going to pay for the visit.

The contractors who win the storm season are not the ones who inspect the most roofs. They are the ones who inspect the right ones, having decided which roofs were worth a truck roll before the truck ever moved. Per-roof age and storm data — like the ranked, address-level view from RoofPredict — makes that decision faster and across a whole territory, while keeping you honest about what it can and cannot tell you: a range, not a date; odds, not proof; a reason to inspect, never a substitute for the inspection.

FAQ

What does it actually mean to qualify a storm lead?

It means confirming four things before you dispatch an inspector: a real wind or hail event hit the address in a date range that matters, the roof is old enough or vulnerable enough to have been damaged, the person is an owner and decision-maker who will attend the inspection, and there is still a realistic window to file. If any one of those fails, the inspection is a gamble. Qualification is checking all four cheaply over the phone and at a desk.

How do I verify a hail or wind event without buying a hail map?

Use free public sources. The NOAA Storm Prediction Center keeps a storm reports archive, and NOAA's Storm Events Database lets you search confirmed hail, wind, and tornado events by location and date. The National Weather Service confirms severe events. Paid radar-derived hail maps add resolution but are estimates of energy aloft, not proof of damage on a specific roof, which is why you still inspect.

How old does a roof need to be to be worth a storm inspection?

There is no hard cutoff, but susceptibility rises with age because aged shingles lose granules and their wind seal weakens, so the same event that does nothing to a three-year-old roof can damage a sixteen-year-old one on the same street. A roof under about five years old with no event is usually a poor storm lead. You only need an age range, not an exact install date, to make the call.

Can I tell a homeowner their insurance will pay or that the roof will be free?

No. Promising a covered claim, a paid deductible, or a free roof can run afoul of state insurance regulators and consumer-protection law, and it attracts homeowners chasing outcomes you cannot deliver. The honest and safer framing is that you document the actual roof condition, the insurer decides coverage, and the homeowner owns the claim. That framing also filters out poor-fit leads.

What is the single fastest way to disqualify a bad lead?

A two-minute desk check before you dial. Pull the storm history for the address and date, and look at recent aerial or street imagery for roof age and prior work. If there was no meaningful event and the roof looks new or was recently permitted, you can drop it before spending a phone call, let alone a truck roll.

How does the claim window affect whether a lead is worth inspecting?

Property policies generally require prompt notice of a loss, and carriers apply practical limits on how long after a storm they will entertain a new claim. A roof with real damage but a closed window is a dead-on-arrival claim. Ask a simple timing question on the phone, are we talking weeks or much longer, and whether anything has already been filed. If the window has closed, it may still be a retail replacement but it is not a storm claim.

Should I qualify shared and aged leads differently?

Yes. Shared leads go to several contractors at once and aged leads are resold after cooling off, so your effort shifts toward speed, recency, and exclusivity. The first credible contractor to book a real appointment usually wins, so your desk check has to run fast. Also make sure your callers operate within telemarketing and Do Not Call rules regardless of how warm a lead feels.

How does per-roof storm and age data fit into qualification?

It pre-scores the two hardest desk-check questions at territory scale: how old each roof likely is, given as a range from aerial imagery, and how hard the specific storm exposed each individual roof, given as odds. That lets you rank routes and focus inspectors on roofs the data says are due, while your callers handle intent, authority, and timing. It does not decide coverage and never replaces the inspection. Roof age is a range, not a date, and the storm model is odds, not proof.

How should I measure my appointment-setters?

Measure qualified booked appointments, not raw bookings. When setters are judged purely on appointment volume, they book weak leads to hit the number and inspectors absorb the cost. Tie the metric to a lead score and to inspector feedback on whether the visit was worth running, so the incentive points at quality rather than quantity.

What roof and site details should I qualify before the inspector arrives?

Confirm the roofing material and pitch, and whether there is safe ladder access. Material drives both hail vulnerability and inspection time, steep or complex roofs cost more inspector time and carry more fall exposure, and OSHA fall-protection requirements apply on every job. Knowing this up front lets you staff, schedule, and price the visit correctly instead of having an inspector abort on arrival.