Roofing has a phone problem the other trades do not quite share. It is not steady volume with the occasional emergency; it is long stretches of ordinary quote traffic broken by a week when one hailstorm or one wind event hands every roofer in the region the same hundred calls at the same time.
What makes that harder than it sounds is the mix. A cold snap gives an HVAC shop emergencies — urgent, obvious, high-value. A storm gives a roofer mostly quote requests, a few genuine active leaks buried among them, and a growing pile of insurance-claim calls that arrive weeks later on the same line. Those three need different handling, they arrive interleaved, and the person best placed to answer is usually on a roof.
For transparency, since it shapes the framing: Reign AI builds an AI receptionist on human-grade voice AI, which is one of the options weighed here. The page is written to stay useful to a roofer who reads it and chooses differently.
Why storm week breaks a normal setup
Work through an ordinary version, with every assumption stated so you can substitute your own:
- A hail event crosses your service area on a Tuesday afternoon.
- Say 60 calls arrive over the next four days — a figure a small crew would recognise after a real storm, and one you should replace with yours.
- Your crews are working. Say the phone gets answered on 15 of them, mostly in the truck between jobs.
- Of the other 45, say 10 leave a voicemail. The remaining 35 call the next roofer, because a homeowner with a wet ceiling and an insurance deadline is working down a list.
The lost value is not 35 roof replacements — most of those calls were never going to convert, and honest arithmetic has to say so. But at any realistic close rate on storm-driven inspections, a fraction of 35 is still the difference between a good quarter and an average one, and you lost them without ever knowing they rang.
Those are worked figures from stated assumptions, not a claim about your business.
The structural point is the part worth keeping: the week you are least able to answer the phone is the week the phone is worth the most, and unlike a seasonal trend you cannot staff for it, because you do not know which Tuesday it is.
The three call types, and why mixing them costs you
Most answering scripts written for contractors treat every inbound call as one flow. In roofing that is the actual failure:
| Active leak | Storm quote | Insurance follow-up | |
|---|---|---|---|
| Arrives | During and just after weather | The following week | Weeks to months later |
| Wants | Someone to stop water | A price and an inspection | A status or a document |
| Time-critical | Yes | Competitively — the list fills | No, but costly when dropped |
| Right outcome | Triage plus an honest expectation | Inspection booked on the call | Routed to whoever owns the file |
The middle column is where most shops leak money quietly. A storm quote is not an emergency, so returning it tomorrow feels safe — but the homeowner is not waiting, they are collecting inspection slots. The third column leaks goodwill instead: a customer mid-claim who cannot reach anyone assumes the job has stalled, and says so in the review that follows.
What roofing intake needs to capture
More specific than a generic script, and the differences change what the crew does next:
- Whether water is coming in right now. The one question that sorts lane one from lane two, and almost no general script asks it first.
- The address, not the neighbourhood. Storm damage is geographically tight, and knowing whether a caller sits inside the hail swath changes how you schedule the week.
- What they actually saw — shingles in the yard, a stain spreading across a ceiling, a neighbour’s roofer knocking on doors. The last one tells you you are in a competitive race you did not know had started.
- Roof age, and whether they are the original owner. It shapes the repair-versus-replace conversation before anyone drives out.
- Insurance state — filed, adjuster booked, adjuster been, or not going through insurance at all. Four different jobs for your office, and the caller will not volunteer which.
- Storey count and access. Whether the assessment needs equipment is worth knowing before the truck leaves.
- Whether anyone has already been on the roof. A tarp somebody else put on changes both the liability picture and what your crew will find.
An agent asks all of that on the fortieth call of the week in the same order as on the first. A person triaging between roofs asks the two or three that come to mind, which is not a criticism of the person.
Is answering fast really the differentiator?
In most trades the “answer faster and win” pitch is oversold. In post-storm roofing it is closer to mechanically true, for a reason that has nothing to do with being impressive: the homeowner is booking inspections, and inspection slots are the scarce thing that week. The roofers who pick up fill the calendar; the ones who call back on Thursday are calling someone who already has three quotes coming.
Note what that argument does not claim. It does not say a fast answer wins the job — the quote, the crew and the warranty do that. It says a fast answer is what gets you into the comparison at all, and you cannot win a comparison you were never entered in.
If you want the number this turns on for your own shop, the method in what missed calls actually cost transfers directly: swap the plumbing job values for your roof average and a realistic storm close rate.
How the options hold up in storm week
| Crew answering | Human answering service | AI receptionist | |
|---|---|---|---|
| 25 calls in an afternoon | A handful | Queued | All at once |
| Sorting leaks from quotes | Well, when they answer | Script-level | As configured |
| Insurance-claim vocabulary | Yes | Rarely | As configured |
| Cost during the spike | Lost work time | Rises with volume | Flat |
| Booking the inspection live | Yes | Sometimes | As configured |
The cost during the spike row reads differently here than in a trade with even volume. A per-minute answering service bills most in the week you are busiest — defensible, but worth pricing before the storm rather than after. The crew-answering column is not free either: a foreman taking calls on a roof is expensive in a way that never appears on an invoice, and it is the most common hidden cost in this trade.
For the general version of the coverage question, the after-hours answering guide is the broader treatment across trades, and the four-way comparison sets out where each option genuinely wins. The same intake pattern shows up in a trade with a completely different rhythm — see garage door companies, where the urgent call is a car trapped behind a door rather than water coming through a ceiling.
What AI answering does NOT solve for a roofer
Any provider who does not volunteer these is selling rather than explaining:
- It cannot assess a roof, and it should not guess repair-versus-replace from a caller’s description. That judgement is the entire reason the inspection exists.
- It cannot price. See the FAQ above. This is the single most common place a roofing setup goes wrong, because callers push hard for a figure and a badly-configured agent will oblige.
- It should not advise on insurance coverage. Capturing claim state is fine. Telling a homeowner what their policy covers is not a line you want your phone system on.
- It does not add crew. If storm week ends with sixty properly-captured leads and capacity for twenty inspections, answering has converted lost calls into a scheduling problem. That is a better problem to have, but be honest about which one you are solving.
- It will not know that you stopped doing flat roofs, or no longer service the far end of the county, unless somebody configured that.
- A badly-configured agent is worse than voicemail, because it is confidently wrong in front of a customer rather than silent.
Where it fits, honestly
The strongest case in roofing is not replacing your office. It is:
The calls a person can reach still go to a person. The forty that arrive in the same afternoon as a hail event, the leak at 9pm, the claim question while every crew is out — those get answered, sorted into the right lane, and booked, instead of going to voicemail during the one week of the year that pays for the quarter.
That is a narrower claim than most vendors make, and it is the version that survives a real storm.
Before you buy anything, run this test
Call whatever you are considering — your own line, a trial agent, an answering service’s demo number — and behave like a homeowner two days after hail:
- Say a neighbour’s roofer knocked and you want someone to look at your roof.
- Ask what a new roof costs.
- Say you have filed a claim but the adjuster has not been out, and ask whether your deductible applies.
- Then say water is coming through the kitchen ceiling right now, and see whether the call changes lane.
Then look at what arrived on your end. The notification is the product. A pleasant conversation that yields “homeowner wants roof quote” and a garbled address is worth nothing. An unglamorous one that lands the address, the claim state, what they saw, and whether water is currently coming in is worth the fee — and the answer to the deductible question tells you immediately whether the thing was configured by someone who understands the trade.
Any provider unwilling to let you run that test on a live agent before you commit has told you something useful.
Common questions
Can an AI receptionist quote a roof over the phone?
No, and a setup that tries is building a dispute for later. A roof price depends on square footage, pitch, layers, decking condition and access — none of which survives a phone description, and the last two are not knowable until someone is up there. The workable configuration gives your inspection fee if you have a fixed one, says plainly that the price comes after the inspection, and books the visit. Callers accept that readily; what they will not accept is a number on the phone that changes later.
How should it handle an active leak during a storm?
As a separate lane from a quote request, because those are the same call only in the sense that both start with the word roof. An active leak needs the address, whether water is coming in right now, whether it is near anything electrical, and whether they have containment. It should also say the honest thing — that nobody safely goes up in high wind or on wet shingles — so the caller knows what will actually happen tonight rather than expecting a truck. Configure that explicitly; it will not happen by itself.
Can it handle insurance-claim questions?
It can capture the claim state, which is the part that matters for scheduling: whether they have filed, whether an adjuster has been out, and the claim number if they have it. It should not advise on coverage, predict whether damage will be approved, or discuss deductibles. That is the homeowner conversation with their insurer, and a wrong steer from your phone line is a problem you would own.
Does answering faster actually win roofing jobs?
It is one of the few places in this trade where the mechanism is plain rather than argued. After a storm a homeowner calls several roofers in one sitting, and the ones who answer get onto the inspection list — not because speed impresses anyone, but because the list fills. That is a claim about being reachable, not about being cheapest, and it only holds if the inspection is booked on that call rather than promised.