Roofing Lead Follow-Up: A Simple Process for Small Teams

Roofing lead follow-up is a handoff process, not a message cadence

A small roofing office can lose track of a good inquiry without anybody deliberately ignoring it. A form is forwarded to an estimator. A voicemail is noted while the office is booking inspections. A homeowner asks for a call next month. Each person believes the next step belongs to someone else.

The fix is not a larger sequence of texts or more reminders by default. Before choosing a channel or date, make the work visible: what came in, what happened last, who owns it now, and what should happen next.

Separate a missed handoff from an intentional pause

Not every quiet roofing request needs another call. A homeowner may be waiting for insurance, deciding on timing, outside your service area, or simply not ready. An intentional pause has a documented reason and a future action or a clear close-out. A missed handoff has neither.

That distinction protects both sides. The team stops treating every old record as a sales opportunity, and the homeowner does not receive a generic message just because a timestamp is old.

• Intentional pause: a real reason, a named owner, and a specific date or trigger to revisit.
• Active work: an action is currently owed, such as returning a call, clarifying scope, or offering inspection availability.
• Closed work: booked, not a fit, completed elsewhere, or do-not-contact — recorded plainly rather than left ambiguous.
• Missed handoff: the last action is unclear, the next action is blank, or ownership is assumed rather than named.

Use four fields before adding software

A workable follow-up system does not start with a large pipeline. It starts with four fields every person can understand. They work in a shared inbox, a spreadsheet, or an existing CRM.

Give every request one owner

Ownership does not mean the same person must handle every task. An office manager can own the next callback while an estimator owns the inspection. What matters is that the record makes the current responsibility visible until the handoff is complete.

Avoid assigning ownership to a department or a shared mailbox. 'Office' and 'sales' do not answer the question a busy teammate needs answered: who is doing the next thing?

Write a real next action

'Follow up' is a reminder, not a plan. A real next action carries enough information that another person could perform it: the channel the homeowner prefers, the reason for the contact, and a sensible time or trigger.

For example: 'Email the revised repair scope after the photos arrive.' Or: 'Call Friday morning; homeowner asked to revisit after adjuster meeting.' Those notes are more useful than a generic sequence because they preserve what the homeowner actually said.

Use only channels the homeowner has agreed to use and honor do-not-contact requests. A legitimate follow-up respects the existing relationship; it does not manufacture urgency or repeatedly chase silence.

Run a short daily review instead of a monthly cleanup

Set one short review point each day. Look at the requests marked Needs Action and In Progress. For each one, confirm that the owner, last action, and next action are still true. Close records that are clearly not moving rather than allowing them to become a pile of false opportunities.

This is different from reopening every estimate once a quarter. When an estimate truly goes quiet, use the documented context to decide whether a light, relevant follow-up makes sense. The unsold roofing estimate playbook covers that later decision.

Storm volume changes the call order, not the handoff rule

After hail or wind, a roofing office may need to sort active leaks, core-area work, and inspection requests before deciding the first callback. That affects priority, but it does not remove the basic rule: every request still needs an owner and next action.

Use the post-storm roofing triage guide to add urgency, ZIP, and scope to the call-order decision. Then return the request to the same visible follow-up routine so it does not disappear after the first rush.

Start with the system your team will actually use

A spreadsheet is enough for some small teams. An existing CRM is enough for others. The test is operational, not ideological: can the team see every unfinished request and answer who owns the next action? If yes, improve the routine before adding another platform.

Download the free roofing follow-up tracker if you need a small shared board to begin. It contains fictional examples and the four fields above. It does not send messages, book inspections, or replace the tools you already use.

Where Kaldwick fits

Kaldwick gives a contractor a shareable quote link and a Needs Action work list for incoming requests. The team can initiate a call, text, or email action from that list and record a booking outcome separately. Its role is to make the next work visible at the inquiry handoff.

It is not a guarantee that a homeowner replies, an inspection is booked, or a job closes. It also does not replace a full roofing CRM, estimating system, dispatch process, or the human judgment behind a relevant follow-up.

Frequently asked questions