Roofing insurance claim intake: the 3 data points your dispatcher must capture
Three fields on a call card decide whether a storm-damage lead turns into a signed contract or a wasted truck roll: carrier, date of loss, and deductible. Miss any one of them on the first call, and your roofing insurance claim intake leaks time, inspection slots, and revenue straight to the competitor who asked the right question first. This post breaks down the three must-capture data points, why each one changes how the job gets sold, and gives you a downloadable intake template you can hand your dispatcher (or load into an AI receptionist) before the next hail line rolls through.
Why roofing insurance claim intake lives or dies on three data points
A storm-damage call is not a normal service call. The homeowner is juggling a wet ceiling, a skeptical adjuster, and a deductible they may not have budgeted for. Your dispatcher’s first 90 seconds are not for selling — they are for capturing enough structured information that the inspection and the estimate start from solid ground.
Most roofing shops capture name, address, and “there’s hail damage.” That is a message slip, not intake. The three data points that actually change how the job moves are carrier, date of loss, and deductible. Each one controls a different downstream decision:
- Carrier controls which adjuster your estimator sits across from, which depreciation rules apply, and whether Xactimate line items clear without a fight.
- Date of loss controls whether the claim is inside the carrier’s filing window, whether damage is attributable to a documented storm event, and how urgent the inspection really is.
- Deductible controls whether the homeowner can afford to move forward, how the estimate is framed, and whether the job is worth the truck roll.
Skip any one of the three on the first call and the second call becomes a re-interrogation — which homeowners hate, and which is the fastest way to lose a claim to a shop that asked better questions first. This is the same speed-to-lead dynamic we break down in the roofing speed to lead post, applied to the intake form instead of the stopwatch.
Data point 1: carrier (and why “I think State Farm?” is not an answer)
The carrier field drives more downstream decisions than any other piece of intake data. It tells your estimator which adjuster relationship matters, which claim portal to watch, and which carrier-specific quirks to plan around before they cost you a supplement.
Your dispatcher should capture three things under the carrier header, not one:
- Carrier name, spelled correctly. State Farm, Allstate, USAA, Liberty Mutual, Travelers, Farmers, Nationwide. If the homeowner is not sure, the declarations page or the insurance card in their wallet will say.
- Claim number, if one has been opened. A claim number means the adjuster clock is running. No claim number yet means the homeowner is still deciding whether to file — a different conversation your estimator needs warning about.
- Adjuster name and phone, if assigned. Usually blank on the first call. That’s fine. A blank field is information too: it tells your estimator to expect to make first contact.
The Insurance Information Institute’s homeowners insurance overview walks homeowners through the same checklist, which confirms what the carrier expects them to have in hand by the time they call you.
Data point 2: date of loss (the claim clock your dispatcher must start)
Date of loss is the field most dispatchers mis-capture or skip. Homeowners say “last week” and the intake note says “last week.” That is not usable downstream.
Every carrier imposes a filing window — commonly one year from the date of loss, sometimes two, depending on state and policy. A claim filed outside that window is denied on a technicality, no matter how obvious the damage. Your dispatcher needs an exact date, or the closest approximation.
When the homeowner cannot pin it down, the fallback is the storm event. The NOAA Storm Events Database logs hail and high-wind events by county and date — your dispatcher can cross-reference the approximate timeframe and log the matching storm date as the documented date of loss. Out-of-state storm chasers do this before they even arrive in a market, and it is why they close claims your shop could have owned.
A good intake captures three things under date of loss:
- Specific date (or best estimate with “approx.” flag)
- Storm event, if one is known (hail, wind, fallen tree, ice dam)
- Days since loss, calculated once the date is entered — so the dispatcher sees whether the claim is fresh, stalled, or approaching a deadline
A claim that is 11 months old is not the same lead as one that is 72 hours old. Your inspection scheduling, sales approach, and supplement strategy all depend on knowing which one you have. For the triage logic on top of this field, see the roof leak triage questions post.
Data point 3: deductible (the number that decides if the job happens)
The deductible is the single number that decides whether the homeowner can proceed, and it is the field dispatchers are most uncomfortable asking about. They shouldn’t be. The homeowner already knows the number; asking politely saves everyone a wasted inspection.
Wind/hail deductibles in the hail belt are typically 1% to 5% of dwelling coverage, which on a $400,000 home means $4,000 to $20,000 out of pocket. Many policies split “all other perils” (a flat $1,000 or $2,500) from wind/hail (a percentage), and the homeowner often does not realize they have a separate wind/hail deductible until you ask.
The dispatcher should capture:
- Deductible amount in exact dollars if known. Otherwise flag “homeowner to confirm from dec page.”
- Deductible type — flat dollar, percentage of dwelling, or split (wind/hail separate).
- Affordability signal. Not a direct question. A gentle “ready to move forward if the carrier approves the claim?” captures whether the homeowner has mentally budgeted.
An affordability signal is not a disqualifier. Plenty of homeowners find the deductible once the claim is approved and the ACV check clears. But an estimator who walks into a $12,000 deductible conversation blind is one who just lost the job. The Insurance Information Institute’s guide to deductibles is worth handing any homeowner confused about what their own policy says.
The intake template: what every roofing dispatcher should have on screen
Below is the structured intake your dispatcher (or your AI receptionist) should run through on every storm-damage call. Keep it short; keep it in this order. Capturing the five contact fields first earns the right to ask the harder questions about carrier, date of loss, and deductible.
| # | Field | Required | Notes |
|---|---|---|---|
| 1 | Homeowner name | Yes | Spelled; plus preferred contact name if different |
| 2 | Service address | Yes | Include ZIP; flag rural access or HOA |
| 3 | Phone (mobile) | Yes | Confirm it’s the best number; flag landline |
| 4 | Yes | For the estimate, adjuster thread, and PDF | |
| 5 | Damage type and location | Yes | Hail, wind, fallen tree, leak, ice dam, unknown |
| 6 | Carrier name | Yes | State Farm, Allstate, USAA, etc. |
| 7 | Claim number, if opened | If open | Blank = claim not yet filed |
| 8 | Adjuster name and phone | If assigned | Usually blank on first call |
| 9 | Date of loss | Yes | Exact date or best approx; flag storm event |
| 10 | Deductible amount | Yes | Flat $ or % of dwelling; note if unknown |
| 11 | Deductible type | Yes | Flat, percentage, or split wind/hail |
| 12 | Affordability signal | Yes | ”Ready to proceed if approved?“ |
| 13 | Preferred inspection window | Yes | Morning, afternoon, weekend; note availability |
| 14 | How they found us | No | Source tag for marketing; not a blocker |
| 15 | Notes | No | Anything the homeowner volunteered |
Bold fields are the three must-capture data points. Everything else supports them. If your current call script does not have lines 6 through 12 in it, your intake is leaking.
Why AI receptionists capture this intake more consistently than humans
A trained dispatcher running this intake on call 1 of a Tuesday morning does it well. The same dispatcher on call 47 of the 48 hours after a hail event misses fields — not from negligence, but from volume. The storm weeks we cover in the storm surge call handling post are exactly when intake discipline collapses and the three must-capture fields go blank.
An AI receptionist closes that gap in three ways:
- Every call gets the same script. No skipping the deductible question because it feels awkward. Same ask on call 1 and call 147.
- Structured capture goes directly to your CRM. ServiceTitan, Housecall Pro, JobTread, AccuLynx — fields land in the claim record instead of on a sticky note.
- Unknowns are flagged, not guessed. If the homeowner doesn’t know their deductible, the intake logs “homeowner to confirm from dec page” and fires a follow-up email instead of fabricating a number.
The honest tradeoff is in the edge cases — adjuster already on property, second-mortgage lender holding the check, homeowner crying because a tree is through the kitchen. Those belong with a human. For the full breakdown of where AI wins and where humans win, see AI receptionist vs answering service. For how the rest of the roofing intake stack fits together, the roofing vertical page lays out the full call-handling workflow.
Frequently asked
Q: Is it legal to ask a homeowner for their claim number and deductible on the first call? A: Yes. None of the three data points are protected by HIPAA, TCPA, or state privacy law — they are routine intake fields that every adjuster, carrier, and roofing estimator will ask about anyway. Capture them on the first call and save everyone the re-interrogation.
Q: What if the homeowner doesn’t know their deductible? A: Log “homeowner to confirm from dec page” and move on. Most homeowners can find the number on their declarations page (the cover sheet of their policy) in under five minutes, and a quick follow-up email with a template request usually closes the loop before the inspection.
Q: Should I train my dispatcher on the carrier’s specific claim process? A: Only at a high level. Your estimator is the one sitting across from the adjuster, so the carrier-specific knowledge lives there. The dispatcher’s job is to capture the carrier name, claim number, and adjuster contact accurately so the estimator walks in prepared.
Q: How do I handle a call where the homeowner hasn’t filed a claim yet? A: Capture carrier and date of loss as you would for an open claim, and leave claim number and adjuster blank. Flag the record “pre-claim” so your estimator walks the homeowner through the filing decision during the inspection.
Q: What’s the single most commonly skipped field? A: Deductible type. Dispatchers capture the amount (“$5,000”) and skip whether it’s a flat deductible, a percentage of dwelling coverage, or a split wind/hail. That ambiguity costs estimators an average of one follow-up call per claim, and in storm weeks it adds up fast.
Not legal or insurance advice. Specific policy terms, filing windows, and claim procedures vary by carrier, state, and individual policy — always confirm with the carrier’s declarations page and the state department of insurance before relying on intake fields for a coverage decision.
Download the roofing insurance claim intake template
Hand your dispatcher (or load into your AI receptionist) the exact 15-field intake template above, formatted as a one-page PDF and a JSON schema for CRM import. Every bold field is required before the call ends, so the three must-capture data points make it onto the record every time.