Roofing Inbound Lead Qualification: The Form Questions That Actually Sort Real Jobs From Tire-Kickers

Every roofing company with a website has a contact form. Almost none of them have a form that does any work. The typical version asks for name, email, phone, and "how can we help you?" — then dumps whatever comes back into an inbox where a salesperson reads it cold three hours later, calls a number that goes to voicemail, and books an inspection on a roof that turns out to be four years old with a homeowner who just wanted a number for a refinance appraisal.

That is not a lead problem. That is an intake problem. The form is the first and cheapest place in your whole sales operation to separate a real job from a tire-kicker, and most contractors leave it blank.

What follows is the set of questions that actually sorts inbound roofing leads — what to ask, why each question earns its place, how to score the answers, and how to route the result so your best closer is on the phone with the best opportunity inside five minutes instead of next Tuesday. It is written for the owner or sales manager who is tired of paying a $90 fuel-and-labor cost to inspect roofs that were never going to buy.

Why your form is the highest-leverage qualifier you own

Think about where qualification can happen. A salesperson can qualify on the phone — but only after the lead picks up, which for inbound web leads is roughly half the time on the first try, and worse if you wait. A canvasser can qualify at the door, but you have already spent the gas. An inspector can qualify on the roof, but you have already spent the truck roll and an hour of skilled labor.

The form qualifies before any of that. It costs nothing per lead, it never has a bad day, and it asks every single person the same questions in the same order. That consistency is the whole game. When every lead arrives with the same six or eight data points filled in, you can score them, route them, and prioritize them automatically. Your team stops triaging and starts selling.

There is a real tension to manage, and pretending it does not exist is how contractors end up with bad forms. Every field you add costs you conversion. Industry intake data consistently shows that form completion drops as field count climbs — somewhere past four or five fields you start measurably leaking submissions, and past eight you are bleeding. So the discipline is not "ask everything." The discipline is: ask only the questions that change what you do next, and make the painful ones easy to answer.

The frame to hold in your head for the rest of this piece: a good qualification question is one whose answer changes your next action. If the answer never changes whether you call, who calls, how fast, or what they say — cut the question. It is friction with no payoff.

The four things you are actually trying to learn

Strip away the specifics and every qualifying question is trying to establish one of four things. Map your form to these and you will never add a useless field again.

1. Is this a real, in-scope job? Roof type, property type, problem, address. A flat commercial TPO roof is a different business than a residential asphalt tear-off. A renter cannot authorize work. An address 90 minutes outside your service area is a no regardless of how hot the lead is.
2. Is it urgent or is it someday? Active leak versus "thinking about replacing it eventually." Urgency sets your speed-to-lead and your routing. A water-coming-in-now lead that sits for two hours is a lost job and possibly a one-star review.
3. Can this person actually authorize and pay? Owner versus renter, decision-maker present, rough sense of how they intend to fund it (out of pocket, financing, or an insurance pathway). You are not asking for a credit score. You are asking whether there is a path to yes.
4. How do I reach them and what do they expect? Best number, best time, contact preference, and consent to contact. The fastest, most qualified lead is worthless if you can never get them on the phone or you call at the one time they asked you not to.

Every question below earns its spot by feeding one of those four buckets. If you are evaluating your own form, put each existing field next to a bucket. The orphans — the ones that map to nothing — are the ones to kill.

The core questions, field by field

Here is the working set. Treat this as a menu, not a mandate — a residential storm-restoration shop and a commercial re-roof outfit will pick different items. After each one is the reason it earns its place and, where it matters, exactly how to word it so a homeowner can answer in two seconds.

1. Property address (or at least ZIP)

This is the single most valuable field on the form and the one contractors most often bury or skip. Address tells you, before a human touches the lead, whether the property is in your service area, what the structure looks like from above, how old the roof likely is, and what weather it has lived through. A bare ZIP gets you service-area filtering instantly; a full address opens up everything else.

