Read a defined set of leads

Choose a recent period and review each lead's category, location, contact record, and outcome. Note what the customer asked for and what the business did next.

Use the same criteria for the earlier period. Otherwise a change in how your team labels leads can look like a change in lead quality.

Keep dispute records separate

Record the reason, submission date, and result for each dispute. Platform rules can change, so check the current help documentation before you make a claim about eligibility.

A dispute decision does not explain every lead-quality concern. Keep call handling and category fit in the review.

Assign the next operational check

If the leads fit your service but fail at intake, work on response. If the service or location is wrong, examine account setup. PrimeLSA can help you keep those paths separate.

Working example

A caller asks for a service outside the business's category. Another asks for an eligible service but never receives a callback. Put them in different buckets: category fit and response. If the business considers a platform dispute, retain the current rule and submission record. A single label such as bad lead would hide the operational difference.

  • Use consistent labels across the sampled period.
  • Keep dispute decisions separate from customer-contact outcomes.

Advantage by PrimeLSA can help bring lead quality into the broader account review.

Start guided audit