Roofing - Inquiry handoff - 5 min read
Roofing Estimate Request Handoff: From Form Submission to Next Action
Six steps between form submitted and job booked. Most shops collapse them into one - and that is where the request goes quiet.
Submission is not a handoff
The form came in. The notification pinged. And for a lot of roofing shops, that is where the system ends: everybody assumes the request is "handled."
It is not. Between form submitted and inspection booked, there are six distinct steps, each with its own failure mode. Submission alone does not mean an inspection is booked, a homeowner was reached, or anyone took ownership.
The question that matters is whether the request made it through the first handoff: saved, visible to the right person, with a clear next action. Or did it get lost between steps that everybody assumed somebody else was doing?
Capture comes before every downstream step
The request should be saved before the office tries to notify anyone, sync it to another system, or send an acknowledgement. If a provider or integration has a problem, the homeowner's request should not disappear with it.
For a roofing office, the initial record needs just enough context to start responsibly: homeowner contact details, property ZIP, the kind of help requested, and anything the homeowner chose to share. The form is not an inspection report, and it is not proof of roof damage.
If you are designing the intake itself, use the roofing quote-form checklist to keep it short while capturing the fields that change the next action.
Six steps, six different proofs
These steps often collapse into one vague promise that a lead was "handled." They are six different events, each with its own evidence - and its own way of faking it.
Read the right column as a chain of assumptions. Each one is true only if somebody made it true. The dangerous shops are not the ones failing step 1 - those notice immediately. The dangerous ones are the shops that pass 1 and 2 automatically, then quietly assume 3 through 6 happened because "the system said so."
| Step | What it does | What it does not prove |
|---|---|---|
| 1. Capture | Stores the homeowner's request for the contractor. | That anyone has reviewed it or contacted the homeowner. |
| 2. Acknowledgement | Confirms receipt through a channel the contractor chose. | That an inspection is scheduled or a person will call at a specific time. |
| 3. Notification | Makes the request available to the people who need to act. | That a team member has read it or taken ownership. |
| 4. Ownership | Names the person responsible for the next action. | That the action has already happened. |
| 5. Contact action | Records that a team member initiated a call, text, or email. | That the homeowner answered or that a booking resulted. |
| 6. Booking outcome | Records whether an inspection was booked or not. | That every earlier step worked or that the job will be sold. |
The first handoff needs a named decision-maker
A request can be visible and still leave the office unsure whether the estimator, dispatcher, or office manager should act first. The first handoff should make that choice clear without pretending the later follow-up process is complete.
For example, the office may need to confirm service area, offer an inspection window, or record that the homeowner does not want contact. Those are immediate decisions. The ongoing owner, last action, and next-action routine is covered in the roofing lead follow-up process for small teams.
An attempted contact is not a result
A call, text, or email can be the right next action, but the team should record the action rather than assume it produced a conversation. The homeowner may not answer, may ask for a different time, or may already have signed with the roofer who called first.
Record the attempt plainly, then let the team decide the next step from the homeowner's response or the lack of one. For estimates that later go quiet, see the unsold roofing estimate follow-up playbook.
Booking is a separate outcome, not a side effect of a notification
An inspection is booked only when the contractor and homeowner have actually made that arrangement. A form confirmation, a notification, or a link clicked by the office is not a booking.
Keeping the outcome separate prevents the team from mistaking activity for progress. Six notifications and a calendar reminder can feel like momentum. None is step 6.
Record a clear outcome: Booked, Not Booked, or still in progress with a real next action. A small team does not need a complicated funnel to do this, but it does need a place where those states mean the same thing to everyone.
The first handoff ends where ongoing follow-up begins
Once the office has completed that first review, the request moves into an ongoing process: one owner, a record of what happened, and a specific next action until it is booked, closed, or intentionally paused. That process is distinct from the initial form handoff.
For a small shared view, download the free roofing follow-up tracker. For the routine that follows the first handoff, read the roofing lead follow-up process. During a storm surge, use the storm inquiry handoff guide to preserve the request context without turning an intake note into a diagnosis.
Where Kaldwick fits
Kaldwick gives a roofing team 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.
A configured acknowledgement can be one step in the flow. Kaldwick does not make the calls or decide what the team does next. The six steps stay yours; Kaldwick keeps the record of them visible.
Frequently asked questions
What should happen after a homeowner submits a roofing estimate request?
Capture the request, review its basic context, name one owner, and write a specific next action. Record a contact attempt and a booked inspection as separate outcomes rather than assuming either from a notification.
Does a confirmation message mean a roofing inspection is booked?
No. A confirmation can acknowledge receipt of a request. An inspection is booked only when the contractor and homeowner have actually agreed on the appointment.
What is the difference between a roofing lead notification and follow-up?
A notification makes the request visible to the team. Follow-up is the human work of naming the owner, deciding the next action, initiating contact through an appropriate channel, and recording what happened.
How should a roofing office track estimate requests after submission?
For the first handoff, preserve the request details and record the immediate decision or action. For the ongoing process after that, keep one owner, the last action, the next action, and a clear status. Keep booking separate from an attempted call or message.