Define the request before judging the result.
A qualified service inquiry is a genuine request that matches the criteria you and the provider have agreed to use. Those criteria might cover the requested work, job location, contact information, and timing. There is no useful universal shortcut that turns every call into a qualified opportunity.
For this guide, the example framework is a real person asking about a covered service at a location inside the agreed area, with usable contact details or a live conversation. Your actual arrangement needs its own definition.
A person can make a genuine, in-scope request and then decline the price, postpone the project, or choose another business. That outcome alone does not turn the original request into spam.
Check five things.
A genuine request
Is someone seeking the service, or is this a sales pitch, job application, wrong number, or automated submission?
The agreed work
Does the request concern a service included in the partnership? Related work is not necessarily covered work.
The actual location
Is the job inside the defined service area? A phone area code alone does not establish where the job is.
A usable way to respond
Is there a live conversation or contact information that can be used to follow up? Separate invalid details from a person who simply has not answered yet.
A distinct project
Is this a new request or the same person following up about the same work? Decide how repeated contacts are grouped.
Classify examples consistently.
| Example request | Suggested classification | Reason to record |
|---|---|---|
| A real estimate request for covered work inside the area | Potentially qualified | Document the requested work and location; a sale is not required at this stage. |
| The same person calls again about the same estimate | Repeat contact | Link it to the existing project instead of automatically counting another opportunity. |
| Someone asks for work the partner does not offer | Outside scope | Record the actual service requested and check the agreed service boundary. |
| A request comes from outside the agreed area | Geographic mismatch | Record the job location, not a guess based on the phone number. |
| The person does not answer the first return call | Unresolved | One missed connection does not prove fake intent or invalid contact details. |
| A relevant customer declines the estimate | Qualified inquiry, not won | Keep the sales outcome separate from the original request’s fit. |
| A bot message or a supplier trying to sell to you | Not a service inquiry | Record the reason and remove it from the useful-inquiry count. |
Use judgment where records are incomplete. “Unresolved” is more accurate than labeling something bad merely because the business did not manage to reach the person.
Keep a small, useful review log.
A workable log records the date, source, project identifier, service, job location, classification, and outcome. Add a short factual note when something falls outside scope. Avoid collecting information that is not needed to manage the request.
Keep personal contact details in the agreed secure system rather than putting them in public reports, screenshots, or sales materials. A public example can explain what happened without displaying the customer’s name, phone number, or address.
The review is easier when all parties use the same terms. “Qualified” should describe a request’s fit; “quoted,” “won,” and “completed and paid” should describe later outcomes.
Ask for evidence behind quality claims.
Ask a provider how a request was collected and what its quality statement actually measures. “Ready to hire,” “verified,” and “high intent” need explanations. A real submission does not automatically establish urgency, budget, or a decision to book.
The FTC’s 2023 HomeAdvisor order addressed allegations involving lead-source, quality, and conversion claims. The practical lesson is to ask how a claim is supported rather than treat a promotional label as proof.
Source: FTC: substantiation issues in the HomeAdvisor matter
For WebmPros market previews, no established inquiry history is being claimed. Any future property review should distinguish what was observed from what is only expected.
Agree on the review process upfront.
Decide which records support a review, how soon issues should be raised, and who resolves ambiguous cases. Then establish what, if anything, happens to billing. Classifying an inquiry as outside scope does not automatically create a refund or replacement unless the agreement says so.
With a monthly property arrangement, qualification is still useful for understanding performance even when billing is not charged per lead. Track the number and mix of relevant requests instead of judging a month solely by the raw phone count.
Bring the definition into the partnership discussion. Clear service boundaries and an agreed review process prevent more confusion than an impressive-sounding lead label.