The Yelp Lead Qualification Checklist

Why check before you respond at all

Yelp's Request-a-Quote system charges a response fee every time a business replies to a lead. That fee is the same whether the lead turns into a $2,000 job or was someone three states away who fat-fingered their zip code.

The checklist below is the manual version of a filter: five things to glance at before you hit reply, so the response fee you pay is more often attached to a lead worth paying for. None of this requires special tools, just a habit of checking the same things in the same order every time a lead lands.

Is the service area actually yours?

Yelp's location matching isn't perfect. Leads sometimes come in from a zip code or neighborhood you don't cover, especially near the edges of a metro area.

Check the address or zip code in the lead against your actual service radius, not the radius you wish you covered. If a lead is 40 minutes outside your normal range, decide up front whether it's worth the drive before you reply. Businesses that serve a tight radius (a plumber covering three zip codes, say) get burned by this more than businesses that cover a whole metro.

If the lead is out of range and you wouldn't take the job anyway, don't reply. There's no upside to paying the response fee on a job you'd turn down.

Does the service type match what you actually do?

Yelp's category system is broad, and Request-a-Quote leads get routed based on the category the consumer picked, not necessarily the specific service they need. A lead tagged "plumbing" might be someone who needs a new water heater installed, someone with a clogged drain, or someone asking about a full bathroom remodel.

Read the actual request text, not just the category tag. If someone describes a job outside what you offer (structural work when you do repairs only, new construction when you do service calls only), that's a lead to skip regardless of how the category looks.

This is also where a lot of wasted response fees come from: the category matched, but the actual job didn't.

Urgency and spam signals: what to weigh before replying

Real jobs tend to have specific detail. A message that says "water heater stopped heating this morning, need someone today if possible" reads differently than "need a quote." Specificity is a good sign of a real request. Other signals worth weighing in a lead's favor: a specific symptom or problem rather than just a service category, a stated timeframe ("today," "this week," "whenever you have an opening"), contact info the consumer chose to include, and a message length that suggests the person typed with intent.

On the other side, some leads are low-effort or automated in a way that shows in the text. Common spam patterns: a generic one-line message with no details, repeated across many businesses; a request that doesn't match anything your business does in a category that clearly got mis-tagged; a message that reads like a test of the system; or immediate, scripted follow-up asking for personal or payment information before any job is discussed.

None of these signals guarantee a real job or prove spam on their own, and a short message alone isn't proof of spam either — plenty of real customers write two sentences and expect you to ask for details. Treat both lists as patterns to notice, not pass/fail rules.

What to do when a lead is missing information

Plenty of legitimate leads come in incomplete. A consumer might describe the problem but skip their location, or give a timeframe but not what's actually wrong. Don't guess and don't skip the lead outright just because it's thin.

The better move is to ask one direct, specific question in your reply that answers what you actually need to quote the job. "What's the address so I can confirm you're in our service area?" moves the conversation forward without wasting anyone's time.

One compliance note here: if a consumer's phone number shows up in the lead, that number is for you to use for a human callback, not for automated texts or calls. Any tool reading these leads, Yelp Lead AI included, should never auto-text or auto-call a consumer's number directly — replies belong in the Yelp thread, or a real person picks up the phone. This is a general compliance concern under laws like the TCPA, and this checklist is not legal advice; talk to an attorney about what applies to your business specifically.

Running this checklist on every lead, without it eating your day

This five-step check takes maybe thirty seconds once it's a habit: area, service type, urgency, spam signals, missing info. The trouble is volume. A business getting a steady stream of Request-a-Quote leads doing this manually, every time, at 11pm or between jobs, is where owners start skipping steps and paying response fees on leads that were never going to close.

That's the specific gap Yelp Lead AI is built to close: it reads each incoming lead with AI, runs essentially this same checklist, and drafts a reply only for the ones worth responding to, so the response fee lands on leads worth paying for. It doesn't replace judgment on borderline cases, and it doesn't auto-text or auto-call the consumer's phone number directly — replies go into the Yelp thread or get texted to you to review first, depending on plan. For a business getting a handful of leads a week, doing this checklist by hand is completely reasonable. It's the businesses getting leads daily where the manual version starts to slip.