What Can AI Agents Do for Roofers Between Lead and Signed Contract?

An AI agent can run most of the admin between a roofing lead and a signed contract: reply to the enquiry, qualify it, book the inspection, draft and chase the estimate, and send contract and deposit reminders. It should not set prices, promise insurance cover or timing, or give safety advice. A person approves anything that commits the company.

The catch is that each step carries a different risk. A late first reply loses a lead; a wrong estimate loses money; a careless sentence about insurance cover can start a dispute. So for every step, decide three things: what the agent may do alone, what waits for your click, and what never leaves your hands. Vendor pages tend to skip that part, and it is the part that decides whether an agent helps or embarrasses you.

Follow me on Instagram@sagnikteaches

An agent here means software that takes actions in your other tools as well as talking: it reads the diary, writes a CRM record, sends a message or sets a reminder, then decides what to do next within rules you give it. The example firm is a small roofer with a crew of eight, around 25 new leads a month, an average re-roof of about $14,800 and a repair ticket of about $700. Every figure is illustrative.

Connect on LinkedInSagnik Bhattacharya

The journey on one page

Notice how much of the "agent does" column is repetition: send, remind, log. The "stays human" column is judgement and commitment. That split holds at every step and is the cleanest way to decide what to automate.

Subscribe on YouTube@sagnikteaches

Step 1: the lead arrives, and the first reply goes out in minutes

A roofing lead goes cold fast, because the homeowner is usually asking two or three firms. The first firm to reply sensibly often gets the inspection. An agent watching your web form, email inbox and missed calls can reply while you are on a roof.

What it does: reads the enquiry, picks the right template (repair, replacement, storm damage, commercial), sends a reply that confirms it has arrived, asks one or two questions, and creates a lead record. What it never does at this step: quote a price, say whether a roof is repairable, or promise a date.

You reply first to roofing enquiries for a small roofing company. Under 80 words. Greet by first name, say what we understood they want, ask (a) is water coming in right now, (b) the best number to call. Offer an inspection and say we will confirm a time shortly. Never give a price, never say a roof can be repaired or must be replaced, never mention insurance cover. If water is coming in or there is storm damage, say a person will phone within the hour and give the number [phone].
Enquiry: [paste]

An illustrative case. An enquiry arrives at 7.40pm: "Lost a few tiles in the wind, there's a damp patch on the landing ceiling." The agent classes it as possible active leak, replies with the wording above, flags it red in the CRM and sends you a text. You phone within the hour, as promised. Without the flag it would have sat until morning.

The limit worth stating: an agent that can send messages needs a "stop" rule. If the customer replies "stop", "wrong number" or anything angry, it halts and hands over to a person. Test this with your own phone before it goes live. For storm days, when volume spikes, see the storm-day receptionist tutorial.

Step 2: qualify the lead without interrogating it

Qualifying decides how much of your time a lead gets. Too many questions and the homeowner leaves; too few and you waste an inspection on a job you would never take. Five or six questions, asked in a short exchange, is usually about right.

1. What is the problem, in the homeowner's words?
2. Roof type if known (tiles, slate, flat, metal) and roughly how old?
3. Is water coming in now?
4. Do you own the property, and are you the decision-maker?
5. Is an insurance claim involved, or will you pay directly?
6. When do you want the work done, and have you had other quotes?

The agent asks these over text or email, records the answers and scores the lead against your rules. Write the rules as numbers where you can. An example scoring block:

Score each lead A, B or C.
A: owner, replacement or major repair, wants work within 3 months, in our service area, no other firm already booked.
B: owner, minor repair or inspection only, flexible timing.
C: tenant without owner contact, outside area, under $400 of work, "just curious".
Return the score, the answers in a table, and the one question still missing.

AccuLynx, for example, lists AI lead scoring on both its Pro and Elite plans, so a CRM you already own may do part of this natively. Check whether yours does before you pay for a separate agent. If you use a chat assistant instead, the scoring depends entirely on how clear your rules are.