Word it as a benefit, not an interrogation: "Property address (so we can pull up your roof before we call)". That parenthetical does real work — it tells the homeowner you are going to show up informed, and it dramatically raises the odds they fill it in honestly.

If you are worried about address scaring people off, split the difference: make ZIP required and full street address optional but encouraged. You will get most of the value from ZIP alone for routing, and the address-fillers self-select as more serious.

2. Property type: residential / commercial / multi-family

One click that prevents the most expensive mismatch in roofing intake. A property-management company asking about a 40,000 sq ft warehouse should never land in the same queue as a homeowner with a missing shingle. Different crew, different estimating, different sales motion, sometimes a different company entirely.

Keep the options short and concrete. "Single-family home," "Commercial building," "Multi-family / HOA." Three buttons. Do not make people read a dropdown of fourteen building classifications.

3. Are you the property owner?

The cheapest disqualifier on the form. A renter cannot authorize a roof replacement, and a significant slice of "my roof is leaking" web submissions come from tenants who should be calling their landlord. This is not a hostile question — it is a routing question. Owner goes to the main pipeline; renter gets a polite, automated "you will want to loop in your property owner, here is what to tell them" response that costs you nothing and might still earn goodwill.

A simple yes/no does it. For commercial, swap to "Are you authorized to approve roofing work for this property?" which catches the facilities manager who can sign and the receptionist who cannot.

4. What's going on with your roof? (the reason field)

This is where you learn whether you have a leak, a storm event, an aging roof, a real-estate deadline, or a curiosity. Do not leave it open-ended only — give buttons that map directly to urgency and intent, then allow a free-text box for detail.

Good option set:

• Active leak / water coming in (highest urgency)
• Storm or hail damage (urgency + a documentation pathway)
• Missing or damaged shingles (real, schedulable)
• Roof is old / planning to replace (real, lower urgency)
• Buying or selling — need an inspection (deadline-driven)
• Just want a quote / pricing (qualify carefully)
• Something else (free text)

Notice what these buttons do: they let you score urgency without asking "how urgent is this?" — a question nobody answers honestly because everybody thinks their roof is urgent. Behavior beats self-report. "Active leak" routes to your fastest responder. "Just want a quote" routes to a nurture sequence and a salesperson who knows to qualify hard before scheduling a truck.

5. When did you first notice the problem? / How soon are you looking to move?

Timeline is the other half of urgency, and it separates the genuinely-now from the eventually. "Noticed it today" plus "active leak" is a drop-everything lead. "Been thinking about it for a year" plus "old roof" is a real job that does not need to interrupt anyone's lunch.

For planned work, a forward-looking version works better: "How soon are you hoping to get this done?" with options like As soon as possible / In the next month / 1–3 months / Just researching. "Just researching" is gold — it is an honest tire-kicker flag the homeowner volunteers, and it lets you nurture instead of burning a truck roll.

6. How would you like to handle the cost? (funding pathway)

This one makes contractors nervous and it should be handled with care, but it is too valuable to skip. You are not asking for financial details. You are asking which path the homeowner is even considering, because it changes the entire conversation.

Offer neutral options: Paying out of pocket / Interested in financing / Going through an insurance claim / Not sure yet. Each routes differently. "Financing" tells your salesperson to lead with monthly numbers and have the application ready. "Insurance claim" tells you this is a storm-pathway lead that needs thorough documentation and a clean, accurate estimate.

A hard compliance note on that last bucket, because it is where roofers get themselves in trouble. If a lead selects an insurance pathway, your job is to document the roof thoroughly and prepare an accurate repair estimate for the homeowner. That is it. You inspect, you photograph, you write a defensible, Xactimate-aligned scope for the work you would do, and you hand it to the homeowner. The homeowner files the claim. The insurer decides coverage.

