AI Receptionist for Roofing Companies After a Storm

Hail hits on a Saturday afternoon. By Sunday morning your voicemail is full. By Monday your office is taking more calls in an hour than it normally takes in a day, and your two CSRs are on hold with each other.

Roofing has a different phone problem from HVAC or plumbing. An HVAC company's emergency is a single urgent call. A roofer's is a flood of calls, most of them not urgent and many of them not yours to win. The scenarios in the HVAC no-heat call test and the plumbing burst pipe test do not carry over. The questions here are about volume, filtering and promises. The general buyer's guide is AI receptionist for contractors.

What a storm surge does to a phone line

Three things happen at once.

Concurrency. Dozens of callers ring at the same time. A person answers one call at a time. Software can take several, but only up to a limit. That limit is often a pricing tier. Retell's pricing page, for example, lists 20 concurrent calls included and charges $8 per month for each additional concurrent call (Retell pricing, as of October 2026). If your whole region's phones ring in the same hour, ask the vendor for the concurrency ceiling in writing and what a caller hears when the line is full.

Billing spikes. Per-call and per-customer plans scale with the surge. Goodcall's pricing page, as of October 2026, bills by unique customers who speak with the agent, with a $0.50 charge per customer after the plan limit (Goodcall pricing). Smith.ai's page lists per-call overage between $8.50 and $11.50 depending on plan (Smith.ai pricing). A three-day spike at those rates is a real line item. Our AI receptionist cost guide breaks down how to model it.

Caller mix. After a storm, a large share of calls are people who want a free look at the roof, not people ready to hire anyone. That mix is what makes qualification the central job.

Who is actually calling

Sort your post-storm calls into buckets. These are illustrative categories, not data.

• Active leak. Water is coming in now. This is the real emergency.
• Damage suspected, wants an inspection. The largest group. Many have not talked to their insurer.
• Claim filed, adjuster scheduled. Highest intent, with timing attached to the adjuster visit.
• Claim approved, needs a contractor. The easiest to close, and your competitors are calling them too.
• Price shopping or comparing. Real, but low-intent.
• Existing customers. A warranty or a past job.
• Not a lead. Solicitors, other contractors, callers outside your service area, renters without owner authority, spam.

The agent's job is to sort callers into these buckets in under two minutes and treat each differently.

Qualification: the questions that matter

Write the intake in the order that screens fastest.

1. Is water entering the home right now? Yes means the active-leak path and a human or the on-call person.
2. Is the property in your service area? ZIP code or address check, first. It saves everyone time.
3. Are you the owner, or authorized to approve work? Tenants and relatives often cannot sign. Capture the owner's contact and note it.
4. What do you see? Missing shingles, a leak, dents on gutters or soft metals, nothing visible. The agent records it and does not diagnose. Whether there is hail damage is for an inspector to say.
5. Have you contacted your insurance company? Is there a claim number or adjuster date? Record what the caller says. Do not give coverage advice.
6. Roof type and approximate age, number of stories. Needed for scheduling and pricing the inspection.
7. Best contact method and time. Include text consent where required.

Feed these into your lead score so the office works the claim-approved and active-leak calls first. We cover how in lead scoring for home services and the follow-up logic in our AI lead generation and follow-up service.

Junk leads: filter them, but carefully

The case for AI in roofing is largely about not wasting your inspectors' time. The risk is filtering out real jobs.

Filters that are safe:

• Out-of-area addresses, handled politely with a referral line if you have one.
• Obvious solicitations from other contractors, suppliers and vendors.
• Spoofed or blocked numbers with no message.

Filters that cost you jobs if tuned too hard:

• "Does not own the home." A landlord who is on the phone in another state is still a customer. Capture, do not reject.
• "Hasn't filed a claim." Many homeowners call before they file. A good agent offers an inspection and says nothing about outcomes.
• "No visible damage." The caller may not be able to see it.

A useful rule: the agent may deprioritize, but it should rarely discard. Put low-intent callers in a slower follow-up lane instead of deleting them.

The promises an AI must never make

This is where roofing differs most from the other trades, because insurance is part of the sales conversation.

• No coverage promises. It must not say the insurance company "will cover it" or that a claim "will be approved."
• No deductible talk. The Colorado Roofing Association, in a July 2023 advisory about storm chasers, states that offering to pay, waive or rebate a deductible is illegal, and warns homeowners about contracts signed before they understand cancellation terms (Colorado Roofing Association). State rules vary, so confirm yours with counsel, and make sure your agent's script says nothing about deductibles at all.
• No arrival promises it cannot keep. After a storm, inspections back up. "We'll be there tomorrow" is a lie if your next opening is in nine days. Pull the real calendar, or say a coordinator will confirm a window.
• No diagnosis. It records what the caller reports. A human inspects.

The same association describes storm chasers as contractors who follow severe weather into new areas and pose as local businesses, and says homeowners should not rush, since a roof that is not leaking can usually wait for a reputable contractor. That is useful context for your script: a local company that sets honest expectations stands out. It is one regional trade body's advice, not a national statistic.

The failure modes to test

1. The 40-call hour. Simulate it. Place calls from several phones at once, or ask the vendor for a load test, and see what the extra callers hear.
2. Backlog honesty. On day three, the agent should tell callers the real wait for an inspection and offer a waitlist. Test that it does not default to the best-case date.
3. The leak that is buried in a long call. A caller starts with "I think I have hail damage" and mentions water on the ceiling at minute three. Does the agent catch it and escalate?
4. Claim-related questions. Ask it directly: "Will my insurance pay for a new roof?" The right answer is a polite refusal to speculate and an offer of an inspection.
5. Crew and storm-chaser confusion. A caller says "a man came to my door from your company." Do you have a rule for that? The agent should capture the detail and flag it for a human.
6. Text follow-up. Post-call texts need registration and consent. Run through the rules in A2P 10DLC registration for contractors before turning them on, and see TCPA texting rules for contractors.
7. Recordings. Storm-season calls often become evidence in an insurance dispute or a warranty claim. Know who owns them and how long they are kept.

Where AI helps, and where it does not

It helps with:

• Answering every call during the surge, with no hold queue.
• Screening for area, ownership and active leaks.
• Capturing structured details your office can work from at 7 a.m.
• Booking inspections into real availability, if integrated.

It does not help with:

• Closing the sale. A roof sells in person.
• Judgment on borderline callers.
• Capacity. If your crew cannot inspect 200 roofs in a week, a faster phone line moves the bottleneck without removing it. Set expectations early, and consider whether the answer is more inspectors or a smarter waitlist.

If you run several branches, storm calls often need routing by territory. See multi-location call routing. Angi and similar paid leads behave differently from storm calls, as covered in Angi and Thumbtack lead response.

Before storm season

Do this in March, not after the first hail event.

• Write the seven intake questions and the "never say" list.
• Set the concurrency ceiling and overage terms in writing.
• Run the 40-call load test and the insurance question.
• Choose where low-intent callers go.
• Pre-write the backlog message, so you can change one line when the queue grows.

If you want that built, tested and connected to your scheduling software, see our Booked-Jobs Recovery System.

Frequently asked questions

Can an AI receptionist handle a hail-season call surge?

It can answer many calls at once, up to the concurrency limit in your plan. Ask for the ceiling in writing, test it with simultaneous calls and check what happens to the overflow.

Will it weed out junk leads?

It can screen for service area, ownership, active leaks and obvious solicitations. Tune it to deprioritize rather than discard, because low-intent callers sometimes become real jobs.

Should it talk about insurance?

It should record what the caller says about a claim and nothing more. No promises about coverage, no discussion of deductibles. Have counsel review the script.