Illustrative result: of 25 leads in a month, six score A, nine B and ten C. You inspect all A, most B, and send C a helpful note with a link to your price guide. Before the agent, you inspected 18 and signed seven. Scoring will not sign more jobs from the same visits by itself; what it does is stop you spending something like a third of your inspection hours on jobs that never close.

The limit: an agent should never decline a lead on its own for anything other than "outside the service area". Anything else is marked C and a person decides. Declining work can be a legal or reputational matter, and a humane human reply to someone in distress is worth the minute.

Step 3: book the inspection, and make it stick

Booking looks easy, but there are three ways it goes wrong: slots that ignore travel time, no reminders so customers forget, and no confirmation of access. An agent with read access to your diary can fix all three.

Set your diary rules in plain words: inspection length (say 45 minutes), buffers (30 minutes between sites), the days and hours you inspect, how far you travel before an extra charge, and slots held back for emergencies. The agent offers two or three real slots, books the one chosen and sends a confirmation.

Inspection confirmation text:
Hi [first name], your roof inspection is booked for [day] at [time]. [surveyor first name] will arrive in a van marked [firm]. Please make sure we can reach [side gate / ladder access]. We will text when we are 20 minutes away. To change the time, reply to this message or ring [phone].

Reminder, 24 hours before:
Hi [first name], a reminder that [surveyor first name] is coming tomorrow at [time] to inspect your roof. If anyone needs to be home, or access has changed, tell us here.

A mistake that shows how this fails: a firm sets a rule "book any slot in the next three days". The agent books an inspection for 4pm on a Friday during a forecast gale, and the surveyor will not climb. Add a weather rule: the agent checks the forecast notes you provide, and any slot flagged high wind is held for a person to confirm. The related weather-delay rescheduling checklist covers how to rebook when the weather wins anyway.

What stays human: choosing who attends for a complex roof, a commercial site or a customer who has already complained. And the roof access decision on the day, which is always the surveyor's.

Step 4: prepare the inspection so the visit is shorter

This step is quiet and valuable. Before the visit, the agent assembles a one-page brief: the customer's words, any photos they sent, the roof type and age they gave, any claim details, notes from earlier jobs at the address and a checklist for the visit. The surveyor reads it in the van.

A brief for a fictional job might read: "Semi-detached, concrete tiles, about 25 years, lost tiles in last week's wind, damp patch on landing ceiling, owner says insurer has been told. Photos: three, show missing tiles at the ridge on the left slope. Check: ridge and hip mortar, felt condition in loft, gutters, flashing at chimney, damp in landing ceiling from loft side. Ask: has the insurer asked for a report, who is the contact, can they send the claim number?" This took the agent seconds, and the surveyor arrives knowing what to look at.

After the visit, the surveyor speaks their notes into a phone. Turning a voice note into a structured estimate input is its own subject, covered in the voice AI tutorial for roofers. Photo organisation is another, with tools like CompanyCam, whose plans differ by credits and users; check its current pricing before you plan around it.

Limits: the agent can say what to look for. It cannot say what is wrong. It does not see the roof, and a photo from a customer's phone may show tiles but not the felt or the timber under them. Never let a brief be mistaken for a diagnosis, and never let it go to the customer.

Step 5: draft the estimate, and check every line

This is the step with the most money in it, and the one where an unchecked agent costs you most. The agent's job is to assemble: take the surveyor's notes, measurements and your price list, and produce a line-by-line draft for a person to correct.

Give it your price list in a table, not from memory. A shortened example:

Using only this price list and these inspection notes, draft an estimate with each line, quantity, rate and total. Add a line for contingency only if I say so. List anything the notes do not cover under "Not included". If a quantity is not in the notes, write [MEASURE]. Do not round or adjust any rate.
Notes: roof 94 m2, concrete tiles, replace felt and battens, ridge 11 m, 2 hips 9 m total, chimney flashing renew, scaffold front and rear, skip needed.

An illustrative output: re-tile 94 m2 at $68 is $6,392; felt and battens 94 m2 at $14 is $1,316; ridge and hips 20 m at $32 is $640; flashing $420; scaffold two elevations at $480 is $960; skip $390. Total $10,118. What you would fix: nothing in the arithmetic, but the notes had no mention of fascias, soffits or the rear dormer, so "Not included" matters. You add a line for rotten timbers as a provisional sum, with the wording you use.