You do not — on your form, in your auto-reply, or anywhere in the sales conversation — promise that the claim will be approved, promise a specific payout, tell them their deductible will be waived or absorbed, advertise a "free roof," or offer to negotiate or "handle" the claim on their behalf for a fee. Those moves cross into unlicensed public adjusting in most states and into deceptive-practice territory under consumer-protection law. The safe and honest frame is documentation and an accurate estimate. Keep your form copy on that side of the line. (More on the wording in the storm section below.)

7. Best phone number and best time to reach you

Speed-to-lead is the most studied number in inbound sales, and the finding is brutal and consistent: contact rates and qualification rates collapse as minutes pass. A lead worked in the first five minutes is contacted at a dramatically higher rate than one worked at thirty. So the form's job is to hand your team a number that will actually be answered.

Ask for the best number and, critically, the best time. "Best number to reach you" plus "Best time to call: Morning / Afternoon / Evening." Honoring "evening" instead of blasting them at 9 a.m. is the difference between a connect and a block. It also signals you respect their time, which sets the tone for the whole relationship.

8. Contact consent and channel preference

Two jobs in one small field. First, consent — a clear checkbox that the homeowner agrees to be contacted by phone, text, or email about their request. If you intend to text (and you should — texting is often the fastest path to a connect), your consent language and your records need to reflect that, because telemarketing and texting rules under the TCPA and FCC are enforced and the penalties are per-message. Get clean, documented, express consent at the point of the form. Talk to your own counsel about the exact language; do not copy a competitor's checkbox and assume it covers you.

Second, channel preference — "How should we reach you first? Call / Text / Email." Some of your best leads will never answer a cold call but will reply to a text in ninety seconds. Asking lets you meet them where they are.

Optional fields worth considering by trade

A few questions don't belong on the universal form but earn their place for specific shops. Add them only if you are the shop they apply to.

• Roof material / current roof type. Useful for commercial and for residential outfits that don't do every system. "Asphalt shingle / metal / tile / flat-low-slope / not sure" lets you route a tile or standing-seam job to the right estimator and screen out systems you don't touch. For most residential shingle shops the imagery-derived data tells you this anyway, so skip it on the form.
• Approximate roof age, homeowner's best guess. Tempting, and worth one optional dropdown ("under 10 years / 10–15 / 15–20 / 20+ / no idea") precisely so you can compare it to the verified range. The gap between what they guess and what the imagery shows is a useful discovery prompt — not a number to score on directly, because "no idea" is the most honest and most common answer.
• Number of stories / steep or walkable. Niche but real for safety and pricing on the residential side; a two-story steep-slope changes your labor and your OSHA fall-protection setup before you ever quote.
• Photo upload. A single optional "add a photo if you have one" field is gold on storm and leak leads. A picture of a ceiling stain or a pile of granules in the gutter tells your estimator more than three text fields, and the homeowner who bothers to upload one is self-selecting as serious.

None of these are required, and none should push a homeowner in distress through more than a tap or two. The rule holds: if it doesn't change your next action for your kind of work, it doesn't go on.

That's the core. Resist the urge to add more.

Eight required-ish fields, several of which are one-tap buttons, is already on the heavier end for a web form. If you are running paid traffic to a landing page, use a two-step form: capture address and reason on step one (the commitment), then phone, timing, and consent on step two. People who complete step one are invested and finish at a high rate, and you have captured the two most valuable fields even from partial completions — which means a number to chase even when someone bails before the end. Some intake teams set up a soft alert on those partial submissions and call them too; a real address and a stated problem is plenty to act on.

A reference form you can copy

Here is the working layout, in order. Order matters — start with the easy, benefit-framed question (address, sold as "so we can pull up your roof") and save consent for last.

Notice email is optional and near the bottom. For a roofing job you live and die by the phone; email is a nice-to-have for follow-up, not a qualifier. Do not let it sit in the prime real estate at the top of your form where address belongs.

Turning answers into a score

