Roofing Estimate Follow-Up Texts: Your 14-Day Sequence

Key Takeaways
- Send a roofing estimate follow-up text within an hour of delivering the quote, then on roughly Day 1, 3, 5, 7, 10, and 14. Seven short texts is enough to cover the decision window without nagging.
- Each text should do one job: confirm receipt, offer help, show proof, remove a likely objection, offer options, give an honest scheduling note, then ask permission to close the file.
- Stop the sequence the moment the homeowner replies, and let a person (or a booking flow) take over the conversation.
- Speed matters at the start. Harvard Business Review research found that firms contacting leads within an hour were nearly seven times as likely to qualify them as firms that waited longer.
- Quiet estimates are not dead estimates. A final "should I close your file?" text and a later reactivation message often revive jobs that went silent.
What is roofing estimate follow-up by text?
Roofing estimate follow-up by text is a short series of timed text messages a roofing contractor sends after delivering a replacement quote, to answer questions, remove objections, and get a yes or no. It replaces the single "just checking in" call that most contractors make once and then forget.
Homeowners rarely decide on the spot. They compare two or three bids, talk to a spouse, check an insurance claim, or look at financing. A text sequence keeps your company in front of them while they do that.
When should I send the first text after a roofing estimate?
Send the first text within an hour of delivering the estimate, ideally while the homeowner still has the quote open. The goal is simple: confirm they received it and invite a question. Waiting until tomorrow lets a competitor's follow-up land first.
Harvard Business Review's study of online sales leads looked at lead response, not roofing estimates specifically. Still, the pattern holds for any high-ticket purchase: the first company to engage a person who is actively shopping has the advantage.
What is the full 14-day roofing estimate text sequence?
The sequence below uses seven texts over 14 days. Each one has a single purpose, and the spacing widens as the homeowner goes quiet, so it reads as service and not pressure.
| Day | Purpose | Sample text |
|---|---|---|
| Day 0 (within 1 hour) | Confirm receipt | "Hi [Name], it's [Rep] from [Company]. Your roof estimate is in your email. Any questions, just reply here." |
| Day 1 | Offer a walkthrough | "Hi [Name], want me to walk through the estimate by phone? Takes about 10 minutes. What time works today or tomorrow?" |
| Day 3 | Show proof | "Here's a recent job like yours on [Street/Area]: [photo link]. Happy to answer anything about materials or warranty." |
| Day 5 | Remove an objection | "Quick note: we can help with financing and with insurance paperwork if that's part of your decision. Want details?" |
| Day 7 | Offer options | "If the number is higher than you expected, I can send a second option with different shingles or scope. Want me to?" |
| Day 10 | Honest scheduling note | "Our install calendar is filling for the next few weeks. If you're leaning our way, I can hold a slot. Still interested?" |
| Day 14 | Permission to close | "Hi [Name], I don't want to keep pinging you. Should I close out your estimate, or is there anything holding you back?" |
Adjust the wording to sound like your crew, but keep each message short enough to read in one glance.
What should each text actually say?
Each text should be one or two sentences, carry one question, and sound like a person wrote it. Messages that ask something specific get replies; messages that only say "checking in" get ignored.
Why does Day 1 offer a phone call instead of more information?
A call offer on Day 1 catches homeowners who have questions but will not type them out. Many people want a human to explain scope, warranty, or line items. Offering ten minutes of your time signals confidence and gives them an easy yes.
What should the Day 3 and Day 5 texts cover?
Day 3 gives proof, such as a photo of a finished roof nearby or a short review. Day 5 names the objection you hear most often, usually price, financing, or insurance. Naming it first lets the homeowner raise it without feeling awkward.
Is the Day 10 scheduling text pushy?
The Day 10 text is fair only if it is true. If your crew calendar really is filling, say so and offer to hold a slot. Do not invent scarcity or pressure you cannot back up. Homeowners can tell, and roofing is a trust business.
What if the homeowner replies in the middle of the sequence?
Stop all automated texts the moment the homeowner replies, and switch to a real conversation. A reply means the lead is alive, and a scheduled message that arrives after they have answered looks careless.
Two way texting makes this natural: the homeowner asks about shingle color or start date, and a person or a booking flow answers right away. A tool like InstantReply.ai can pause the remaining messages as soon as a reply comes in and keep the thread ready for your team. If they want a site visit or a signing appointment, send a booking link or offer two specific times.
What do I do when a roofing estimate goes completely quiet?
If the Day 14 text gets no reply, move the lead into a slower reactivation track instead of deleting it. Quiet estimates often come back when a leak shows up, a storm passes through, or a competing bid falls through.
Say a contractor with 40 open estimates revives just three of them at a $15,000 replacement each. That is $45,000 of revenue from messages that cost almost nothing to send. This is an illustrative example, not a benchmark, but it shows why cold lead reactivation is worth scheduling.
A simple cadence is one light check-in at 30 days and another at 60 or 90 days, such as "Hi [Name], we're scheduling spring roof work. Want me to refresh your estimate?" Keep these rare and relevant. InstantReply.ai can queue these later check-ins automatically so no quiet estimate gets forgotten.
What rules keep roofing follow-up texts compliant and welcome?
Only text homeowners who gave you consent to be texted, include a clear way to opt out, and honor stop requests immediately. In the US, business texting is regulated by rules such as the TCPA, and the FCC's guide on unwanted calls and texts is a useful starting point. Confirm the details for your state with a qualified advisor.
Practical habits that help:
- Text during normal hours, not late at night.
- Use the homeowner's name and your company name so the message is clearly from you.
- Cap the sequence at the planned number of messages.
- Never send a text that implies urgency that does not actually exist.
Can I automate roofing estimate follow-up without sounding robotic?
Yes, as long as the messages are short, personal, and stop when the homeowner replies. Automation should handle the timing and the remembering. A person should handle the conversation once it starts.
Roofing CRMs such as JobNimbus, AccuLynx, and Roofr include estimate tools and some automated messaging, and they are a reasonable fit if you already run your pipeline in one of them. If your gap is speed and consistency across calls, texts, email, and WhatsApp, an AI SMS follow up tool such as can send the sequence, answer replies, and book inspections or signing appointments without waiting on your office staff.
The same system can also cover missed calls with a missed call text back and after hours cover, so a homeowner who rings at 7 p.m. does not go to a competitor. Once the job is done, the same channel can send review and referral requests.
How do I know the sequence is working?
Track three numbers: how many estimates get a reply, how many reply-driven conversations turn into booked appointments, and how many estimates close. Compare them month to month and edit the weakest text first.
If replies are low, shorten the messages and ask a clearer question. If replies are high but closes are low, the problem is probably price or scope, so the Day 7 options text deserves more attention. Keep notes on the objections you hear, because they tell you what the next sequence should address.