The risks are specific. An agent may do the sums right and still pick the wrong line for the job, such as a slate rate for a tile roof. It may carry over a rate from an earlier prompt. Always read every line, and spot-check the total with a calculator. Keep exclusions and provisional sums in your own words, because those lines settle arguments later.

What stays human: price, scope, warranty terms and anything the roof may hide. Approve every estimate before it goes out. ChatGPT's agent-style Work mode, for example, asks for approval on important actions by default, which is the right pattern to copy even if you build it yourself.

Step 6: chase the estimate without nagging

Plenty of roofing estimates are lost to silence rather than to a competitor. The estimate goes out, the homeowner gets busy and nobody follows up. An agent can run a follow-up sequence that is timely, polite and stops when it should.

A sequence that works for a re-roof estimate:

• Day 0: estimate sent, with a short summary and a link to book a call.
• Day 2: "Did the estimate arrive? Happy to talk through any line."
• Day 6: a useful piece: your standard FAQ on what the work involves and how long it takes.
• Day 12: "Is anything holding this up? Questions about timing, scope or payment are common."
• Day 25: a close-out message that leaves the door open and stops the sequence.

Day 6 message:
Hi [first name], while you decide, here are the questions people usually ask after an estimate like yours: how long the job takes (typically [X] days, weather permitting), what happens to the garden, whether we take away the old tiles, and how payment works. If any of these matter for your decision, reply and I will answer them. No pressure.

An illustrative case with numbers. Of 15 estimates a month, say five sign without chasing. The sequence brings back two more that would have gone quiet. At an average $14,800, that is nearly $30,000 a month of work from messages that took no one's time. These figures are made up, and your own will differ. Track which message in the sequence actually brings replies, and trim any that never do.

Rules for the agent: stop on any reply, and hand it to a person if the reply contains a question about price, a complaint or the words "insurance". Never offer a discount, never claim "limited availability" unless it is true, and never message outside agreed hours. The AI-qualifying and follow-up tools in CRMs differ, so see the AccuLynx and JobNimbus comparison for what to ask each vendor about AI.

Step 7: insurance and finance questions, handled carefully

Many roofing customers ask: will my insurer pay, will you deal with them, can I pay in instalments. The answers are legal, financial or contractual, and an agent's job is to give your standard, checked wording and collect what you need, not to improvise.

A standard reply on insurance might read: "We can provide a written report with photographs of the damage, which you can send to your insurer. We cannot say whether a claim will be paid, because that is the insurer's decision. If you tell us who is handling your claim, we can send the report to them with your permission." That is written once, by you, reviewed by someone who knows the rules where you work, and stored as a template.

The agent then does three things: sends that reply when the topic comes up, asks for the claim reference and the adjuster's contact if the customer has them, and logs a task for a person if the customer asks anything beyond the template. It never says "this will be covered", never advises on how to word a claim and never states the cause of damage.

For finance, the same principle applies. An agent can send your finance partner's link and the standard description of how it works, if you offer one. It must not state rates, approval chances or terms it has not been given, and it must not collect credit information.

What stays human: all of it, once the conversation moves past the template. A warm call from you to a homeowner worried about a claim is worth more than any message.

Step 8: contract, deposit and the final nudge

A homeowner says yes, and then nothing happens for a week: the contract is not signed, the deposit is not paid and the start date drifts. An agent can send the contract, track it and remind.

The flow: you approve the contract text once, as a template with merge fields for name, address, scope, price, payment schedule and start window. On "yes", the agent fills the template from the approved estimate and sends it for signature through your e-signature tool, then sends the deposit request and logs both.

Contract reminder, 3 days after sending:
Hi [first name], just checking you received the contract for [scope]. Once it is signed and the deposit is in, we can confirm your start window of [window]. If anything in it needs changing, tell me and I will sort it out. Signing takes about two minutes on your phone.

