Text-back is one possible response channel after an eligible missed call. The company still needs clear consent, disclosure, opt-out, routing and escalation rules for its actual use case.
Start by estimating the potential gap with the roofing missed-call revenue calculator.
The six-part workflow
- Detect one eligible missed call. Deduplicate repeat attempts and exclude numbers or call types that should not enter the flow.
- Acknowledge the context. Identify the roofing company and explain that the call was missed.
- Ask one useful first question. Separate a new roofing need, current customer request and other contact.
- Qualify progressively. Collect the service address, project type, service-area fit and urgency in a natural order.
- Offer an approved next step. Present a real appointment option or create a clear callback request.
- Record the outcome. Mark no response, customer request, unqualified contact, qualified opportunity, appointment or staff handoff.
Example opening—not a universal script
“Hi, this is [Roofing Company]. Sorry we missed your call. Are you contacting us about a repair, replacement, inspection or an existing project?”
The actual message should match the company’s brand, services and approved compliance language. Avoid pretending the text is a live employee when it is automated.
Keep the first exchange short
Do not send a long intake form in the first text. Ask for the minimum information needed to decide the next question. The roofing qualification guide shows how to prioritize fields.
Build explicit exceptions
- A caller says STOP or asks not to receive messages.
- The number cannot receive texts.
- The caller is an existing customer with an active issue.
- The property is outside the service area.
- The caller describes a possible safety emergency.
- The system is uncertain or the caller asks for a person.
Measure the text-back honestly
Track unique calls entering the flow, delivered messages, two-way responses, qualified opportunities, booked appointments, staff handoffs and verified outcomes. Delivery is not engagement; engagement is not qualification; qualification is not revenue.
Compliance belongs in the design
Automated texting rules can vary by message purpose, consent, location and workflow. Use appropriate legal guidance and configure identification, opt-out handling, records and retention before launch.
Plan the after-hours version
Storms and evening calls need different escalation and scheduling rules.
A response is not the end of the workflow
Consider a homeowner who replies, “I need a replacement quote.” The next useful step is to confirm the service area and property need, then offer an approved inspection option or named callback. A message marked delivered is not proof that this happened.
| Observed outcome | Next action |
|---|---|
| No response | Keep the disposition visible; follow only the company's approved contact rules. |
| Existing project question | Route to service staff and remove it from the new-lead count. |
| Qualified request | Offer verified availability or assign a callback owner. |
| Requested time | Confirm calendar acceptance before counting an inspection. |
Review a small sample of records with the office each week. Ask which callers still lack a next step and who owns each one.
Check your process against a sample scorecard
Review the example and worksheet, then calculate a scenario from your own call records.
View the free missed-call scorecard · Use the calculator
Request a free missed-call audit