Roofing is the trade where missed-call economics hit hardest. When a homeowner's ceiling stained Sunday night, by Monday at 6:30am they've already filled out three contractor websites. Whoever calls back first — and sounds competent — usually gets the job. Industry data is brutal: 67% of callers hang up on voicemail, and two missed calls a week translates to roughly $50K/year in lost revenue.
The day before OpsLight
Mike's old Monday-after-storm routine: get to the office at 6am, open his email, find anywhere from 6 to 22 new form submissions from his website plus another 4-8 voicemails on the office line. Spend an hour reading and listening. Spend another hour writing back. By 10am he'd be on the road doing site inspections. By 6pm he'd be quoting. By 10pm he'd be exhausted and aware that some of those leads had already booked his competitor.
The problem wasn't his quote quality — Mike's quotes are well-priced and clearly written. The problem was elapsed time between form submission and his reply. By the time a homeowner heard back from Mike at 10am, they'd usually already gotten replies from two other roofers who'd answered automatically (or had a paid call-answering service).
The trade-forum pattern: "Lost a $40K job because I didn't have a second crew to run it." For Mike, it was usually "lost a $12K replacement because the homeowner had already booked the guy who called back in 20 minutes." Multiply across a year's worth of storms.
He'd tried two paid call-answering services. The first sent garbled summaries that were missing the address half the time. The second was so generic in its scripts that homeowners told Mike, when he eventually got hold of them, that they'd assumed his company was a national chain.
"The roofing job goes to whoever responds first AND sounds like a roofer, not a call center. I was always the second guy. The 'best price' didn't matter because I never got the chance to give it."
Mike Sutton · Sutton RoofingHow Mike found OpsLight
A property manager Mike does commercial work for asked him if he'd heard of OpsLight — her painter was using it and the auto-reply had impressed her. Mike asked one specific question on our intro call: can your auto-reply sound like me, not a chatbot? The answer was: that's exactly what it does.
Setup focused on storm intake:
- Storm-keyword classifier. "Leak," "damaged shingles," "missing tile," "wind damage," "branch through roof," "ceiling staining" all trigger urgency=high.
- Auto-reply in Mike's voice. Within 60 seconds of form submission, a personalized reply lands in the homeowner's inbox: confirms the address, sets next-step expectation ("I'll either call you within 2 hours or you'll see me at your house by tomorrow morning"), and signs from Mike, not "Sutton Roofing Team."
- Insurance carrier capture. If the homeowner mentions insurance, OpsLight prompts for carrier name and claim number in the auto-reply.
- Same-day quote draft. By the time Mike reads each lead, OpsLight has pre-built a preliminary quote estimate based on scope keywords and his standard pricing.
Live two weeks before the first big November storm of the season. That Sunday squall dumped 2.4 inches across Marin overnight.
Three moments from the Monday flood
The first lead lands, auto-reply goes out at 6:13
First storm lead arrived at 6:12 from a homeowner in Mill Valley — "branch came down through the back patio cover, water in the dining room, please help." Auto-reply went out at 6:13 with Mike's name, the address confirmed back, and a same-morning visit window. Lead was on the Sheet, classified urgency=emergency. Mike saw it on his Game Plan at 6:30 with coffee.
14 leads in the inbox, all already replied-to
By 9:47, 14 form submissions had landed since 6am. All 14 had received personalized auto-replies within 60 seconds of submission. Mike was at his desk reviewing the queue — sorting by urgency, blocking out site visits for the next 48 hours. None of the leads had heard silence from him. None had moved on yet.
The insurance lead that found its own path
One of the morning leads mentioned State Farm in the form. OpsLight's auto-reply prompted for the claim number. By 1:30 the homeowner had replied with the number and Mike had the carrier, claim number, and adjuster contact already attached to the project. The scope-of-loss document drafted itself from the site visit notes that evening. Mike submitted it to the adjuster Tuesday morning.
Six months later
Mike's storm-lead conversion rate roughly doubled — from his self-reported "maybe 25% of leads booked" to a measured 51%. He didn't change his pricing, his quality, or his crew. He changed the response time. The lead-conversion math then compounds: more booked jobs feeds more referrals, more referrals feeds more leads, more leads books more jobs.
The other change: his Monday-after-storm anxiety basically vanished. He used to dread the Monday-morning inbox open. Now he treats it like a normal Monday — coffee, queue review, day planned by 9am.
What's configured specifically for roofing
- Roofing-vocabulary classifier. Knows shingle types (3-tab, architectural, designer, slate, tile, metal panel, TPO, EPDM, modified bitumen), failure modes (lifting, missing, granule loss, flashing failure, ice dam, hail damage), structural concerns (sag, rot, decking failure).
- Storm-keyword priority. Auto-classifies storm-driven intake as urgency=high.
- Personalized auto-reply. Written in your voice. Includes the homeowner's address back to them (confirms intake), sets a callback expectation, asks about insurance.
- Insurance-job workflow. Carrier + claim # + adjuster captured. Documents formatted for carrier submission.
- Same-day quote draft. Preliminary estimate based on scope keywords + standard pricing.
- Closeout packet. Manufacturer warranty (GAF, Owens Corning, CertainTeed, etc.), lien waiver, photo release, scope-of-completed-work for the carrier.
What roofers ask us
Will the auto-reply actually sound like me?
It's tuned during install. We listen to how you talk on a real recorded call, capture the cadence and word choices, and write the auto-reply in that voice. The output is reviewed by you before going live. We re-tune as needed.
Can it handle hail / insurance storm-chasing volume?
Yes — the intake engine scales with volume. If you're getting 50+ inbound forms in a day during a hail event, OpsLight handles all of them without losing anything. Your bottleneck becomes site-visit capacity, not intake capacity.
What about supplement requests with carriers?
OpsLight generates the supplement request document from the project Sheet — original scope vs revised scope, line items, carrier-formatted. You email or upload to the carrier portal. We don't yet submit directly to Xactimate or carrier portals.
Does this work for commercial roofing too?
Yes. The intake/classifier handles both residential and commercial. Commercial roofing tends to have higher document burden (membrane spec sheets, manufacturer warranties with longer terms, insurance riders) — OpsLight templates all of it.
What's NOT included?
No Xactimate or Symbility integration. No live aerial measurement (we capture the measurements your estimator takes but don't run EagleView/Hover ourselves). No financing-application integration. Honest list before you sign.