Roofing Lead Conversion System

Map the roofing lead journey from enquiry to first appointment

The journey runs through a fixed sequence of observable stages: the enquiry is captured, it's matched to a territory and delivered to your CRM, your team or the network's follow-up touches the contact, and — where applicable — an appointment is requested or booked. Mapping it this way lets you see exactly where a given lead sits without guessing.

The stages, in order

• Captured — a call connects to a tracking number, a form is submitted, or a chat produces a saved record, even if some fields are missing.
• Qualified — the lead is matched to your accepted services and ZIP territory and checked for duplicates against existing opportunities.
• Engaged — a missed-call text, a follow-up touch, or a chat handoff reaches the homeowner after the initial contact.
• Appointment requested or booked — the homeowner picks a time from the assigned roofer's available calendar slots, or requests a callback.
• Delivered — the lead record, with whatever stage it reached, is pushed to your CRM with a delivery status.

Each stage produces a timestamp and an event type in the lead record. A call that rang and went unanswered looks different in the record from a call that connected for four minutes, and both look different from a web form submitted at 11 p.m. with no phone contact at all. The map exists so your team isn't relying on memory or a verbal summary to know which stage a specific contact reached.

Assign a clear owner to each supported response stage

Every stage in the journey has one responsible party — either the network's automated systems or your team — and mixing that up is a common cause of dropped leads. A clear ownership map removes the ambiguity of "I thought someone else was handling that."

Who owns what

The one stage your team should never assume is covered automatically is anything after delivery. The system does not call your customer back on your behalf after handoff, does not chase a stalled proposal, and does not know whether your estimator showed up. That responsibility sits with your team, and the review sheet later on this page gives you a way to log it.

Identify where contacts stall, fail or need a different next step

Contacts stall for specific, identifiable reasons at each stage, and naming the reason is more useful than a generic "lead went cold" label. The lead record keeps enough detail to distinguish, for example, a homeowner who never answered a follow-up text from one who explicitly opted out.

Common stall points

• Call never connected — rang through to voicemail, or the homeowner hung up before the AI or a staff member could respond.
• Missed-call text sent but no reply — the one automated text per unanswered call went out, but the homeowner didn't respond, and no further text goes out unless they reply or a follow-up program is enrolled.
• Chat abandoned mid-conversation — the homeowner started but didn't finish providing name, phone, ZIP, service, problem, urgency or preferred time; whatever was captured is still saved.
• Opted out — the number is on the STOP list; it is not and will not be texted again on that number.
• Qualification failed — service not in your accepted list, ZIP outside your territory, or the contact is a duplicate of an existing opportunity.
• No appointment slot chosen — the homeowner was shown available times but didn't book; a callback request may still exist.
• Delivered but no CRM confirmation — the push to your CRM reported queued or failed status rather than delivered.

A long phone call is sometimes mistaken for a qualified lead. It isn't, on its own — call length tells you engagement, not whether the caller is a homeowner or authorized decision-maker, whether the ZIP is in your territory, or whether the service is one you accept. Qualification is a separate check, and a stall at that step is recorded with its specific reason, not folded into a vague "unqualified" bucket.

Coordinate answering, messages, qualification and booking

Coordination means each stage hands off cleanly to the next without duplicating work or leaving a contact in limbo. In practice this looks like a fixed order: answer or capture, then qualify, then engage with follow-up or chat handoff, then offer booking, then deliver — with every step logged against the same lead record rather than scattered across separate tools.

How the pieces connect

After a tracked call goes unanswered, the system can send the one "sorry we missed you" text tied to that specific call, checked against an idempotency key so it never sends twice for the same call, and checked against the STOP list before every send. If the homeowner replies, staff can take the conversation over — the text itself is a response to the missed call, not a marketing message, and it runs under the network's registered A2P texting campaign.

Website chat runs in parallel to phone and form capture, collecting the same core fields — name, phone, ZIP or town, service, problem, urgency, preferred time — and allowing a photo upload. The chat never invents a price, an appointment time, a warranty, or a roofer's name, and an incomplete chat is still saved as a lead rather than discarded. Staff can switch any chat to human mode, after which the chat tells the homeowner a person has taken over and the AI is paused.

Once a lead clears the ZIP and service checks and is de-duplicated against existing opportunities, homeowner follow-up enrolls with timing based on urgency — about five minutes for an emergency, thirty minutes for high urgency, three hours otherwise — paired with problem-specific safety guidance, such as never climbing on the roof to check damage. Email sequences only run if the person opted in, and texting always stops on STOP or any other opt-out. The intended stop condition is the homeowner booking or your team marking progress, configured per program.

Appointment booking draws on Calendar OS as the single source of open times, showing the homeowner three to six real choices for their ZIP and service from your calendar, with a live Google Calendar check so already-filled times don't appear, and a rate-limited, atomic reservation so two homeowners can't grab the same slot. None of this includes automated reminders, crew scheduling, dispatch, or ERP functions — those stay outside the system's scope.

Measure stage progression using events the platform can observe

Measurement is limited to events the platform itself can see: a call connecting, a text sending, a chat completing or being abandoned, a lead qualifying, an appointment booking, and a CRM delivery status. Anything that happens after delivery — whether your estimator called back, whether a proposal went out, whether the job sold — is outside the platform's visibility unless you report it back.

What gets reported, and what doesn't

This split matters because a conversion report built only on platform-observable events will understate your actual close rate if a chunk of your sales happen entirely inside your own CRM and sales process, with no outcome data ever flowing back. The honest version of a conversion report says, plainly, which numbers are measured and which are unavailable — rather than filling the gap with an estimate presented as fact.

Agree a conversion improvement plan with the roofer's team

An improvement plan starts from the stage data that actually exists, names the most common stall point for your account, and proposes one specific operational change your team controls — not a platform promise of a better conversion rate. This keeps the conversation grounded in what each side can actually do.

What a plan typically covers

1. Review the last period's stage counts: captured, qualified, engaged, appointment requested or booked, delivered.
2. Identify the single stage with the largest drop-off relative to the stage before it.
3. Separate stalls your team controls (callback speed, calendar availability, staff follow-through) from ones that are platform-side (chat completion rate, text opt-outs).
4. Agree one specific, testable change for the next period — for example, keeping more open calendar slots visible, or confirming your forwarding number stays verified.
5. Set a date to review whether the change moved the specific stage it targeted.

Lead conversion review sheet

Use this worksheet internally, or bring it to a Roofing Market Review call, to work through a specific stretch of leads stage by stage.

• Stage definitions: write out, in your own words, what counts as captured, qualified, engaged, appointment-booked and delivered for your account.
• Unique-lead counts: how many distinct leads reached each stage in the period you're reviewing (de-duplicated, not counting repeat contacts from the same opportunity).
• Timestamps: when each stage was reached, so you can see gaps in response time.
• Assigned owner: who on your team (or which network system) was responsible for the next action at each stage.
• Failure reason: the specific, recorded reason a contact stalled, not a general label.
• Available evidence: call recording, chat transcript, or delivery log you can check against a stall.
• One proposed operational change: a single, testable adjustment for the next period.

Most accounts find the improvement conversation is more productive when it is scheduled on a cadence — monthly for an active territory, less often for a slower one — rather than only after a complaint about lead quality. A recurring review turns stage data into a habit your team checks, instead of a one-time audit that gets filed away.