Roofing Lead Qualification

Agree the roofing enquiries your company can accept

Qualification starts with a written list, agreed in advance, of the services and ZIPs your company accepts — the intake can't apply a rule nobody wrote down, so the first step in any qualification program is defining that list clearly rather than relying on a general sense of "roofing work we do."

Most roofing companies accept a narrower list than their marketing suggests: a company that does full residential replacements may not want small gutter repairs, or a commercial-focused crew may not want single-family residential calls at all. Writing the accepted-services list down, and keeping it current as your capacity changes, is what the qualification rules are actually checked against.

Think through a few roofing situations before you sign off on the list. A homeowner with a single missing ridge cap after a windy night is a repair call. A landlord asking about a full tear-off on a duplex may be residential, multifamily, or both, depending on how you define them. A church facilities volunteer asking about a flat section over a fellowship hall raises a decision-maker question as well as a service question. Writing your answer to each case ahead of time means the intake does not have to guess, your office staff do not have to argue about it later, and any dispute is settled by reading the agreement rather than by memory. If a case truly falls in between, note it as reviewed by hand instead of forcing it into yes or no.

A short worked case shows why order matters. Suppose a caller in a ZIP you accept asks about gutter guards, which you did not list, and also mentions a soft spot near the chimney. The first request fails the service check, but the second may pass, so the record should keep both facts and let the written rule decide. Suppose instead the caller is a tenant who wants a landlord to fix a leak. The roofing problem is real, yet the decision-maker check is not met until the owner is reached. Writing these cases down keeps your team consistent from week to week.

• Accepted services: the specific roof types and job types your team wants routed, not a general "roofing" category.
• Accepted ZIPs: the exact territory boundary your agreement defines, including any carve-outs or overlap rules.
• Excluded work: anything explicitly out of scope (for example, a service you don't perform, or a property type you don't service) so it can be flagged rather than routed.

Keeping the list current matters more than getting it perfect on day one

A company's accepted list can and should change as crews, specialties, or capacity change. An out-of-date accepted-services list is one of the most common reasons a lead looks "unqualified" when the real issue is that the list no longer reflects what the company actually wants.

Ask about the project, address, urgency and decision-maker role

Each channel — call, form, or website chat — asks for the same core facts in a form suited to that channel: name, phone, ZIP or town, the service needed, a description of the problem, urgency, and a preferred contact time. Chat also supports a photo upload so a homeowner can share what they're seeing.

• Project: what the homeowner described needing, in their own words where possible, plus the service category it's matched to.
• Address or ZIP/town: used to match the enquiry to a territory, not to publish or share beyond the routing and delivery process.
• Urgency: the homeowner's stated urgency, which also drives follow-up timing separately from qualification.
• Decision-maker role: whether the caller is the homeowner or property owner, or someone else (tenant, family member, property manager) without authority to approve work.

AI chat has specific limits here

Where an AI chat handles the conversation, it is built to never invent prices, appointment times, warranties, or a specific roofer's name, and it never offers an instant estimate. Its job is to collect the fields above accurately, not to sound like it's already qualified the job technically. Staff can switch a chat into human mode at any point, which shows the homeowner a message that a person has taken over and the AI is paused, and staff can then continue by chat or by text.

Apply geography and service-fit rules consistently

Once the core facts are captured, the ZIP is matched against the territory map and the requested service is matched against the accepted-services list — the same two checks run the same way on every enquiry in that territory, so two homeowners with similar requests get evaluated by identical logic.

Pay-per-call programs layer additional billable conditions on top of this base qualification: the call has to have connected to your company, met the agreed minimum talk time, and come from a caller who isn't spam, a vendor, a job applicant, or a wrong number, and the enquiry can't duplicate an opportunity your company already has on record. Every call lists every reason it was or was not billable, not a single pass/fail flag.

Long calls aren't a substitute for these checks

A call lasting several minutes is not, by itself, qualification — a long conversation with a vendor, a wrong number who stayed on the line out of politeness, or someone outside your territory still fails the relevant checks regardless of talk time. Duration is one input among several, not a stand-in for the others.

Handle incomplete, uncertain or exception enquiries

Leads are saved even when details are missing — a dropped call, an unanswered form field, or a chat the homeowner abandoned before finishing all still produce a record, with whatever was captured recorded honestly rather than filled in with a guess.

1. Missing phone number: the lead is saved with whatever contact method exists (email, chat thread) and flagged so your team knows a callback number wasn't captured.
2. Missing or unclear ZIP: territory fit is marked unknown rather than assumed in your favor or against it, and the record is flagged for manual review.
3. Service outside the accepted list but close to it: flagged as an exception rather than silently dropped or silently routed, so a human can decide whether it's worth an exception.
4. Uncertain decision-maker role: noted in the record so your team can ask directly on the first call rather than assuming.

Duplicate handling

The same phone number or the same opportunity contacting the territory again is de-duplicated against existing records rather than treated as two separate new leads, which protects your team from being billed or distracted twice for the same homeowner's ongoing conversation.

Exceptions are not simply discarded. They're flagged with the reason, so your team (or a reviewer on the program side, depending on your agreement) can make a specific decision rather than relying on a blanket rule that doesn't fit every situation.

Deliver the qualification evidence with the lead

Every delivered lead carries the specific facts that drove its qualification outcome, not just a single qualified/unqualified label — your team can see what matched, what didn't, and what was unknown, the same way a Pay Per Call record lists every reason a call was or wasn't billable.

Delivery runs into your company's existing CRM through a generic webhook, Zapier, or a native connection where one is actually built and tested, with email or SMS as a fallback. Every delivery attempt carries a status — queued, sent, delivered, or failed — with retries and a fallback alert so a failed push never silently loses the lead.

• Where recording is enabled and permitted, call recordings or transcripts are attached to support a later review or dispute.
• The delivered record includes territory match status, service match status, and decision-maker information as captured.
• Exception flags (unknown ZIP, service outside list, missing contact) travel with the lead rather than being silently resolved before delivery.

Disputes are reconciled against written rules

If your team believes a billed or routed lead was misclassified, the dispute is reviewed against the written qualification rules in your agreement, along with recordings or transcripts where available and intake data on file — not a fresh subjective judgment about whether the lead "felt" qualified.

Review quality feedback without confusing interest with a sale

Qualification measures fit against your written criteria at the moment the enquiry came in — it is not a prediction of whether the homeowner will ultimately sign a contract, have the budget, or qualify for insurance coverage. Those outcomes depend on your estimate, your team's follow-up, and the homeowner's own situation, none of which the intake can know in advance.

Reviewing quality feedback over time — which exceptions kept recurring, which service categories produced the most territory mismatches, which decision-maker roles turned into real appointments — is useful for tightening your accepted-services list or territory boundary, but it should be read as operational feedback, not as a scorecard graded against a guaranteed conversion rate.

A HYPOTHETICAL example, using assumptions you set rather than a published figure: say your territory receives 60 enquiries in a month, and after qualification checks, 45 match your territory and accepted services cleanly, 10 are flagged as exceptions needing a manual look, and 5 fail outright (wrong territory, unreachable, duplicate). If your team closes an estimated 20% of the cleanly qualified group, that would model out to roughly 9 jobs for the month — a labeled assumption using your own close rate, not a guarantee.