A form that collects clean data and then dumps it undifferentiated into one queue has done half the job. The other half is scoring — converting those answers into a single number or tier that tells your team who to call first and how hard to push.

Keep the model simple enough that a human can sanity-check it. A 100-point scale with four or five weighted inputs is plenty. Here is a starting rubric you can tune to your own close data.

A sample scoring rubric

Sum it up and bucket the result:

• 80+ — Hot. Owner, urgent, reachable, real job. Call within five minutes, route to your best closer.
• 55–79 — Warm. Real job, less urgent or a missing data point. Call same day, standard pipeline.
• 30–54 — Nurture. Researching, unsure on funding, or a quote-shopper. Automated follow-up, light-touch sales, no truck roll yet.
• Below 30 or fails the gate — Disqualify or refer. Renter, out of area, out of scope. Polite auto-response, no human time.

The exact thresholds matter less than the discipline of having them. Once leads are tiered, your speed-to-lead policy writes itself: hot leads get the five-minute treatment, warm leads get same-day, and you stop spending your fastest response on someone who is "just researching."

One caution: score off behavior and verifiable facts, not vibes. "They sounded motivated" is not a field. "Selected active leak, owner, ASAP, in-area, gave evening as best time" is. The whole point of the form is to replace gut-feel triage with something repeatable.

The self-reported data problem — and how to fix it

Here is the uncomfortable truth that undermines a lot of qualification forms: people are unreliable narrators about their own roofs. A homeowner genuinely does not know if their roof is twelve years old or twenty. They will check "storm damage" because a neighbor got a new roof, when their shingles are just sun-baked and curling from age. They will say "ASAP" because everyone says ASAP. Self-reported intake is noisy, and scoring noisy inputs gives you a confident-looking number built on sand.

The fix is to pair what the homeowner tells you with data you can verify independently before anyone calls. Two facts about the property are knowable without a truck roll: roughly how old the roof is, and what weather it has actually been through.

This is where pulling roof intelligence on the address — at the moment the form is submitted — changes the quality of every downstream decision.

Verifying "is this roof actually due?" before you call

The address field, the one we put at the top of the form, is the key. With an address you can pull an independent read on the property and answer two questions the homeowner cannot reliably answer themselves:

• Is the roof old enough to plausibly need work? Roof age estimated from aerial imagery comes back as a range, not a birth certificate — something like "replaced roughly 14 to 18 years ago" rather than a precise install date. That range is exactly what you want for qualification. A roof in a 16-to-20-year band on asphalt shingles is squarely in replacement territory; a roof estimated at 3 to 6 years old, no matter what the homeowner clicked, is almost certainly not a tear-off. When the form's self-reported answer and the imagery-derived age agree, your confidence in the lead goes way up. When they conflict, you have a useful flag to probe on the call.
• Has real weather hit this specific roof? Storm exposure modeled per individual roof — accounting for the hail and wind that actually passed over that address, rather than merely "a storm was in the county" — tells you whether a "storm damage" claim has physics behind it. This is expressed as odds and severity, not proof of damage; only an inspection confirms damage. But it sharply sorts the "my neighbor got a new roof so I should too" leads from the ones where the roof genuinely took a beating.

This is the core of what RoofPredict does: it tells you, house by house, which roofs are due — a roof-age range from aerial imagery plus storm physics modeled per roof — and it enriches your own lead list and CRM with those signals. It is not a lead-buying service and it does not replace an inspection. What it does is turn a noisy, self-reported web form into a scored, verified opportunity, and let you append the same age-and-storm signals to the contact list you already own. When a form comes in, you can have the roof-age range and storm exposure for that address sitting next to the homeowner's own answers before your closer dials.

The honest limits, stated plainly: the age is a range and can be off, especially on partial re-roofs or unusual roof materials; the storm read is a probability, not a confirmed-damage finding; and neither one knows what is happening under the deck. Treat both as a strong prioritization signal that makes your form smarter and your truck rolls more productive — not as a verdict. Used that way, it is the difference between guessing which inbound leads are real and knowing where to look first.

