Missed-call text back for roofers: the complete workflow

Why the first few minutes matter

A homeowner who calls about a leak, storm damage or a replacement is often contacting more than one roofer. If the call reaches voicemail while the crew is up on a roof, the job can be gone before anyone sees the missed call.

A missed-call text back closes that gap. It doesn't replace the roofer. It acknowledges the call, learns why the person called, and creates a clear next step while the need is still fresh.

Storms make it harder. After a big one, calls arrive in bursts, often from people with water coming through a ceiling. A text back answers everyone at once and helps the office see who needs help first.

The six-stage workflow

A dependable workflow is more than an automatic "sorry we missed you" text. Each stage needs a clear input, a clear output and a plan for when something goes wrong.

1. Spot the missed call

   Catch calls that ring out, hit a busy line or fail, without texting people the team actually spoke to.

2. Send a short branded text

   Name the roofing company, acknowledge the call, and ask whether they need a repair, a replacement or an inspection.

3. Ask one question at a time

   Each answer decides the next question. Nobody should receive a questionnaire.

4. Capture what the team needs

   The job, how urgent it is, the property address, a contact name and any useful details, such as where the leak shows.

5. Line up the next step

   Request an inspection time or a callback, and put it in front of the team.

6. Stop, or hand over

   Respect STOP immediately, and pass unusual or urgent situations to a person straight away.

What the conversation should sound like

The strongest opening is specific and easy to answer: name the roofing company, acknowledge the missed call, and ask what kind of help they need. The next question should depend on the answer.

Avoid pretending the system is a person, repeating the same question in different words, or promising a price before anyone has seen the roof. Useful automation reduces uncertainty; it shouldn't manufacture certainty.

Storm days and busy seasons

After a storm, the phone can ring all day. A text back can't send a crew out faster, but it can make sure every caller hears back, and that the office sees urgent cases first.

• Put active leaks and safety worries at the top of the list, and alert the owner straight away.
• Be honest about timing. If inspections are booked days ahead, say a person will confirm, and don't promise a time.
• Expect insurance questions, and leave them to a person. Never promise what a policy covers.
• Watch for repeat callers. The same homeowner may call three times; keep it to one conversation.

What the roofer needs to see

A text thread on its own isn't enough. The team needs a short brief: who called, what they need, where the property is, how urgent it looks, what's still missing, whether an inspection was requested, and when a person should take over.

That brief stops the homeowner having to repeat everything, and gives the roofer a reason to call back now. In Dolittle, it appears in your client workspace, and urgent cases also send an alert to the owner.

Questions the agent must not answer

• Prices, before anyone has seen the roof
• Whether insurance will pay
• Whether a roof or ceiling is safe
• Arrival times the crew can't promise

A good response acknowledges the question, says plainly that a person will answer it, captures the details and moves the homeowner toward an inspection. The full list of what to ask is in our roofing lead qualification checklist.

How to judge a pilot

Test the real path: place a call, let it ring out, receive the text, reply naturally, request an inspection, send STOP and check the lead in the workspace. Then repeat it with incomplete answers, out-of-area requests and a failed send. Our end-to-end testing guide lists every check.

Revenue is the outcome to watch over a season, not a promise any software can make.