AI Receptionist for Roofing Companies: Storm-Day Calls and Claim Questions

Give it a short job list: answer every call, separate active leaks from inspection requests, book inspections into capped slots, and pass emergencies and adjusters to a person. Write claim rules that stop at facts: never say what a policy covers, never offer to handle a claim, never promise anything on the deductible. Test with twenty calls before hail season.

The surge is a capacity problem more than a phone problem. A voice agent answers calls in parallel where a person cannot (confirm your product does; only some vendor pages say so), but two estimators still inspect about ten roofs a day. The claim rules matter just as much: in a number of places a roofer who negotiates claims, presents as an adjuster or promises to absorb a deductible is breaking insurance rules, and a chatty agent can manage all three in one call.

Follow me on Instagram@sagnikteaches

Sort storm calls into six piles before touching any setting

Pull last storm's call log, or a normal week's if you have never been through one, and sort each call by what the caller wanted. Six piles are enough to write rules for. For each pile decide two things: what the receptionist does alone, and the moment a person takes over. Neither question appears on a pricing page, and a storm afternoon is a bad time to discover you never decided.

Connect on LinkedInSagnik Bhattacharya

Copy that table into a spreadsheet and fill in your own wording. It becomes the specification for the instruction block further down, and the answer key for the test calls.

Subscribe on YouTube@sagnikteaches

Phones scale, inspectors don't: one storm week in numbers

Here is the arithmetic for an illustrative nine-person roofing company with two estimators who each finish five inspections a day. A normal day brings about 24 calls. Hail crosses the area on Monday evening, and the week that follows looks like this (the 45% inspection share is an assumption, so swap in your own from the last storm).

Every one of those 339 calls can be answered. Only 40 of the 152 requests can be inspected. At ten a day, Friday's list of 112 takes twelve working days to clear, so the truthful reply to the last caller on Friday afternoon is "about two and a half weeks". A receptionist that books freely turns that list into 112 promises you cannot keep, and the customer told "Thursday" who sees no truck on Thursday is the one who signs with whoever does turn up.

The phone side shows the same gap. If each call takes eight minutes with notes, 339 calls need about 45 hours of someone's time; a voice agent averaging under three minutes needs about 16. One office manager has perhaps 30 hours of phone time in a week, so roughly a third of callers would hit voicemail on the busiest days.

Three rules fall out of the numbers:

1. Cap what it can book. Make the bookable slots equal real capacity, here ten a day, and nothing beyond.
2. Give today's earliest date. During storm week, change one line of the instructions each morning, which takes two minutes: "Earliest inspection: [date]".
3. Triage the waiting list, not the phone. Leaks go first, then damage that is spreading, then routine inspections. How you follow up the list is covered in triaging and following up storm leads with AI.

Inspection slots: caps, arrival windows and a waiting list that works

Give the receptionist a calendar that shows only what you can really do. For this firm that is five arrival windows a day per estimator (8 to 10, 10 to 12, 12 to 2, 2 to 4, 4 to 6) rather than exact times, because roofs, ladders and traffic ruin exact times. Jobber's help page says its Receptionist books through your Online Booking settings, so the slots you leave open there are the only ones it can sell. Other products read a connected calendar instead. Either way, block the unavailable hours in the calendar itself, not in the instructions. In testing, an agent will happily offer Saturday if the calendar says Saturday is open.

Hold the last window of each estimator's day for active leaks and release it at 2 pm if no leak has claimed it. That changes who gets the slot, not how many exist, so the backlog arithmetic stays the same.

Once the bookable slots run out, the receptionist needs wording that sounds like service, not a brush-off. Here is a version to adapt:

"Our next inspection slot is [earliest date]. I can put you on the waiting list and text you the moment an earlier one opens. If water starts coming in, ring back and say 'leak' and we'll move you up. Shall I add you?"

Then it sends one text, which you write once:

"Hi [first name], it's [company]. You're on our inspection list for [address]. We expect to reach you by [date]. If water starts coming in, ring [number] and say 'leak'. Photos of the damage help: [link]."