Putting verification into the score

That "roof age data shows roof is due" line in the rubric above is where this lands. A warm lead whose imagery says the roof is 18-plus years old jumps to hot. A "storm damage, ASAP" lead whose address shows essentially no significant storm exposure and a roof estimated at four years old drops to nurture and gets a gentle, honest call instead of a rushed truck roll. You are no longer scoring what people claim. You are scoring claims cross-checked against the property.

Speed-to-lead: the multiplier that makes good questions worth it

You can have the best form and the sharpest scoring in your market and still lose, because none of it matters if the hot lead sits. The most replicated finding in inbound sales research is that the odds of contacting and qualifying a lead fall off a cliff as time passes — minutes, not hours, are the unit that matters. A lead called within five minutes is reached and worked at a far higher rate than one called even thirty minutes later, and the curve only gets steeper from there.

So wire your scored leads to action automatically:

1. Form submits. Address-based roof data is pulled and appended.
2. Score computes in seconds and assigns a tier.
3. Hot leads fire an instant alert — text and/or call — to the on-deck closer, plus an auto-text to the homeowner: "Got it, [Name]. We're pulling up your roof now and will call you within a few minutes at [number]." That auto-text alone lifts connect rates because the homeowner is expecting the call.
4. Warm leads drop into the same-day queue with a target callback window.
5. Nurture leads enter an automated sequence — a helpful email, a soft text a day later — with no truck roll until they re-engage.
6. Disqualified leads get an immediate, courteous auto-response and never consume a human minute.

The form questions and the speed-to-lead system are two halves of one machine. Good questions without speed means you qualify leads beautifully and then lose them to the competitor who called first. Speed without good questions means you call everyone in five minutes including the renters and the researchers, and you burn your team out chasing noise. You need both.

What pros get wrong

A decade of watching roofing intake go sideways, the recurring mistakes:

Asking for too much. The instinct after reading a piece like this is to add every field. Don't. Each field costs conversion. If a question's answer would not change your next action, cut it. "How did you hear about us?" is a marketing-attribution question, not a qualifying question — it belongs in a post-sale survey, not on the form that is supposed to be capturing a leaking-roof homeowner in distress.

Making urgency a self-report. "How urgent is this?" gets you a form full of "very urgent" because everyone's roof feels urgent to them. Infer urgency from behavior — what's wrong, when they noticed, how soon they want it done — not from a slider that asks them to rate their own emotions.

Treating the form as a finish line. The form is the start of the qualification, not the end. Its job is to tier and route fast, not to fully close. A salesperson still has to confirm authority, dig into the problem, and qualify the budget on the call. The form gets the right person to the right lead fast; the human does the rest.

Ignoring the disqualified. A renter or an out-of-area submission is not garbage — it is a chance to be helpful at zero cost. An automated, genuinely useful response ("here's what to tell your landlord," "here's a contractor we trust in your area") builds the kind of reputation that sends you referrals later. Silence after a form submission is its own kind of bad review.

Scoring on gut, not fields. If your "scoring" is a salesperson eyeballing the inbox and deciding what looks good, you do not have scoring — you have bias, mood, and inconsistency. Write the rubric down. Make it a number. Tune it against what actually closed last quarter.

Not handing the form data to the salesperson. Plenty of shops collect good answers and then route the lead to a closer who never sees them — the CRM shows a name and number and nothing else, so the rep opens the call by asking the eight things the homeowner already typed. That is insulting to the customer and it wastes the form. Whatever the homeowner told you should land in front of the closer as a short brief: address, problem, timeline, funding, and the verified roof signals, in plain language, before the dial. A rep who opens with "I see you've got water coming in and the storm came through Sunday — let's get you taken care of" is starting the call thirty seconds ahead of where a cold opener ever gets.

