After a hail or wind storm, roofing calls and web forms pile up faster than the office can answer. An AI assistant replies to every inquiry within minutes, asks a few triage questions (active leak? tarp needed? storm date? insurance claim started?), collects photos, and books a free inspection by area so crews aren't zig-zagging across the county. Active leaks get flagged to a person right away.
Tools used
JobNimbus, AccuLynx or Roofr (roofing CRM, scheduling, proposals)
CompanyCam (inspection photos)
Twilio or the CRM's built-in texting
OpenAI API or Claude (triage replies)
Zapier or Make (form and call-tracking intake)
Calendly or Cal.com, or the CRM's own booking, with inspection slots grouped by area
Expected outcome · Typical goal
Typical goal: every storm lead gets a reply in minutes instead of hours, active leaks reach a person the same day, and inspections are booked in tight geographic clusters so each estimator can do more per day.
Setup notes
Set up the intake before storm season (spring hail, summer thunderstorms, fall tropical remnants). Trying to bolt it on during a storm week rarely works.
Define inspection zones by ZIP code (for example south Charlotte, Union County, York County) and only offer slots in the zone the crew is already working that day.
Anything with water coming in, a tree on the roof, or a safety issue skips the bot and pages the on-call person immediately.
Don't let the AI give insurance advice, promise coverage, or talk about deductibles. It can ask whether the homeowner has called their insurer and note the claim number, and that's it.
Register your texting number for A2P 10DLC (the US carrier registration for business texting) and get consent on the web form, or messages will be filtered.
Photos uploaded by the homeowner go into the job record so the estimator sees them before arriving.
Prompt / agent config
Replace the {placeholders} with your own details.
You answer roofing inquiries for {Company} in {service area}. Reply within one text, friendly and plain, under 300 characters. First, check for an emergency: if they mention water coming in, a tree or limb on the roof, exposed decking, or anything unsafe, say a person will call within {X} minutes and create an URGENT task; stop there. Otherwise ask, one or two at a time: address (to confirm we serve it), what happened and roughly when (storm date if known), what they've noticed (missing shingles, leaks, dents, gutter damage), and whether they'd like to send a few photos. Then offer 2-3 inspection times from get_slots for their ZIP zone. Do not give prices, insurance advice, coverage opinions, or say damage is or isn't covered. If asked about insurance, say our estimator can document what they find during the inspection and the homeowner's insurer makes coverage decisions. Log every answer to the CRM lead.
Last reviewed October 19, 2026. Tool names and features change; check vendor docs before you build.
Where I set this up
I build this for businesses across the Charlotte metro and nearby NC/SC towns, remote or in person by appointment:
Every new lead, whether a website form, Google Local Services Ads message, Angi, Thumbtack or Facebook, gets a personal-sounding reply within a minute, two or three qualifying questions, and a booking link. Qualified leads are pushed to the CRM and flagged for a callback.
Home Services · Contractors & Remodelers · HVAC · Plumbing · Roofing · medium complexity
After an estimate goes out, an automated, personal-sounding follow-up runs over two to three weeks: a check-in, an answer to common objections, a gentle deadline, and a 'should I close this out?' message. Replies stop the sequence and alert the estimator.
The estimator records a voice memo and snaps photos on site. An AI workflow turns them into a structured scope of work with line items mapped to the company's price book. The estimator reviews and adjusts it before sending.
Contractors & Remodelers · Roofing · Home Services · high complexity
One practical AI use case a month, for Charlotte-area businesses.