Missed-call text back for roofers: the complete workflow
What should happen between an unanswered call and a booked inspection, how to handle storm days, and where automation should stop.
Industry playbooks
The questions a roofing lead-response workflow should ask before an inspection or callback, in the right order, without overwhelming the homeowner.
A homeowner shouldn't receive ten questions in one message. Qualification works when each answer changes the next question, and the conversation keeps moving toward help.
Start with the reason for contact. Then collect only what the roofing team needs to decide how urgent it is, whether it's a fit, and what happens next.
The exact questions vary by company, but most roofing workflows need a common core:
| What to find out | Why it matters | How to ask |
|---|---|---|
| The job | Decides who calls back, and how fast | "Do you need a repair, a replacement or an inspection?" |
| Urgency and safety | Active water entry and exposed structure come first | "Is water coming in right now?" |
| Property address | Confirms you cover the area | "What's the address of the property?" |
| Name | Lets the team greet them properly | "Could I take your name?" |
| Useful context | Saves time at the inspection | "Where does the problem show, and since when?" |
| Insurance involvement | Some companies handle claims differently | "Is an insurance claim involved?" |
| Preferred time | Starts the booking | "When would suit you for an inspection?" |
Repair, replacement, inspection or something else. Everything else depends on it.
An active leak changes the whole conversation. Flag it, and get a person involved.
Ask for the address before investing more of the homeowner's time.
So the person who calls back can greet them properly.
Where the problem shows, how long it's been happening, whether insurance is involved.
An inspection time, a callback or your booking link.
Stop asking as soon as you know enough for the next step. A homeowner with water coming in needs a callback, not seven questions.
A hot lead isn't simply someone who uses urgent words. Define it with business rules: an active leak, recent storm damage in your area, an in-area homeowner ready for an inspection, or a replacement request with clear timing.
When those conditions appear, the system should mark the lead clearly and alert the owner or the person on duty. It can explain why the lead was flagged, but a person decides how to respond.
A lead-response system shouldn't judge whether a structure is safe, promise insurance cover, quote an exact roof price or confirm a crew time that isn't actually available. Those need an inspection, the actual policy, or real scheduling authority.
A safe response acknowledges the question, explains the limit plainly, captures the details and moves the customer toward the right person or an inspection.
The team's view should sum up the customer, the address, the job, the urgency, the key details, where the conversation stands and the requested next step. It should keep what the customer said separate from anything the system inferred.
| Field | Example |
|---|---|
| Customer | Dan, 14 Elm Street, Riverside |
| Job | Repair: water through the bedroom ceiling since the storm |
| Urgency | High: active drip (customer's words) |
| Insurance | Not mentioned |
| Requested | A call about an inspection |
| Still missing | Roof type, best time to call |
Good qualification is done when the roofer can open the lead and know what to do next within a few seconds.
The same structure works for plumbers, electricians and HVAC companies: swap the first question for the jobs you handle, and keep the rest. Businesses that book appointments rather than visits need different questions altogether; see the salon playbook and the complete guide.
For the workflow around these questions, from the missed call to the booked inspection, read missed-call text back for roofers.
If the next step is already clear, stop. Four or five short questions, one at a time, is the most a homeowner should see before someone calls them.
Usually not by text. Budget conversations go better in person, once the roof has been seen.
Your own rules: for example an active leak, recent storm damage in your area, or a replacement with clear timing. Write them down, so the system and the team agree.
Try it on your own number
Dolittle texts each missed caller by SMS or WhatsApp, asks what they need and lines up the booking. Free 14-day pilot, no setup fee.