Never re-tuning the rubric. A scoring model built once and never revisited slowly drifts away from reality as your market, your crews, and the weather change. Pull your closed-won and dead leads every quarter and ask the same question: did the rubric tier them right? If your hot leads stopped closing better than your warm ones, the weights are stale. Treat the score as a living thing you calibrate, not a setting you flip on once.

Forgetting consent and the rules around it. Texting a homeowner who never agreed to be texted, or calling a number on a do-not-call list, is not a growth hack — it is exposure. Get clean, documented consent on the form, respect stated channel and time preferences, and have your own attorney review your language. The cost of getting this wrong is measured per message and it adds up fast.

Putting compliance-risky promises in the funding flow. The moment your form, auto-reply, or script starts implying "we'll get your claim approved" or "your deductible disappears," you have wandered out of contracting and into territory regulated as public adjusting and policed as deceptive advertising. Stay on the document-and-estimate side. It is the honest position and it is also the safe one.

Storm and claims leads: capture the intent, stay on the right side of the line

A large share of inbound roofing leads, especially after a hail or wind event, arrive thinking about insurance. Your form should absolutely capture that — the "storm or hail damage" reason button and the "going through an insurance claim" funding option are there precisely to route these leads into the right workflow. What that workflow can and cannot say is the part that protects your license and your reputation.

What your form and follow-up can do, honestly and well:

• Capture that the homeowner believes they have storm damage and route the lead to your documentation-focused inspection process.
• Pull the storm-exposure read on the address so you walk in knowing whether real hail or wind actually crossed that roof — useful for prioritization, never a substitute for the inspection.
• Promise a thorough inspection and an accurate, well-documented repair estimate the homeowner can use. That is a real, valuable, fully-compliant offer.
• Set the expectation clearly: "We'll document everything we find and write you a detailed estimate. You file the claim with your insurer, and they decide what's covered. We'll make sure your documentation is solid."

What it must never do:

• Promise the claim will be approved or that any specific dollar amount will be paid.
• State or imply the deductible will be waived, absorbed, covered, or made to disappear. (Eating the deductible is illegal in many states and is a classic insurance-fraud flag everywhere.)
• Advertise a "free roof" or "no out-of-pocket cost."
• Offer to negotiate, adjust, interpret, or "handle" the claim with the insurer for the homeowner. That is public adjusting and in most states it requires a license you do not have.
• Interpret the homeowner's policy or coverage for them.

The line is clean once you see it: you are a contractor who inspects roofs and writes estimates for your own work. You document facts about the roof and the scope you would perform, and you hand that to the homeowner. The homeowner files. The insurer decides. Build your storm intake to do that job superbly — fast routing, thorough documentation, a clean Xactimate-aligned estimate, storm data that tells you where to look — and you will out-compete the shops making illegal promises, because the homeowners who get burned by those shops come back to the contractor who told them the truth.

A worked example, end to end

Walk one lead through the whole machine.

It's a Tuesday afternoon, two days after a hail event moved through the north side of your metro. A form comes in:

• Address: 4218 Birchwood Ln, in a ZIP that is inside your service area. (Gate: pass.)
• Property type: Single-family home.
• Owner? Yes. (+20)
• What's going on? "Storm or hail damage" + free text: "Got hit Sunday, neighbors are getting roofs looked at." (+25)
• How soon? As soon as possible. (+20)
• Cost? Going through an insurance claim. (+10)
• Phone + best time: Provided, evening. (+8)
• Consent: Checked, prefers text first.

Before scoring even finishes, the address triggers a roof-data pull. It comes back: roof age range estimated at 17 to 21 years, and the storm model shows meaningful hail exposure over that specific address from Sunday's event — odds are real, severity moderate-to-high. The roof is plausibly due on age alone, and the storm read backs up the homeowner's story. (+15 for roof-is-due confirmation.)

