Roofing Lead Verification

Defining a valid roofing enquiry before the first lead arrives

A valid enquiry is defined in writing before a territory goes live: the ZIPs it covers, the services your company accepts, and — for Pay Per Call — the minimum talk time and the other billable-call criteria. Verification checks an incoming enquiry against that pre-agreed definition rather than against a judgment call made after the fact.

This order matters. If the rules were written only after a dispute came up, every disagreement would turn into a negotiation about what should have counted. Instead, the territory agreement sets the boundaries first — accepted ZIPs, accepted services, minimum talk time where Pay Per Call applies — and every enquiry that follows is checked against those same boundaries, consistently.

What the definition typically covers

• ZIP codes included in the assigned territory
• Services your company has agreed to accept (repair, replacement, inspection and others, since not every roofer accepts every service)
• For Pay Per Call: the agreed minimum talk-time threshold and the full list of billable-call criteria
• What counts as a duplicate of an existing opportunity

Where your company later changes which services it accepts, or a territory's ZIP boundaries are adjusted, the written agreement is the mechanism for updating the definition — verification rules shift with the agreement, not independently of it. A Roofing Market Review is the place to confirm or revise that definition before changes take effect.

Checking contact information, service fit and territorial eligibility

Every enquiry is checked on three dimensions: can the contact actually be reached, does the ZIP fall inside the assigned territory, and does the requested service match what your company has agreed to accept. An enquiry can fail on any one of these and still have been a real, honest contact from a real homeowner — verification is about agreement fit, not honesty.

Contact reachability

For forms and chat, this means a phone number in a plausible, reachable format. For calls, reachability is inherent — a connected call is, by definition, a reachable number — but a call that never connects, goes to voicemail, or is missed is not eligible as a billable Pay Per Call contact regardless of any other factor, because no actual conversation took place.

ZIP-to-territory matching

The property or caller ZIP is matched against the territory's defined ZIP list. Where a ZIP is never captured at all — a caller who hangs up before providing one, or a form submitted without it — the enquiry's territorial fit is unknown rather than confirmed, and it's recorded that way rather than assumed to be in or out of territory.

Service fit

The requested service (repair, replacement, inspection, coating and so on) is checked against the list your company has accepted under the agreement. A homeowner asking about a service your company doesn't perform in that market is a real enquiry, but it isn't eligible under your specific agreement, and it's flagged as a service mismatch rather than delivered as a standard lead.

Separating duplicate enquiries, spam and unrelated sales calls

Beyond fit, every enquiry is also checked against a short exclusion list: is this a duplicate of an existing opportunity, and is this actually a homeowner with a roofing need rather than spam, a vendor pitch, a job applicant, or a wrong number. Each of these gets filtered before, or flagged clearly alongside, delivery, so your team isn't spending estimator time qualifying obvious non-fits.

Duplicates

Duplicate checking matches on phone number and existing open opportunity, the same logic used for attribution reporting. A second call or form from someone who already has an open lead on file is linked to that record instead of generating a new, separately billable one.

Spam, vendors, applicants and wrong numbers

• Spam or automated contact attempts with no real service need described
• Vendors, suppliers or sales calls directed at the roofing company rather than from a homeowner seeking roofing work
• Job applicants calling about employment rather than roofing service
• Wrong numbers — a caller who reached the tracking number by mistake and has no roofing need

For Pay Per Call specifically, these categories are explicitly listed among the non-billable reasons in the written agreement: a call that connects and lasts past the minimum talk time is still not billable if it turns out to be a vendor pitch or a wrong number, because length of call alone was never the qualifying criterion.

Why a valid enquiry is different from a booked or sold roofing job

A verified enquiry has passed the contact, territory, service and duplicate checks. It has not been diagnosed, estimated, scheduled, or sold. Conflating "verified" with "ready to close" sets an expectation the checks were never designed to meet, and it's worth stating plainly so a roofing company isn't disappointed by a verified lead that doesn't turn into an appointment.

Homeowner motivation, budget, competing quotes, and the actual scope of the roofing problem are all outside what any intake check, ours or anyone else's, can determine before your team speaks with the person directly. A homeowner can be perfectly verified — real contact, correct territory, accepted service, not a duplicate — and still decide not to proceed, shop other roofers, or turn out to need work outside what they originally described.

What verification does and doesn't claim

• Does claim: the contact, territory, service and duplicate checks were run and passed
• Does not claim: the homeowner is ready to sign, the job size, or the likelihood of closing
• Does not claim: the roof problem matches what the homeowner described before your team inspects it

Where the Calendar OS booking flow is used, a booked appointment is a stronger signal than a bare verified enquiry — the homeowner chose a specific time from the assigned roofer's open slots, which takes more commitment than answering intake questions. Even then, a booked appointment is a request and a reserved time, not a signed contract, and some booked visits will still end without a sale.

Submitting a quality dispute with useful evidence

A quality dispute is a claim that a specific enquiry — most often a Pay Per Call charge — shouldn't have been counted as billable or valid under the written rules, and it's resolved fastest when it's tied to a specific lead ID and a specific rule, not a general complaint that "the leads have been bad lately."

Useful evidence for a dispute includes the lead or call record ID, the specific billable or eligibility criterion you believe wasn't met (wrong ZIP, wrong service, under the minimum talk time, duplicate, vendor call, wrong number), and any detail from the actual conversation that supports the claim. Where call recording and transcripts are enabled and permitted for a given territory, those records are the most direct evidence available for a Pay Per Call dispute specifically.

Building a disputable case

1. Identify the specific lead or call record ID in question.
2. Name the specific written rule you believe was violated — don't start from "this wasn't a good lead."
3. Pull any available evidence: recording, transcript, form fields, or the territory's ZIP and service list.
4. Submit the dispute referencing the ID and the rule, not a general monthly volume complaint.

A dispute built around "this call only lasted 90 seconds and our agreement sets a 2-minute minimum" is resolvable in minutes against the call log. A dispute built around "this lead didn't turn into a sale" isn't a verification dispute at all, since a no-sale outcome, by itself, doesn't establish that the enquiry was invalid.

Reviewing disputed leads and applying the contracted remedy

A submitted dispute is reconciled against the written rules for that program, using the evidence available for that specific enquiry: the call record and recording or transcript where enabled and permitted, the form or chat transcript, the territory's ZIP and service list, and the duplicate-match history on the contact.

The remedy applied, if the dispute is upheld, is whatever the written agreement specifies for that situation, most commonly for Pay Per Call: the charge is reversed and the prepaid credit is restored. Remedies beyond what's written into the agreement, such as automatic replacement leads for a disputed form or chat enquiry, are not assumed unless they're part of that specific program's terms.

What a review typically confirms or rejects

A HYPOTHETICAL illustration of the mechanics, using assumptions you supply rather than a measured outcome: say your company disputes 3 Pay Per Call charges in a month at $97 each, and 2 are upheld because the call logs show they fell under the agreed minimum talk time. Under a standard Pay Per Call remedy, that would restore $194 in prepaid credit — a model you can run with your own dispute history, not a published average dispute rate.

For roofing companies weighing whether verification rigor is worth it in a given market, a Roofing Market Review is the place to look at dispute history alongside territory inventory, since the two are connected: a market with tighter ZIP boundaries and a clearer accepted-service list tends to produce fewer disputable mismatches in the first place.