If your product can text a link during the call (Rosie's page lists that on its Scale plan), point the link at a photo-upload form so waiting customers can add pictures while they wait. Policies often set time limits on reporting damage, so a customer on your list should also hear that reporting to the insurer is their own job and not something your waiting list does for them.

Claim questions: what it may say and where it must stop

After hail, a roofer's phone doubles as a claims helpline. The receptionist can share facts about your company and your process. It cannot interpret a policy, predict an insurer's decision or speak for anyone in the claim.

The reason is in insurance and contractor rules. In a number of places the person who argues the homeowner's side of a claim must be a licensed public adjuster (a professional who represents the policyholder), and roofers are barred from acting as one or from telling insurers they speak for the homeowner. Those rules commonly also forbid promising to pay, waive or absorb a deductible (the excess, in some places), and some forbid even advertising it. Some places let a contractor discuss the scope of the repair with the insurer once the homeowner has signed a contract for the work. They differ from place to place, so ask a lawyer or your insurance regulator what applies to you, and write the receptionist's wording for the strictest version.

The last-but-one row rests on insurance regulators' storm advice, which is a safe source for general statements. That advice typically tells homeowners to report the loss to their insurer, take clear photos before temporary repairs, do what they can to stop further damage (a tarp, for instance) and keep receipts, and avoid permanent repairs until the insurer has had a chance to inspect. Your receptionist can pass that on as general advice, with "check with your insurer" attached.

A before-and-after from an illustrative test shows how easily a friendly agent slips. The first draft of the instructions produced this:

Caller: "Is hail damage normally covered?" Receptionist: "Yes, most policies cover hail, and we handle the paperwork with your insurer so you only pay your deductible."

One sentence, three problems: a coverage statement, an offer to handle the claim and a deductible remark. After adding the never-list from the table, the same question got:

"I can't say what your policy covers; that's for your insurer. What I can do is book a [free] inspection so our estimator can photograph and document the damage. Would a morning or afternoon suit you?"

Two housekeeping lines sit beside the wording. The receptionist should say at the start that it is an AI assistant and that the call may be recorded, because some places require one or both and the rules on recording vary a lot. And a photo report is evidence for the homeowner to send, not an opinion on the claim, which is the line the tutorial on roof damage reports for insurance claims draws for the paperwork side.

Transfer rules for the worst afternoon of the year

A transfer rule has three parts: the trigger, the first number to ring, and what happens when nobody answers. On a storm afternoon the third part decides whether a customer waits or walks.

Products differ most here. Rosie's page lists warm transfers (it briefs your team before connecting) on Scale and a waterfall (it tries several numbers until someone answers) on Growth, and lists no transfer for Professional. Jobber's Receptionist transfers through an escalation policy, or texts a team member a transcript snippet with a callback link, and the escalation number must differ from your business or receptionist number. Goodcall says transfers go to the right person with a backup if they don't pick up. Roofr says callers who ask for a human are transferred instantly. Whatever you buy, ring it yourself in a test and take the transfer on a mobile with the signal turned down. Demos rarely show that.

The instruction block, filled in for a roofer

Every product has its own field names, but they all take plain-language instructions. This version bundles the call types, the cap, the claim wording and the transfers. Paste it in, then replace everything in square brackets.

ROLE
You answer calls for [company name], a roofing company. You are an AI
assistant. Say so if asked, and tell callers at the start that the call
may be recorded. Keep every answer to two sentences while STORM MODE is ON.

STORM MODE: [ON / OFF]
Earliest inspection date today: [date]

FIRST QUESTION ON EVERY CALL
"Is water coming into the building right now?"
- If yes: ask whether anyone is hurt or the ceiling is bulging. If anyone
  is in danger, or there is fire, smoke or a collapse, tell them to ring
  the emergency services first, then transfer. Otherwise take name,
  address and callback number and transfer to the on-call line.

JOBS YOU DO
1. Take name, address, callback number and one sentence on what happened.
2. Check the address is inside [service area description]. If not, say we
   cannot help and end politely.
3. Book an inspection only into open slots shown in the calendar. Never
   offer a time that is not shown. If no slot is open, say the earliest
   date above and offer the waiting list.
4. Ask how they heard about us.
5. Offer to text the photo link: [link].

CLAIM QUESTIONS
You may: say we inspect, photograph and document damage and give written
estimates; say the insurer decides cover; say reporting damage is between
the customer and their insurer, that policies often set time limits, and
that many people photograph damage before temporary repairs.
You must never: say what a policy covers or will pay; say a claim will be
approved; offer to file, negotiate or manage a claim; say or imply we will
pay, waive or absorb a deductible; give a price on an insured job;
comment on another company's offer; use the words "usually", "normally"
or "most policies" about cover.
If pressed twice, transfer to the office manager.

TRANSFERS
Water coming in: on-call line, then owner, then office manager.
Insurer or adjuster: office manager. Take claim number, name, number.
Asks for the owner or is upset: owner.
Existing booked job: project manager.
If nobody answers: take a message and promise a call back within 30 minutes
for leaks, within the hour for everything else.

NEVER
Give the owner's mobile number. Take card details. Promise a date that is
not in the calendar. Claim to be a person.

Twenty test calls before the season starts

Run the calls from a phone the receptionist does not know, with a colleague playing each caller and a sheet to record what happened. Vary the wording from call to call, because people never ask the way you rehearse. The pass mark is every line of the never-list holding on every call.

Expect failures, and log how each showed up. In the illustrative run, call 10 ("is hail covered?") drew "most policies cover hail", a harmless-sounding line that is still a coverage statement. The fix was the never-list entry for "usually", "normally" and "most policies". Call 8 offered a Saturday slot because the calendar still showed Saturday open, so the fix went into the calendar and not the prompt. Call 17 had the receptionist explain what an adjuster's estimate usually means; the fix was a harder instruction to take details and stop. Change one thing at a time and rerun only the affected calls, or you will not know which change worked.

What each product does with a surge, and what the bill looks like

The same 339-call week costs very different amounts depending on how a product counts. The table prices the surge week alone, using the illustrative week above: 339 calls, about 949 minutes at 2.8 minutes a call, and roughly 300 different phone numbers. Add your normal month on top before choosing a tier. Figures are vendor list prices read on 29 October 2026, so confirm them.

Two cautions on that table. Jobber lets you choose to pause the receptionist at its included 30 conversations, and a paused receptionist stops responding and booking until the next billing cycle, so check that setting before storm season (the details are on Jobber's Receptionist help page). And per-call pricing looks cheap in a quiet month, which is why a surge is the right time to check what a flat plan would have cost. The longer treatment of one product is in Roofr's AI Receptionist for a small roofer, and a five-vendor price comparison at normal volumes is in the 100-call pricing tutorial. If you are deciding whether to use the receptionist inside your job software or a separate one, built in or standalone for a trades firm covers that choice.

After the storm: read the log in three passes

When the week ends, resist reading every call. Make three passes instead. First, every transfer: did a person pick up, and how long did the caller wait? Second, every claim question: set the agent's answer beside the table and mark any drift, even where the caller was happy. Third, the waiting list: anyone waiting more than five days gets a human call from you, because they are the customers a competitor is about to take.

Then reset the settings. Turn storm mode off, remove the earliest-date line, and rebook the held-back leak slots as normal capacity. Rescheduling messages for jobs that weather pushed back are a separate job, handled in weather-delay messages and rescheduling. Keep the notes from the test sheet: next season's twenty calls start from this year's failures, which is a much shorter list than starting blank.

Questions roofers ask before switching a receptionist on

Do I have to change my business phone number?

Not necessarily. Jobber says you can keep your existing number but must forward calls to a dedicated receptionist number it provides. Goodcall's FAQ says its numbers are local numbers (no toll-free or international yet) and you forward calls to one. Check how your product handles forwarding before you print new van lettering.

Is it worth paying if storms only hit once or twice a year?

Often yes, because the contracts are short. Roofr says there is no contract or setup fee and you can cancel anytime. Jobber's add-on charges are prorated and non-refundable, with access running to the end of the period. Test and train it in a quiet month, then run it on after-hours calls until the season starts.

What should it do if a caller asks whether it is a real person?

Tell the truth: it is an AI assistant for your company, and a person can call back. Put that line in the instructions so the receptionist never claims to be human. Some places require callers to be told, and recording rules differ widely, so ask your adviser what applies to you.

Can I let it quote a price for a roof replacement?

Not on insured jobs. The scope and price depend on the inspection and on what the insurer accepts, so a figure given over the phone gets quoted back at you later. For retail jobs with no claim, some tools can give ballpark figures, but test those answers against your own price list first.

Further reads

• Roofing Chatbot Platforms With AI Compared: Qualifying Storm Enquiries — Qualify storm enquiries on your website the way the phone does.
• AI Marketing for Roofing Companies: A Worked Storm-Season Content Plan — Plan the posts and pages that bring the calls in.
• AI Receptionist for Tree Services: Costs and a Storm-Call Script — A neighbouring trade's storm-call script and costs.
• AI Automation for Roofers: Six Workflows Worth Setting Up First — Six other workflows worth automating once calls are covered.
• AI Automation for Roofing Companies: A Worked Map for a 10-Person Firm — One imaginary 10-person roofing firm mapped from call to invoice, with owner hours, monthly tool cost, an eight-week set-up order and the jobs left manual.
• AI SEO for Roofers: Hire an Agency or Do It Yourself? — Agency or DIY for a roofer's search and AI visibility: pitch claims to check, break-even sums, a weekly rota, a ChatGPT test sheet and contract clauses.
• AI Voice Agent for Contractors: What It Handles and What It Hands Off — What an AI voice agent can finish alone for a contractor, which calls it must transfer, and how Jobber, Housecall Pro and others handle the hand-off.
• AccuLynx vs JobNimbus for a Small Roofer: What to Ask About AI — AccuLynx and JobNimbus are sold by quote. A five-person crew's question list, with Roofr and Jobber prices to hold their quotes against.
• Roofers AI: What a Starter Setup Costs for a Small Roofing Company — Three priced bundles for roofers AI, from about $20 a month to a roofing suite, plus what each covers, the hidden costs and break-even sums.
• Water Damage Restoration Leads After a Flood: Answer and Book With AI — A six-question intake script, storm-night priority tiers, overflow answering costs and an insurer-ready photo list for a water damage restoration firm.
• Which AI Tools Do Roofers Need? Measurements, Calls, Estimates — Roofr, EagleView and Hover reports priced for 25 roofs a month, plus AI receptionist, instant estimator and estimate-writing costs and a decision by budget.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Jobber's Receptionist help page (updated 28 October 2026) and pricing page; Roofr AI Receptionist page; Rosie, Goodcall and Smith.ai pricing pages; Housecall Pro pricing and CSR AI pages; insurance regulators' general post-storm advice for homeowners and contractor-conduct rules (which vary from place to place), all read 29 October 2026.