Score: well past 80. Hot. The system instantly texts your on-deck closer the lead with the roof-age range and storm read attached, and auto-texts the homeowner: "Thanks [Name] — we see the storm came through your area Sunday and we're pulling up your roof now. We'll text you in a few minutes to set up a documentation inspection." Closer texts within four minutes, books a next-morning inspection, and walks in already knowing the roof is old enough and the storm was real — so the conversation is about documenting thoroughly and writing an accurate estimate, not about guessing.

Now run a near-identical lead through it: same form, same "storm damage, ASAP, insurance," but the address comes back with a roof-age range of 3 to 6 years and essentially no significant storm exposure on record. The self-reported answers are loud; the verified data is quiet. That lead does not vault to hot. It drops to a careful warm-or-nurture, and your closer calls knowing to gently probe — "tell me what you're seeing" — instead of rolling a truck on a four-year-old roof that a county-wide storm rumor stirred up. Same form, same homeowner enthusiasm, completely different and correct response, because the data did the sorting.

That contrast is the entire argument for building the form this way. The questions capture intent. The verification keeps you honest about which intent is backed by reality. The scoring turns both into a decision. And speed-to-lead makes sure the good one doesn't get away.

A 30-day rollout plan

You don't need a six-month project to put this in place. A focused month gets you most of the way.

Week 1 — Audit and rewrite the form. List every field on your current form. Map each to one of the four buckets (in-scope, urgency, authority, contact). Kill the orphans. Add the missing core fields — address at the top framed as a benefit, the reason buttons, owner question, timeline, funding, best-time, consent. Keep it to roughly eight fields plus consent.

Week 2 — Build the score and the tiers. Write the rubric down as a real document. Pull last quarter's closed jobs and dead leads and back-test: would your rubric have tiered the winners as hot and the losers as nurture? Adjust weights until it does. Define your three tiers and the response policy for each (five-minute, same-day, nurture, auto-decline).

Week 3 — Wire speed and routing. Connect the form to instant alerts for hot leads, an auto-text to the homeowner, a same-day queue for warm, and an automated sequence for nurture. Write the auto-responses, including the courteous renter and out-of-area replies. Have your attorney sign off on the consent language and any storm/claims wording.

Week 4 — Add verification and measure. Bring in address-based roof-age-range and storm data so it appends to each lead at submission and feeds the score. Then watch the numbers that matter: form completion rate, speed-to-first-contact, contact rate by tier, inspection-to-sale rate by tier, and — the one that pays for everything — cost per booked inspection. If your hot tier isn't closing at a meaningfully higher rate than your warm tier, your rubric needs another pass.

Measure, tune, repeat. A qualification system is never finished — it is calibrated against what actually closes, every quarter.

The bottom line

Your contact form is the cheapest salesperson you will ever hire, and most contractors have it answering the phone with "how can I help you?" and nothing else. Give it real questions — address, property type, ownership, what's wrong, how soon, how they'll pay, how to reach them, and consent — and every one of those questions earns its place by changing what you do next. Score the answers into tiers. Verify the noisy self-reported claims against what the property actually shows. Route the hot ones to your best closer inside five minutes and let the researchers nurture themselves.

Do that and the math changes. You stop paying truck-roll costs to inspect four-year-old roofs. Your closers spend their hours on owners with real, due roofs and a path to pay. And the homeowners who came in scared about a leak or a storm get a fast, honest, well-documented response instead of a voicemail and a sales pitch. The form did the sorting. Everyone downstream gets to do their actual job.

If you want the verification half handled — the roof-age range from aerial imagery and the storm physics modeled per roof, appended to each inbound lead and to the list you already own — that is exactly the signal RoofPredict was built to put in front of your team before they dial. Honest limits and all: a range, not a date; odds, not proof; a strong place to start, not a verdict. Pair it with the right questions and a five-minute response, and your inbound flow stops being a guessing game.

FAQ

How many questions should a roofing lead form have?

