A real storm week is the highest-leverage moment in a roofer's calendar and the moment most phone systems break. A 4-truck roofing shop fielding 30 calls a week jumps to 200 calls in 48 hours after a hail event. The shops that win storm-week revenue have a pre-storm operating plan; the ones that lose it have a phone tree that escalates hold times until callers dial the next roofer.
This is the operating manual we recommend for roofers running AI phone answering through a storm event. It assumes you are already shipping a contractor AI like OnCrew (or an equivalent) on the line; if you are not, start with the contractor answering service decision framework and come back.
Last reviewed May 17, 2026.
Featured answer
A roofing storm-week call surge typically runs 3x to 10x normal call volume across the 48 hours after a hail or wind event. The operating moves: pre-storm, confirm AI intake captures insurance carrier, claim status, and damage type; configure the urgent-call queue so active interior leaks page the on-call crew first and roof-damage estimates queue for daytime callback. During the storm, monitor concurrent-call counts on the AI dashboard; an AI answering service handles unlimited concurrent calls without busy signals, which is the primary edge over per-minute operator services that hit operator-capacity walls. Post-storm, audit transcripts for first-contractor-of-record signals on every claim and rebook the callbacks that converted to estimates.
Why storm weeks break phone systems
Three structural failures roofers see in storm weeks:
- Per-minute live operator services hit operator-capacity walls. During a Tampa hail event or a Dallas tornado day, the operator pool is shared across every contractor and every industry. Hold times double or triple at exactly the worst time. Callers abandon and dial the next roofer.
- Voicemail or owner's-cell coverage cannot absorb the volume. A 20-call hour during a storm event means the owner is taking back-to-back calls, missing every other one, and never getting back to the active-leak callers in time to win the tarp job.
- Generic AI answering services lack insurance vocabulary. The first 30 seconds of a storm-week call usually include the insurance carrier name (State Farm, Allstate, Liberty Mutual, USAA), whether a claim has been opened, and the date of loss. Generic AI scripts that do not ask these capture a half-useful intake; specialized roofing AI captures the entire claims-ready packet.
The shops that win storm weeks have an AI front end that handles unlimited concurrent calls, a roofing-specific intake script that captures insurance details, and an on-call rotation that triages by leak severity not by call order.
Pre-storm prep checklist (run 24 to 48 hours before)
Run this checklist when your local weather service flags a likely hail or wind event:
- Confirm the AI intake script captures the insurance fields. Carrier name, claim number (if one is open), date of loss, deductible if disclosed, prior storm-damage history at the property. Most AI vendors let you push a one-line update to the intake script from your dashboard; do it before the storm hits.
- Set the urgent-call branch. Active interior leaks (water actively coming through the ceiling) page the on-call crew on Priority-1 SMS. Roof-damage estimates queue for callback the next business day. Tarp requests for storm-active homes page the on-call crew if water is still entering; queue otherwise.
- Pre-stage tarps, ladder racks, and crew assignments. The on-call crew should know who pulls a tarp truck for the first leak call and who handles inspection follow-ups. This is on the contractor; the AI cannot send a crew on the road, only flag the urgent call and capture the intake.
- Notify your CSR (if you have one) of the rotation. During business hours, the CSR converts callback queue. After-hours, the AI runs and pages the on-call crew. Confirm everyone knows the split.
- Verify your phone forwarding is conditional, not 24/7 forced. Most contractor lines forward only when busy or after-hours; during a storm event you may want to force-forward to the AI for the full 48-hour event window so no call hits a busy signal. Test the forwarding rule in your carrier portal before the storm.
Real-time storm-week operations
When the storm hits, the operating cadence is:
- Every 2 hours: scan the AI dashboard for concurrent-call counts, abandonment, and intake-completion rates. AI answering services that handle unlimited concurrent calls should show ~100% answer rate. Per-minute operator services start showing abandonment when concurrent calls exceed the operator pool.
- Every 4 hours: pull the urgent-call queue and confirm the on-call crew is acknowledging within 5 minutes. Late acknowledgements mean the rotation is overloaded; add a second on-call tech to the rotation or shift inspection visits to the next day to free up crew bandwidth.
- Real-time during business hours: the CSR (if you have one) clears the callback queue. Otherwise the owner clears the queue between site visits. Active leaks get callbacks within 30 minutes; estimates within 4 hours.
The shops that win storm weeks treat the dashboard like an air-traffic-control screen. Concurrent-call counts above 6 to 8 mean every additional call is competing for the same operator/crew bandwidth on a live service; on AI, additional calls just get answered in parallel with no hold.
The first-contractor-of-record signal
In hail and wind insurance markets, the first roofer to inspect the property usually becomes the contractor of record on the claim. Insurance adjusters often default to the first roofer's report unless the homeowner explicitly picks a different one. This is the single highest-leverage variable in storm-week revenue.
A working AI intake captures the date and time of the first call from the property, the contractor's first inspection appointment, and the insurance carrier identified by the homeowner. That packet, attached to the customer record, is what your team uses to position as first-contractor-of-record when the adjuster shows up.
Per-minute live operator services often do not transcribe call audio for review; AI services do. Audit storm-week transcripts within 72 hours and rebook any first-contact callbacks that did not convert to a scheduled inspection.
Insurance vocabulary the AI should ask about
The roofing-specific intake script should ask, on every storm-week call:
- "Has the damage been reported to your insurance carrier yet?" If yes, capture the carrier name and claim number.
- "When did the damage occur?" Capture date of loss.
- "Has another roofer been to the property yet?" First-contractor-of-record signal.
- "Is water actively coming into the home?" Active-leak escalation trigger.
- "What's the address, with the apartment number or unit number if applicable?" For the inspection appointment.
- "Best callback number and the best time window for an inspection?" For the daytime callback queue.
Most generic AI answering services do not ship this script by default. Roofing-configured AI (like OnCrew configured for the roofing trade) ships it pre-loaded.
Cost math: AI vs per-minute operator services during a storm
Consider a 6-truck roofing shop in a Texas hail-active market. Normal weekly call volume: 40. Storm week: 280 calls in 5 days.
| Coverage option | Storm-week cost | Notes |
|---|---|---|
| Voicemail + owner's cell | $0 | Lose ~120 to 180 calls to busy/no-pickup |
| Per-minute live operator service | ~$1,800 to $3,200 | Per-minute meter on long emergency calls; storm-week minute counts often double the monthly plan |
| AI service with per-minute model | Variable | Some AI services bill per-minute; risk concentrates on long claims-intake calls |
| OnCrew Pro (per-call model, 400 included calls) | $149 | 280 storm-week calls fits inside Pro; no per-minute meter |
| OnCrew Multi-Truck (1,000 included calls) | $349 | Headroom for multi-storm seasons |
The 10x to 20x cost difference on storm weeks is the largest single arbitrage in the roofing answering-service market. Per-minute live operator services bill exactly when you want them to bill the least; per-call AI plans flatten the spike.
Post-storm audit (run within 72 hours of storm end)
The two highest-value audits:
- First-contact-to-inspection conversion rate: of the calls that came in during the storm event, how many converted to a scheduled inspection? Healthy: 60% to 75%. If under 50%, the AI intake is leaving qualifying signals on the table or the callback queue is too slow.
- Estimate-to-job close rate by storm intake: of the inspections scheduled from storm-week calls, how many became signed contracts? Track this against your baseline close rate; storm-week close rates typically run higher because of urgency, but they fall if first-contractor-of-record was lost.
Both audits run from the AI's call transcript and the CRM customer record. AI answering services that ship transcripts (most do) make the audit easy; per-minute live operator services often only ship a one-line message summary, which makes the audit hard.
How OnCrew handles a storm week
OnCrew is the contractor AI answering service configured for roofing (and 12 other trades). Storm-week handling:
- Unlimited concurrent calls. A 6-truck shop fielding 50 calls in a single hour answers incoming calls without hold time.
- Per-call pricing with $0.99 overage. A 280-call storm week on the Pro plan ($149/mo for 400 included calls) costs $149 flat. The Multi-Truck plan ($349/mo for 1,000 included calls) covers a 5-storm season inside the plan.
- Roofing-specific intake: insurance carrier, claim status, date of loss, active-leak severity, first-contractor-of-record signal, address with access notes, callback window. All captured on the first call.
- Priority-1 SMS handoff to the on-call crew within 90 seconds for active-leak calls. The on-call crew confirms the tarp ETA with the homeowner; OnCrew does not commit an ETA on behalf of the team.
- Full transcripts and recordings on every call for post-storm audit.
14-day free trial, no charge during the trial. Cancel anytime.