What it must never do: change a term, move a date it was not told to, or say anything about the work that is not in the contract. If the customer asks to amend the contract, the agent stops and hands over. A fictional example: a customer asks "can you do it a week earlier?" The agent has no authority over the crew's diary beyond the booking rules, so it logs a request for you, and replies that you will confirm within a day.

Track the numbers: contracts out, days to signature, days to deposit. In some firms the gap between "yes" and a signature turns out to be the slowest part of the whole journey; your own numbers will show whether it is in yours. If it averages nine days, a three-day reminder is the first thing to try.

One re-roof lead from web form to signed contract

Here is a single job, end to end, with the agent's part and yours. The figures are illustrative.

1. Tuesday 6.10pm. Web form: "Roof is old, tiles slipping, quote for new roof?" The agent replies in 90 seconds, asks if water is coming in and for the best number, and logs it. Your part: none.
2. Tuesday 6.25pm. The customer answers: no leaks, owner, wants it done before winter, other quotes pending. Score: A. The agent offers Thursday 10am or Friday 2pm. Your part: none.
3. Wednesday 8am. You see the brief on your phone. Thirty seconds to read it.
4. Thursday 10am. Inspection, 45 minutes. You dictate notes in the van afterwards.
5. Thursday 1pm. The agent drafts the estimate: 94 m2 of re-tile, ridge, flashing, scaffold and skip, $10,118 in the example price list above. You correct one line and add a provisional sum, five minutes. Your part: approve and send.
6. Days 2, 6, 12. The follow-ups go. On day 6 the customer replies asking whether you remove the old tiles. The agent uses your FAQ answer.
7. Day 8. The customer says yes, asks if the start can be before the 10th. The agent logs it, passes to you; you phone and agree a window.
8. Day 8. The contract goes out on your template. Day 11 reminder. Signed day 12, deposit paid day 12.

Your hands-on time across twelve days: about 25 minutes plus the inspection and one phone call. Without the agent, the same lead would take perhaps 90 minutes of admin spread across the same days, and the day-2 and day-12 follow-ups would often not happen at all.

What an agent costs, and what to ask a vendor

Prices vary widely, and many roofing-specific vendors show none. Set a rough picture. A general chat assistant on a business plan costs per seat per month, and both ChatGPT Business and Claude Team need at least two seats. CRMs charge per user, with AI features sometimes on higher plans only. Voice receptionists are often priced per conversation or per minute. A plain agent built on a chat assistant plus your CRM and a messaging tool can run for a modest monthly cost, though the setup time is real.

Before buying, ask each vendor these questions, in writing:

• Which of these eight steps does it do without a person? Show me.
• Can I set approvals per action, for example "send estimate: needs my click"?
• What does it do when it does not know? Does it say so or guess?
• Where are conversations and customer data stored, and can I export and delete them?
• What is the full monthly cost at my volume, including messages, seats and add-ons?
• How do I see everything it has sent, and how do I switch it off in one click?

If an answer is vague, treat it as no.

The limits and guard rails every step shares

• Approvals. Anything that commits money, a date or a promise needs a person: estimate sends, contract changes, discounts, schedule changes.
• A hard stop. The agent halts on "stop", on anger, on a mention of injury or on a claim that something is dangerous, and a person takes over.
• No invented facts. The agent uses only your price list, your templates and the customer's own words. Tell it to write [MISSING] rather than guess.
• A log. Every message sent is recorded where you can search it. Read ten a week for the first month.
• Quiet hours. No messages late at night or early in the morning, except an emergency acknowledgement.
• Privacy. Customers' details go only into tools you have checked, on a business plan where you can. Leave out what the job does not need.

Five agent slips and the rule that stops each

• A confident wrong answer. An agent tells a customer their roof "should last another ten years". It had no basis. Rule: no statements about condition or lifespan, ever.
• Double messaging. The CRM follow-up and the agent follow-up both fire. Switch one off, and test with your own number.
• The estimate has the wrong rate. A rate from an old price list slips in. Keep one price list, dated, and re-paste it each month.
• A hot lead sits in the C pile. The scoring rule penalised "other quotes pending". Review every C weekly for the first month.
• The agent promises a date. It said "we can start Monday" because a template did. Remove date language from templates; use windows and the phrase "subject to confirmation".