Aim for roughly six to eight fields, several of them one-tap buttons, plus a consent checkbox. Completion rates drop measurably as you add fields past four or five, so only include a question if its answer changes your next action — whether you call, who calls, how fast, or what they say. If you run paid traffic, a two-step form (address and problem first, then phone and timing) captures the most valuable fields even from partial completions.

What's the single most important field on a roofing contact form?

The property address, or at least the ZIP code. It instantly filters for your service area and, with a full address, lets you pull an independent read on roof age and storm exposure before anyone calls. Frame it as a benefit — 'so we can pull up your roof before we call' — to keep completion high. If full address scares people off, make ZIP required and street address optional but encouraged.

How do I qualify a roofing lead without scaring the homeowner off?

Use short, concrete button choices instead of open-ended interrogation, frame data-collection as a benefit, and make the heavier questions (like funding) optional with neutral wording. Infer urgency from behavior — what's wrong and how soon they want it done — rather than asking people to rate their own urgency. The lighter and more benefit-framed the form feels, the more honest, complete submissions you get.

Should I ask about budget or insurance on the form?

Ask how they're thinking about paying, with neutral options like out of pocket, financing, insurance claim, or not sure — but don't ask for financial details. The funding pathway changes the whole sales conversation and routing. If a lead selects the insurance pathway, your job is to document the roof thoroughly and write an accurate repair estimate the homeowner files themselves. Never promise claim approval, a payout, or a waived deductible on the form or anywhere else.

How fast do I need to respond to an inbound roofing lead?

Minutes, not hours. Contact and qualification rates fall off sharply as time passes, and a lead worked within five minutes is reached at a far higher rate than one worked at thirty. Wire your hottest tier to fire an instant alert to your on-deck closer plus an auto-text to the homeowner so they're expecting the call. Slower tiers can get same-day or automated nurture, which is exactly why scoring leads first matters.

What should I do with leads that don't qualify?

Send an immediate, genuinely helpful automated response and don't spend human time on them. A renter gets guidance on looping in their property owner; an out-of-area submission gets a referral or a polite explanation. These cost you nothing and build goodwill that can turn into referrals later. Silence after a form submission reads as poor service even from someone you were never going to sell.

How does lead scoring work for roofing companies?

Assign points to verifiable signals — owner versus renter, the stated problem, timeline, funding pathway, reachability — and gate on service area. Sum the points and bucket leads into tiers like hot, warm, nurture, and disqualified, each with its own response speed. Score on fields and behavior, not gut feel, and back-test the rubric against what actually closed last quarter. Tune the weights until your hot tier closes at a meaningfully higher rate than your warm tier.

Can I trust what homeowners report about their own roof?

Only partly. Homeowners often don't know their roof's true age and may report storm damage when shingles are simply aging. The fix is to cross-check self-reported answers against data you can verify from the address — an estimated roof-age range from aerial imagery and storm exposure modeled per roof. When the homeowner's answer and the property data agree, confidence rises; when they conflict, you have a useful flag to probe on the call rather than a wasted truck roll.

How does roof-age and storm data improve lead qualification?

It turns noisy self-reported intake into a scored, verified opportunity. Pulled on the address at form submission, a roof-age range tells you whether a roof is even old enough to need work, and a per-roof storm model tells you whether real hail or wind actually hit that address. Both feed the score so a genuinely due, storm-hit roof jumps to hot while a four-year-old roof riding a storm rumor drops to nurture. Honest limits apply: age is a range not a date, storm is odds not proof, and neither replaces an inspection.

What questions should I avoid on a roofing lead form?

Skip anything whose answer won't change your next action. 'How did you hear about us?' is marketing attribution, not qualification — move it to a post-sale survey. Avoid self-reported urgency sliders, since everyone marks 'very urgent.' Don't request detailed financial information, and never include language promising claim approval, a specific payout, a waived deductible, or a 'free roof,' which crosses into deceptive advertising and unlicensed public adjusting.