The short version: In July 2024, Google replaced manual LSA dispute filing with an automated machine-learning credit system. At the same time, Google removed two lead categories from credit eligibility: "job type not serviced" (callers asking for services you don't offer) and "geo not serviced" (callers outside your service area). These are now pure losses on every contractor LSA invoice with no path to a refund. The exact share of leads that fall into these categories varies significantly by trade, by service area breadth, and by how recently your LSA profile was configured. This playbook shows you how to measure your own uncreditable lead rate and prevent it at the source through service area surgery, job type audit, ad copy filtering, and phone triage.
What Changed in July 2024 (Brief Recap)
Google rolled out automated LSA lead credits between July and August 2024. The manual "dispute this lead" button in the LSA dashboard was replaced with a "Rate this lead" button. Instead of contractors submitting dispute reasons and waiting for Google to review them individually, an AI system now reviews every charged lead within 72 hours and applies credits automatically when warranted.
For a full explainer of how the automated credit system works (the four stages, the rate-lead workflow, the 8-step credit maximization system), see BGM's existing guide at Why LSA Leads Get Disputed (And How to Get Credits). This article focuses on the part that guide does NOT cover: the two categories Google has explicitly excluded from auto-crediting.
If a lead falls into "job type not serviced" or "geo not serviced," you pay for it with no recourse to a credit, regardless of how clearly invalid it feels to you. The only path to reducing this cost is prevention.
The Two Uncreditable Categories Explained
1. "Job type not serviced"
A "job type not serviced" lead is a caller who asked for a specific service that you have enabled in your LSA profile but cannot or do not want to deliver. The keyword is "enabled." Google's position is that you told the platform you offered the service, so it routed a qualified caller to you in good faith.
Concrete examples:
- You're an HVAC contractor. Your profile has "Duct cleaning" enabled because the LSA setup wizard suggested it during onboarding. A homeowner calls for duct cleaning. You don't do duct cleaning, you sub it out at break-even, or you do it but the margin is so thin you'd rather not. That charge is yours, no credit possible.
- You're a plumber. Your profile has "Sewer line repair" enabled but you don't actually trench. The caller wants a sewer line dug up. Your charge, no credit.
- You're a roofer. Your profile has "Gutter installation" enabled because Google's category tree suggested it. The caller wants gutters only, no roof. Your charge, no credit.
Before July 2024, contractors could dispute these as "job type not serviced" and routinely get credits. Now Google's stance is essentially: "You told us you offered this. If you don't, fix your profile."
2. "Geo not serviced"
A "geo not serviced" lead is a caller located inside your declared LSA service area but in a zip code, neighborhood, or sub-region that you can't profitably serve in practice. Google's position mirrors the job-type logic: you declared the area as serviceable, so the platform routed you the lead in good faith.
Concrete examples:
- You're an HVAC contractor based in Dallas with "Dallas, TX" selected as one of your 20 service areas. A homeowner in northeast Dallas (35 miles from your shop) calls. Your trucks are at the south end of the city all day. By the time you'd drive up, the install profit is gone. Your charge, no credit.
- You're a plumber with both "Houston" and "Sugar Land" selected. A caller in Sugar Land wants a $200 hose-bib repair on a Sunday. Your minimum dispatch is $350 in that direction. Your charge, no credit.
- You're a roofer with 7 zip codes selected and you removed one of them mid-month after it underperformed. A caller from the removed zip still gets you for the next 24-48 hours while Google updates routing. Your charges during the lag, no credits.
The structural problem: Google's LSA service area cannot be set as a radius. You must pick cities, postal codes, or area types from Google's list. The maximum is 20 service areas total (per Google Local Services Help: Edit your industries, service areas, and job types). Contractors who select large cities (which contain many zip codes) end up paying for "geo not serviced" leads from the parts of the city they can't actually cover.
Calculating What Uncreditable Leads Are Costing You
No public source publishes a verified uncreditable-rate benchmark, and the rate varies significantly by trade and profile configuration. Rather than guess at industry averages, the more useful exercise is to calculate your own exposure using your real LSA spend.
The math is straightforward: (Monthly LSA spend ÷ your median cost per lead) × your uncreditable rate × your median cost per lead = monthly loss. Median LSA cost per lead for home services trades sits around $38 across 24 trades, ranging from $22 (handyman) to $85 (water damage), per the aggregated public benchmarks at LocaliQ, BrightLocal, and First Page Sage (compiled at /how-much-does-google-lsa-cost).
To find your own uncreditable rate, pull your last 90 days of LSA leads, manually tag each one that fits "job type not serviced" or "geo not serviced," and divide by total leads. The reference table below shows what different uncreditable rates would cost at common LSA spend tiers, using a $50 median CPL as the baseline:
| Monthly LSA Spend | Leads/Month (at $50 CPL) | Cost at 5% uncreditable | Cost at 10% uncreditable | Cost at 15% uncreditable |
|---|---|---|---|---|
| $2,000 | 40 | $100/mo | $200/mo | $300/mo |
| $4,000 | 80 | $200/mo | $400/mo | $600/mo |
| $8,000 | 160 | $400/mo | $800/mo | $1,200/mo |
| $15,000 | 300 | $750/mo | $1,500/mo | $2,250/mo |
Annualized, a $4,000/mo contractor with a 10% uncreditable rate loses $4,800 per year to leads that used to be creditable. A $15,000/mo contractor at the same rate loses $18,000 per year. Whether your real rate is 5%, 10%, or 15% depends on how disciplined your profile configuration is. The audit in the next section will tell you.
Prevention Playbook: 4 Configuration Changes That Stop the Bleed
Every uncreditable lead now has to be prevented at the source. The four levers that work, in order of impact:
1Service Area Surgery
The single highest-leverage fix. Most contractors set up their LSA service area during onboarding using broad city selections (Google's defaults push you toward city-level coverage) and never tighten it. Result: every distant or marginal zip becomes a potential uncreditable charge.
The fix, step by step:
- Pull your last 90 days of LSA call data. For each lead, note the caller's zip code (use the call address Google provides, or check your CRM/CallRail recording metadata).
- Map every booked job to its zip. Calculate your booking rate by zip: (booked jobs ÷ leads) per zip.
- Identify zips with booking rates below 15% and/or average ticket below your target. These are your bleed zips.
- In your LSA dashboard, edit Service Areas. Remove the broad city if you don't actually want to serve every zip in it. Add only the specific zips with proven booking rates.
- Maximum is 20 service areas. Use them deliberately. A roofer covering 7 strong zips outperforms a roofer covering 1 broad city with 30 weak zips inside it.
Common error to avoid: Don't select a giant metro area "to cast a wider net." Google's LSA service area is not radius-based, so a "Dallas" selection includes every zip code Google associates with that city, including ones an hour from your shop. Zips are tighter than cities for almost every contractor scenario.
2Job Type Audit (Quarterly)
The LSA category tree contains dozens of sub-services per trade. During onboarding the setup wizard suggests broad enablement. Months later most contractors still have job types enabled they never actually wanted.
The fix, step by step:
- Open your LSA dashboard. Click the Business profile menu, then Job types.
- For each enabled job type, ask: (a) Do we have a confirmed in-house capacity to deliver? (b) Do we have a known close rate above 25%? (c) Does the typical ticket meet our minimum margin threshold?
- Any job type that fails two of three questions: disable it.
- Run this audit quarterly. Trade-specific sub-services (ductless mini-split for HVAC, sewer line for plumbers, tile for roofers) drift in and out of profitability as your capacity changes.
Trade-specific job types most contractors should review immediately:
- HVAC: Duct cleaning, indoor air quality (IAQ), commercial HVAC, geothermal. Often enabled by default, often unprofitable.
- Plumbing: Sewer line repair, septic, water filtration installation. High mismatch risk if you don't trench or don't sub these out.
- Roofing: Gutters, siding, skylights. Adjacent services Google clusters with roofing that may not match your actual capacity.
- Electrical: Generators, EV charger installation, low-voltage and data wiring. Specializations many electricians don't actually do.
3Ad Copy + Profile Pre-Qualification
LSA ad copy is limited but every word that pre-qualifies the caller filters out mismatches before they call. Your business description, services list, and review collection are the levers.
Specific moves:
- Business description (200 character limit): State the trades + service areas + critical exclusions concretely. "HVAC repair and replacement, Houston metro, residential only. We do not service commercial systems or duct cleaning." That last sentence prevents two uncreditable lead types from ever happening.
- Services list: Match the language to how customers actually search. If your "Furnace repair" job type is enabled and a customer searches "heat not working," Google routes them to you. Update your service descriptions to mirror customer search phrasing so the routing is accurate.
- Review responses: Mention the specific services and the geographic markets you actually serve. Google reads review responses as signal. Reviews that say "Thanks for the AC install in Sugar Land" reinforce both your services and your geo to the matching algorithm.
- Photos: Upload photos that show your trucks, your service vehicles, your team in the right neighborhoods. Photos with visible street signs from your strongest zips reinforce your real geographic footprint to Google's matching ML.
4Phone Triage Scripts (15-Second Deflection)
Google's published billing policy is that you're charged when a lead is "validated" as a potential customer, but Google does not publish an exact call-duration threshold. Many contractors report that calls ended very quickly (under roughly half a minute) sometimes do not trigger a charge, but this is not guaranteed and Google's automated systems make the final call. Regardless of whether you avoid the charge, identifying a mismatch fast and ending the call cleanly is still the right operational habit, it keeps your CSR off bad leads and your phone line open for real customers.
The 15-second triage script:
CSR (answer): "Hi, this is [Name] with [Company]. May I confirm your zip code real quick?"
Caller: "[zip code]"
CSR: "Got it. And what service are you looking for today?"
Caller: "[service request]"
CSR (mismatch path): "I appreciate you calling. Unfortunately we don't service that zip code / we don't offer that specific service. Let me know if there's anything else." (Ends call politely as quickly as is professional.)
CSR (match path): "Perfect, that's right in our service area. Let me get you scheduled..."
Two notes on this script:
- Always confirm zip first, then service. Reverse order leads to a longer conversation that crosses the 30-second threshold before you realize there's a mismatch.
- Don't argue with Google's call routing in the moment. Even if the lead obviously shouldn't have been routed to you, the CSR's job is clean disengagement, not debate. Document the call for your weekly review.
Train your CSR/dispatcher specifically on the difference between (a) leads that route to you in error and (b) leads that route correctly but don't fit your business model. The first category may get a credit. The second category will not, but can often be prevented from billing entirely with a tight script.
When Prevention Fails: Auto-Credit Workarounds
Even with disciplined profile configuration and CSR training, some uncreditable leads will get through. Two workarounds worth knowing:
1. Always use the "Rate this lead" tool. Even when you know the lead doesn't qualify for credit, rate it as "Very dissatisfied" and select the closest available reason. Per Google's documentation, ratings feed back into the ML routing model. Consistent negative ratings on a specific zip or job type signal that Google should de-prioritize routing similar leads to your account.
2. Contact Google Local Services support for clear-cut cases. If a lead is obviously invalid (spam, duplicate, recorded conversation that ended in under 30 seconds) and auto-credit did not apply, contact support through the dashboard's Help & Contact menu. Some advertisers report support agents will issue manual credits for clear-cut cases the ML missed. This is not policy and not guaranteed, but worth the 5-minute effort on any lead worth $30+.
The 90-Day Implementation Plan
If you've been on LSA for 6+ months without auditing your configuration, the first 90 days of this playbook usually produce the biggest cost savings:
Days 1-7: Pull 90 days of LSA call data. Export from the dashboard or your call tracking platform (CallRail, CallTrackingMetrics, or your CRM). Categorize each lead by zip and by job type requested.
Days 8-14: Service area surgery. Drop bleed zips with sub-15% booking rate. Tighten the 20-service-area limit to your strongest zips. Use city-level selections sparingly.
Days 15-21: Job type audit. Disable any job type failing the 3-question filter (capacity, close rate, margin). Re-enable only what you actually want.
Days 22-30: Profile + ad copy pre-qualification. Rewrite business description with exclusions. Update services list to match customer search language. Add photos with visible street signs from strongest zips.
Days 31-60: CSR script training. Roll out the 15-second triage script. Listen to call recordings weekly. Measure call-end-under-30-seconds frequency.
Days 61-90: Measurement. Calculate your uncreditable lead rate from the pre-playbook 90-day window (your baseline). Then calculate it again from the post-playbook 90-day window. Whatever the reduction is, document it. Use that delta as the input to your annual savings math (delta × LSA spend = annualized savings). Continue running the audit + service-area + job-type review quarterly. Profiles drift.
Frequently Asked Questions
What changed about LSA disputes in July 2024?
Google replaced the manual dispute button in the LSA dashboard with a "Rate this lead" button and an automated machine-learning credit system. The ML system reviews all charged leads within 72 hours and applies credits within 30 days when warranted. Contractors no longer file individual disputes. Two important categories were removed from credit eligibility at the same time: "job type not serviced" and "geo not serviced." Per Google's official documentation: "Google no longer supports credits for 'job type not serviced' and 'geo not serviced' leads."
What does "job type not serviced" mean and why is it not creditable?
A "job type not serviced" lead is a caller who asked for a specific service that you have enabled in your LSA profile but cannot actually deliver. For example, you have "HVAC repair" enabled but the caller asks for "duct cleaning" which you do not offer. Google considers this a profile configuration issue (you enabled the job type) rather than a lead quality issue, so credit is not provided. Before July 2024 this category was creditable; it is no longer.
What does "geo not serviced" mean and why is it not creditable?
A "geo not serviced" lead is a caller located inside your declared LSA service area but in a zip code, neighborhood, or sub-region you cannot profitably serve. Google considers this a service area configuration issue (you declared the area as serviceable) rather than a lead quality issue. Like job type mismatches, this category lost credit eligibility in July 2024. The implication: every uncreditable geo lead is a profile configuration mistake, not a Google billing error.
Can I configure my LSA service area by radius (e.g. a 25-mile circle)?
No. Google's LSA service area configuration does not support radius-based targeting. You must specify your service area by city, postal code (zip), or another defined area type. You can declare up to 20 service areas total. This is a structural difference from Google Ads, which does support radius targeting. Most uncreditable geo leads happen because contractors selected too many cities or zips during setup and did not tighten the list after seeing which areas actually convert.
How much do uncreditable leads typically cost a contractor per month?
No public source publishes a verified uncreditable-rate benchmark, and the rate varies by trade and profile configuration. The honest path is to calculate your own: pull the last 90 days of your LSA leads, tag each one that fits "job type not serviced" or "geo not serviced," and divide by total leads. At a $50 median CPL and a 10% uncreditable rate, a contractor spending $4,000/mo loses about $400/mo, or $4,800 per year. Contractors with broader service areas (HVAC, plumbing, roofing covering multi-city zones) tend to run higher uncreditable rates than naturally-narrow trades (locksmiths, garage door, appliance repair), but the only reliable number is your own.
If a job type lead is uncreditable, why not just turn off that job type?
This is exactly the right instinct, and it is the first prevention step. Audit your enabled job types in the LSA dashboard quarterly. Disable any job type that does not have a clear margin profile, a known close rate, and an in-house capacity to deliver. The risk of leaving a low-volume job type enabled "just in case" is the uncreditable mismatch cost; the cost of disabling it is missed leads you might have referred out at zero acquisition cost. For most contractors, narrower job-type coverage outperforms broader coverage on net P&L.
Can my phone staff prevent uncreditable leads before they are billed?
Possibly. Google's published billing policy is that you're charged when a lead is "validated" as a potential customer, but Google does not publish an exact call-duration threshold. Many contractors report that calls ended very quickly (under roughly half a minute) sometimes do not trigger a charge, but this is not guaranteed and Google's automated systems make the final call. Even when the charge still applies, a 15-second triage script that confirms zip code and asks the specific service requested helps your CSR identify mismatches early and keeps your phone line open for real customers. Train CSRs on the script; measure outcomes against your own pre-script baseline rather than relying on industry-wide claims.
What should I do when Google's auto-credit obviously missed a bad lead?
First, use the "Rate this lead" tool in your LSA dashboard within the 30-day window and select the most accurate dissatisfaction reason. The ML system uses these ratings as feedback signals even when it does not result in an immediate credit. If a clearly invalid lead (spam, duplicate, geographic mismatch into a non-declared area) is still charged after 72 hours, contact Google Local Services support via the dashboard's Help & Contact menu. Some contractors report support agents will issue manual credits for clear-cut cases the ML missed, though this is not guaranteed and not policy.
Sources
- Google Local Services Help: About Automated Local Services Ads lead credits (official documentation on the post-July-2024 credit system, including the explicit exclusion of "job type not serviced" and "geo not serviced" credits)
- Google Local Services Help: Edit your industries, service areas, and job types (20-service-area limit, city/zip/area-based targeting, radius not supported)
- LocaliQ annual search advertising benchmark report (median LSA cost-per-lead data by trade)
- BrightLocal local search research
- Camp Digital: Google Local Service Ads Lead Disputes Deprecation: What Home Service Companies Need to Know
- Coalmarch: Google LSA Updates 2024-2025
- Search Engine Roundtable: Google Automates Local Services Ads Lead Credits
We take over your Google Ads + LSA for 30 days, diagnose what is broken, fix the campaign structure, and you pay only at month end if you want us to continue. No invoice up front.