What counts as a qualified contractor lead?

A homeowner calls a roofer about a leaking roof. The property is inside the agreed territory, the company handles that type of repair, and the caller is asking for help. The roofer later loses the job on price.

Was the lead qualified? It may have been. Losing the sale does not, by itself, mean the enquiry failed the qualification rules.

Now change one detail: the property is outside the agreed service area. The caller may still need a roofer, but the enquiry should fail a location rule that was part of the agreement.

A qualified contractor lead is an enquiry that meets the service, location, intent, and other screening criteria agreed for the channel. Qualification describes the opportunity at handoff. It does not guarantee a booking, a profitable project, or payment.

Define the service more precisely than the trade

“Plumbing lead” is too broad if your crew handles emergency repairs but does not install fixtures on new construction. “Roofing lead” may include repairs, replacements, inspections, or work on buildings you do not serve.

Write down the included services and the exclusions. If residential and commercial work have different requirements, say so. If you accept replacement enquiries but not maintenance, that distinction belongs in the screening rules.

Some details will remain unknown until an inspection. Separate what a provider can reasonably establish during intake from what your estimator must assess later. A lead should not be described as a confirmed replacement project merely because the caller suspects the system needs replacing.

Make the territory unambiguous

A metro name is not always a usable service boundary. Agree how location is checked: ZIP codes, named municipalities, a defined radius, or another documented boundary.

Use the property's location for service eligibility, rather than assuming a telephone area code tells you where work is needed. Also agree how to handle an enquiry with an incomplete address and who resolves a boundary case.

If your availability changes, tell the provider. A territory you technically serve can still be impractical when crews are unavailable, but a temporary capacity problem is different from an out-of-area lead.

Separate mandatory screening from helpful context

A useful intake record distinguishes pass/fail information from details that help your team prepare.

Field	Purpose	Example rule to agree
Requested service	Confirm service fit	Repair type must be in the included service list
Property location	Confirm territory fit	Property must fall inside the documented boundary
Reason for contact	Establish genuine intent	Caller is asking about relevant work, not selling something
Contact or connection details	Enable the agreed handoff	Specify whether a connected call, callback number, or completed form is required
Previous enquiry	Apply duplicate rules	Define the person, job, and time window used to identify a duplicate
Urgency	Support routing	Clarify whether urgency gates qualification or is contextual information
Property type and project details	Prepare the operator	Mark optional fields explicitly

This is a checklist for agreeing terms, not a universal industry standard. If budget, authority to approve work, or project timing must be verified for your channel, write that requirement down. Do not assume it is included in the word “qualified.”

Call duration cannot establish quality by itself

A lengthy conversation can concern the wrong service. A short call can contain a clear, relevant request. If a provider uses a minimum connected duration, ask when the timer begins and what else must be established.

Does time in a greeting or hold queue count? Does a transferred call need to reach your team? What happens if the connection drops before the required questions are answered?

Those details determine what the duration rule measures. They should be settled before there is a disputed call, rather than inferred afterward from the length of a recording.

Test the definition against awkward examples

Use sample scenarios during provider evaluation:

Hypothetical enquiry	How to assess it
In-area customer requests included work, then declines the quote	Could qualify; the sales outcome is separate
Caller wants an excluded service	Fails the agreed service test
Same person asks again about the same job	Apply the agreed duplicate window and identity rule
Caller only asks for a price	Check the intent rule; comparing prices alone need not make an enquiry invalid
Operator cannot take more work this week	Review capacity obligations; this is not automatically a qualification failure
Wrong number or vendor sales pitch	Should fail a genuine-enquiry requirement

Ask the provider to explain the evidence behind each decision. If you cannot apply the definition consistently to these cases, the policy needs more detail.

Preserve enough evidence to review a disagreement

For each lead, use a reference ID, timestamp, channel, relevant screening answers, location information, and qualification outcome. Where recordings are lawfully collected and available under the agreement, they may help review the interaction. Otherwise, use the records that actually exist.

Your team should also record the sales outcome separately: reached, estimate arranged, booked, completed, paid, or lost. That allows you to distinguish screening failures from missed follow-up, pricing objections, and capacity problems.

Before signing, check the dispute deadline, required evidence, decision process, and remedy. A per-lead refund and an adjustment to delivered volume in a monthly package have different consequences. Read the actual terms rather than assuming both mean “credit.”

Check the policy before checking the forecast

CallerBridge publishes its qualification policy, including screening questions and exclusions. Use that page and the market agreement for the actual rules; the worksheet above is an evaluation aid.

For a fixed monthly channel, lead quality still matters even when individual enquiries are not billed separately. It affects the delivered volume you can use and the downstream results your team can achieve.

Open the policy beside the market you are considering. Confirm the included services, territory, mandatory questions, duplicate treatment, and dispute remedy before evaluating a volume forecast. A forecast becomes more useful once everyone agrees what it is counting.