Six numbers that show the agent is paying its way

Track five numbers from the first month, compared with the month before if you have them: minutes to first reply, share of leads that reach an inspection, share of estimates that get at least one follow-up, days from estimate to decision, and days from "yes" to deposit. Add a sixth, the one that stops you drifting: the number of messages you had to correct or apologise for. If that is not falling, tighten the rules before adding more steps.

A sensible build order is steps 1 and 6 first, because the first reply and the estimate follow-up give the fastest return and carry the least risk. Then add booking, then the pre-inspection brief, then the contract reminders. Leave the estimate draft and the insurance replies until the others are calm. For a wider map of roofing automation beyond sales, see six workflows worth setting up first, and the AI hub for the rest of the series.

Questions roofers ask about AI agents

What is an AI agent, compared with a chatbot?

A chatbot answers questions. An agent also takes steps in other tools, such as checking a diary, creating a CRM record, sending a text or setting a reminder, and decides what to do next within rules you set. The more steps it can take alone, the more important its limits and approvals become.

Should an agent be allowed to send estimates?

Not without a person approving the numbers. An agent can assemble the estimate from your price list and the inspection notes, and chase it once it is out, but a person should check scope, price and wording before it first goes to the customer.

Can an agent talk to insurance companies for me?

It can draft a summary of damage and a document list for a claim, but contact with the insurer, and anything that states cause of loss or coverage, stays with you or the homeowner. Never let an agent say a claim will be approved.

How much does a roofing AI agent cost?

It varies widely and many vendors do not print prices. A general assistant on a business plan costs per seat, CRM add-ons cost extra, and voice receptionists are often priced per conversation or per minute. Ask for a written price covering your expected volume before you commit.

What if the agent says the wrong thing to a customer?

Limit the damage with rules: no prices, no promises about cover or timing, no safety advice beyond what you wrote. Log every message, review a sample each week, and give the customer a quick route to a person. If it does slip, correct it yourself the same day, in your own words, and add the missing rule so it cannot happen the same way twice.

Further reads

• ChatGPT for Roofing: 10 Prompts for Estimates, Inspections and Warranty — Ten ready prompts for estimates, inspections and warranty.
• Roofers AI: What a Starter Setup Costs for a Small Roofing Company — What a starter setup costs for a small roofing firm.
• AI Automation for Roofing Companies: A Worked Map for a 10-Person Firm — A worked automation map beyond sales, for a ten-person firm.
• Roofing Chatbot Platforms With AI Compared: Qualifying Storm Enquiries — Compare chatbot platforms for qualifying storm enquiries.
• Roofing Software for Small Contractors: CRM or Field Service App With AI? — Choose between a CRM and a field service app.
• CompanyCam Alternatives for Roofers: AI Photo Reports and Checklists — Photo report tools with AI and checklists for roofers.
• Which AI Tools Do Roofers Need? Measurements, Calls, Estimates — Which AI tools help with measurements, calls and estimates.
• Buying AI Lead Generation for Roofing: Pay-Per-Appointment or Retainer? — Compare paid lead sources before an agent ever replies.
• Door-to-Door Roofing Sales: Scripts and Follow-Up Texts Written With AI — A 20-second doorstep script, honest objection replies and a three-text follow-up, with the permit and consent checks to make before anyone knocks.
• Roofing Storm Leads: Triage and Follow Up After Hail With AI — Eight triage questions, a scoring table, consent wording and a five-touch follow-up plan for the weeks after a hail storm.
• AI Agents for Construction Companies: What Works Today — Which agent tasks hold up in a small building firm (inbox triage, document checks, drafts), which claims are still marketing, and the rules for supervising one.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: AccuLynx and CompanyCam public product pages, OpenAI help pages for ChatGPT Work approvals and scheduled tasks, Anthropic documentation for Claude plans, and general roofing sales-process practice. Figures in examples are illustrative.