A roofing shop's worst week is a hail event in a major metro followed by 72 hours of phone calls. A normal month is 80-150 inbound calls. A hail-event month is 600-1,200. The shops that handle the surge well dominate the insurance-claim window. The shops that send everything to voicemail miss the season.
This post walks through what a roofing-specific answering service should do during storm season, the intake schema for the four call types you'll see, and how to set up the handoffs so the right calls get the right response.
The four call types during storm season
After a storm, your inbound mix shifts. Normal mix:
- 40% estimates (new roof, repair, gutter)
- 30% follow-ups (existing customer, warranty, schedule)
- 20% routine repair
- 10% emergencies
Storm event mix:
- 50% damage inspection requests (no leak, just want it checked)
- 25% active leak / tarp requests (water coming in NOW)
- 15% insurance coordination (adjuster called, need contractor on the claim)
- 10% follow-ups and routine
The active leak / tarp request category is the priority. Those calls have a time-decay value: respond in 2 hours and you win the customer. Respond in 24 hours and the customer has already called your competitor.
The intake schema for active leak calls
Every active-leak call needs full capture:
- Customer name, callback number.
- Property address.
- Is water actively coming in right now? Yes/no.
- Where is the water entering? Specific room, specific area (ceiling, exterior wall, window frame).
- How long has it been leaking? Started during this storm, or has been intermittent.
- Has the customer placed any containers, towels, plastic?
- Is there standing water on a floor, or is it dripping?
- Is anyone at home right now? When can they be on-site?
- Does the customer want a temporary tarp tonight, or can it wait until tomorrow?
- Insurance claim status. Already filed, planning to file, not filing.
That's a 4-5 minute call. The output is enough information for your tarp crew to load the right materials and head out, or for your dispatcher to schedule first-light tomorrow.
The tarp-request branch
A tarp request is different from a repair. The script should handle it specifically.
AI behavior:
- AI captures the intake schema above.
- AI confirms tarp service is offered ("we can put a temporary tarp on tonight or first thing tomorrow, depending on weather and crew availability, let me check what we can promise").
- AI checks weather conditions: "Is it still raining and windy right now, or has it let up?"
- AI handoff to dispatch with TARP-REQUEST tag.
- Dispatch (or owner) confirms tarp availability and calls the customer back with a window.
The branch handles the common confusion: customers don't always know whether they're calling for emergency response or a quote. The script clarifies it.
The insurance-claim coordination branch
Storm events trigger insurance claims. The roofer's role on a claim is to inspect, document, and provide an estimate for the adjuster. The script should capture:
- Has the customer filed a claim yet?
- Claim number, if filed.
- Adjuster's name and number, if assigned.
- Date of loss (date of the storm).
- Insurance carrier.
- Has an adjuster inspected yet?
- What does the customer need from us, inspection, estimate, both?
This intake routes to a senior estimator who handles claims, not to the general scheduling queue. Mixing claims work into the routine pipeline slows both.
How to handle a 600-call surge week
The surge week math:
- Normal week: 30-40 inbound.
- Surge week: 200-300 inbound.
- Crew availability is finite. You'll book 60-80 tarp visits and 40-60 inspections in that week, maximum.
The answering service's job during the surge is to:
- Triage hard. Active leaks first. Insurance claims second. New estimates third.
- Set expectations realistically. "We're booking inspections for next Wednesday and Thursday, does that work?"
- Capture full intake on every call so no one has to re-qualify.
- Hold the line on quality. Don't promise what you can't deliver.
An AI answering service handles the surge volume in a way live receptionists struggle with: per-minute scaling on a 600-call week is brutal. Per-call AI with $0.99 overage on a 600-call week is manageable.
The cost math for a hail-event month, illustratively:
- AI with $349 plan + 1,000 included, then $0.99 overage on 200 extras = $349 + $198 = $547
- Per-minute live at $1.85/min × 5 min avg × 800 calls = $7,400 just in minutes
- Per-call live at $11.50 × 800 = $9,200
The category-level call is clear during storm season.
The non-active-leak inspection request
The "just want it checked" call is the volume bucket during storm season. Customers who didn't lose shingles but saw their neighbor lose some and want a free check.
The script should handle these without over-promising:
- AI: "We're seeing a lot of inspection requests this week, let me get you on the schedule. We're typically booking 7-14 days out right now during the storm response. Does that work, or is there urgency I should flag?"
- AI captures address, contact, and any specific concerns.
- AI books the inspection slot.
- AI sets expectation: "If you notice water coming in before then, call us back immediately and we'll move you up the queue."
The expectation-setting is what protects your team from angry customers two weeks later. Customers who hear "7-14 days" and get one in 10 are happy. Customers who get vague "we'll be in touch" and wait three weeks are reviewing you on Google.
The chase-the-storm vendor problem
Storm seasons attract out-of-area roofers ("storm chasers") who promise everything and disappear after the work. Your answering service can help here by capturing the trust signal early: "We're a local company based in [city]. Our license is [number]. We've been roofing in this area for [years]. We can show you references from neighbors who hired us."
Customers who hear that on the intake call are pre-qualified by the time the estimator arrives. The reputation work is half done.
For more, see the roofing answering service resource, the roofing emergency LP, and the roofing LP.
FAQs
Can the AI answering service handle a 200-call surge day?
Yes, AI doesn't have a queue or a hold time. Every caller gets answered immediately. That's the structural advantage during surge weeks. The bottleneck shifts from phone capacity to crew capacity, which is the right place to have it.
How do I handle out-of-area callers during a major storm?
Configure a service-area check in the script. If the address ZIP is outside your area, the AI politely explains and offers a referral if you have one. Don't pretend to serve areas you can't deliver in.
What about post-storm "free inspection" lead farming?
Set the policy on the front end. If you offer free inspections, the AI books them. If you offer paid inspections, the AI sets that expectation upfront. Don't let lead-farming hide your real pricing.
Does the AI capture photos from the customer?
Not directly during the voice call. The script can request the customer text or email photos to a follow-up address, and capture the photo request as part of the intake. Visual evidence helps the tarp crew know what materials to load.