$13,000+ in LSA Credits Recovered in One Cycle — By Automating What Most Businesses Do by Hand (or Don't Do at All)
Google charges you for LSA leads that were never real customers.
Wrong service area. Spam calls. Someone who called about something you don't do. Google's own policy allows you to dispute all of it and get a credit. Most businesses pay anyway.
Not because they don't know disputes are possible. Because doing it properly doesn't scale.
Why Most Businesses Don't Dispute
Disputing an LSA lead correctly means:
- Going through every charged lead individually
- Listening to or reading what actually happened on the call
- Determining whether it meets Google's dispute criteria
- Filing each dispute one at a time in the LSA dashboard
For a single-location business getting 30–50 leads per month, that's already a significant time commitment. For a multi-location operation running across 5, 6, or 10 markets — it's hours of mind-numbing work every week that nobody actually does consistently.
So most businesses eat the cost. They accept that some percentage of their LSA spend is waste, chalk it up to the cost of doing business with Google, and move on.
That waste is larger than most people realize.
What Google Will Actually Credit
Google's dispute policy covers more than most LSA advertisers know:
| Dispute Category | What Qualifies | Common Example |
|---|---|---|
| Wrong service | Call is for a service you don't provide | Plumber charged for electrical inquiry |
| Wrong area | Caller is outside your service area | Job location 40 miles outside coverage |
| Spam / robocall | Automated or clearly non-human call | Robocall, dead air, obvious spam |
| Duplicate charge | Same lead charged multiple times | Same caller, same issue, billed twice |
| Not a service request | Call has nothing to do with your business | Wrong number, personal call, solicitation |
| Already a customer | Existing customer calls, charged as new lead | Repeat client billed as acquisition |
Every one of these is a legitimate dispute ground under Google's own policy. Every one of these is money back in your account. Most businesses are letting all of it go because catching them manually doesn't scale.
The System I Built
The system runs four steps automatically:
1. Pull charged leads — connects to the LSA account and pulls every charged lead from the billing period
2. Auto review — reads the call transcript for each lead (via Whisper transcription + Claude analysis) and checks it against dispute criteria: service match, geographic match, call quality, conversation content
3. File disputes — where the transcript shows valid grounds, files the dispute automatically with the appropriate category and supporting context
4. Track credits — logs every dispute filed and monitors which ones result in credits
The work a person would do by hand for hours — done automatically, only on valid disputes. No gaming. No mass-filing junk. The system applies the same judgment a careful human reviewer would apply — it just does it across every single lead instead of the handful a person gets to before giving up.
The Result
Across several multi-location home service accounts over one monthly dispute cycle: $13,000+ in LSA lead credits recovered.
That's money the business spends on real leads next month instead of handing it to Google for charges that never should have stuck.
To be precise about what that represents:
| Metric | Value |
|---|---|
| Accounts covered | Multiple multi-location home service accounts |
| Dispute cycle | One monthly billing period |
| Credits recovered | $13,000+ |
| Disputes filed | Valid grounds only — no junk filings |
| Manual work required | None after setup |
| Approval rate | ~50–60% (Google approves roughly half of valid disputes) |
The $13,000 is what came back. The amount disputed was higher — Google doesn't approve every valid dispute. But even at a 50% approval rate, the math is compelling for any operation that currently disputes nothing.
What "Disputes at Scale" Actually Means
For a single location, manual disputing is annoying but doable. Most attentive owners or managers can get through a month's leads in an hour or two if they prioritize it.
For multi-location operations, the math breaks down:
| Locations | Avg Leads/Month | Time to Manually Review All | Time Per Week |
|---|---|---|---|
| 1 | 50 | ~2 hours | ~30 min |
| 3 | 150 | ~6 hours | ~1.5 hours |
| 6 | 300 | ~12 hours | ~3 hours |
| 10 | 500 | ~20 hours | ~5 hours |
At 6 locations, you're talking about a dedicated part-time job just to review leads for dispute eligibility. Nobody does this. So the disputes don't get filed. And Google keeps the money.
The automation makes the 6-location case take the same effort as the 1-location case: setup once, run monthly, review the dispute log.
The Transparency Part
Before anyone asks — because this question comes up — here's the full context.
Every dispute filed by this system was filed only where the call showed valid grounds under Google's own policy. The system isn't looking for loopholes. It's applying the same criteria a careful human reviewer would apply: does this call represent a genuine service request in the right area for the right service?
If yes — no dispute. If no — dispute filed with the appropriate category.
The difference between this and doing it manually isn't the judgment. It's the coverage. A person reviewing 20 calls out of 300 might recover some credits. A system reviewing all 300 recovers what's actually there.
If You're Running LSA Across Multiple Locations
You are almost certainly overpaying Google every month. Not because of fraud or errors on your end — because the manual dispute process doesn't scale to multi-location operations, and the money you're owed stays with Google by default.
The fix isn't complicated. It requires systematically reviewing every charged lead against dispute criteria and filing where there are grounds. That's it. The hard part is the scale.
If you're running LSA across multiple locations and want to know what your current dispute gap looks like — how much you might be leaving on the table — let's talk. I can audit your last billing cycle and give you a concrete number.
Related:
- You Don't Have a Lead Problem. You Have a Conversion Problem You Can't See.
- I Analyzed 100 Service Business Calls With AI. What I Found Was Uncomfortable.
- 3 AM, Database Down, AI Bot Dead: What I Learned From My Worst Night in Automation
- From 64 to 496 Pages: How I Built a Local SEO System That Drives 4-5 Organic Leads Per Day