Lead Generation

The Lead-Credit Dispute Log: A Template That Recovers 8-15% of Aggregator Spend

Every operator on Angi, Google Local Services Ads or Bark gets junk leads: wrong number, out of area, spam, a service they do not offer, a tire-kicker who never picks up. Every platform has a way to claw some of that money back. Almost no operator uses it consistently, because the platforms built the dispute process to be just annoying enough that a busy contractor gives up after two tries. That friction is not an accident. It is the point. Here is the leverage. Contractors who dispute promptly, inside the window, with clear documentation, recover credits close to half the time on LSA, and even Google's automated system returns roughly 6 to 7 percent of spend on its own (BGCollective / Coalmarch, 2026). Layer disciplined manual disputes on top and total recovery on a well-run account lands in the 8 to 15 percent range of aggregator spend. On a 3,000-dollar-a-month lead bill, that is 240 to 450 dollars a month you are currently gifting the platform for leads you could never have won. The recovery does not come from arguing harder on any single lead. It comes from a system: a standing log that captures the evidence the same day, and a habit of disputing every qualifying lead by volume so the odds work in your favor. The artifact below is that log and that system.

Joshua Agonya Pi'Rwot

By Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator

Executive summary

The platforms make disputing bad leads deliberately tedious so most operators give up. A standing evidence log flips that. Dispute every qualifying lead the same day, by volume, and recover a slice of spend the passive operator leaves on the table. The artifact is the log template plus the by-volume system.

Section 1

Why this works, in one note

Two models explain why a log beats effort. Mechanism design says the platform engineered the dispute rules to minimize payouts: short windows, automated review you cannot argue with, categories they quietly remove, and a burden of proof placed on you. Google dropped manual disputes for an automated credit system in 2024, and in 2025 stopped crediting "job type not serviced" and "geo not serviced" at all (Coalmarch, 2026). You cannot change their rules. You can build a counter-mechanism: a log that produces the exact evidence their system rewards, on the exact timeline it requires, every time. Game theory of repeated play says a single dispute is a weak bet, but the same bet repeated many times converges on its expected value. If disputing a qualifying lead recovers credit 40 percent of the time, disputing one lead is a coin-flip you might lose, but disputing every qualifying lead all year reliably returns that 8 to 15 percent. The log is what lets you play the volume, because it removes the per-dispute effort that makes operators quit. What this cannot see: platforms can and do change the rules mid-year. The log stays valid, but the categories and windows in it need a quarterly refresh, because the landlord rewrites the lease without asking.

Section 2

The artifact, part one: the dispute log template

Build this as a spreadsheet. One row per disputable lead, filled the same day the lead comes in, because the evidence is freshest and the window is shortest right at the start. These are the columns. The two columns that do the work are dispute reason and evidence captured. Get those right the same day and the filing is a two-minute job. Leave them for later and the evidence is gone and the window closed. The valid-reason list (dispute only these) Disputing leads that do not qualify wastes your time and trains the platform to ignore you. Dispute on grounds the platforms actually credit: • Wrong or non-working number. You could not reach the customer because the contact detail was bad. Evidence: your call log showing the failed attempts. • Spam or fake lead. Obvious bot, solicitation, or a competitor. Evidence: screenshot of the message. • Geography outside your set service area. Note: LSA no longer credits this if your profile settings are wrong, so keep your service area tight and accurate first (Coalmarch, 2026). Evidence: the lead's location versus your service map. • Service you do not offer. They asked for work outside your listed services. Same LSA caveat: fix your profile so you are not charged for it in the first place. Evidence: the request text versus your listed services. • Duplicate. The same customer charged twice. Evidence: both lead IDs. • No contact possible. You attempted contact promptly and repeatedly and got nothing back, on platforms that credit unresponsive leads. Evidence: timestamped call and text attempts. If a lead is just a customer who chose someone else, that is not disputable. It is the shared-lead lottery working as designed, and disputing it burns credibility you need for the real cases.

Section 3

The artifact, part two: the by-volume dispute system

The log is the tool. This is the routine that turns it into recovered cash. Five rules. 1. Log the same day, every day. The moment a junk lead comes in, fill the row and capture the screenshot. Same-day capture is the single biggest driver of recovery, because evidence decays and windows are short. Make it part of whoever handles leads, not a monthly clean-up. 2. Dispute by volume, not by mood. File on every qualifying lead, not just the ones that made you angry. The recovery rate is a percentage, so it only pays out across volume. One skipped qualifying dispute is money left on the table. 3. File inside the window. LSA credits favor disputes filed promptly, generally within 30 days, and disputing quickly correlates with recovery near half the time (BGCollective, 2026). Angi and Bark have their own windows. Put the deadline in the log and never miss it. 4. Match the reason to a credited category, word for word. Use the platform's own category language in the filing. "Wrong number, non-working" recovers. "Bad lead" does not. The mechanism rewards leads that fit its boxes, so put them in the box. 5. Reconcile monthly and total the recovery. Once a month, sum the Amount Recovered column, divide by that month's aggregator spend, and you have your recovery rate. If it is under 8 percent, your same-day logging or your reason-matching is slipping. If it is above 15 percent, either you are getting a lot of junk (a reason to wean the channel) or you are disputing well. The system runs in about five minutes a day plus fifteen minutes a month. That is the entire cost of recovering a low-double-digit slice of your lead spend.

Section 4

The ordered lever list (GEER)

Ranked by cheapest and fastest to stand up. 1. Fix your profile settings first (day one). Free. Tighten your service area and listed services so you stop getting charged for geo and job-type leads that LSA no longer credits. Prevention beats disputing. 2. Build the log (day one). Free. A single spreadsheet with the columns above. Nothing recovers without it. 3. Turn on same-day logging (week one). Free. Assign it to whoever touches leads. This is the habit the whole recovery depends on. 4. Dispute by volume inside the window (ongoing). Free. File on every qualifying lead, every time, before the deadline. 5. Reconcile monthly (ongoing). Free. Total the recovery, compute the rate, and let it flag when the discipline slips. 6. Use the recovery rate to rank channels for the wean. The channel throwing the most junk (highest dispute volume) is often the one to cut first, and your log is the evidence for that decision. Every lever here is free. The only cost is the discipline of same-day capture, which is exactly the friction the platforms are betting you will not sustain.

Section 5

What this system cannot see

The log recovers a slice of spend on a channel you are still renting. It does not make a bad channel good. If you are disputing 20 percent of a platform's leads as junk, the real signal is not "dispute harder," it is "this channel's lead quality is low, wean it." Treat a high dispute rate as a reason to leave, not a reason to stay and claw back scraps. The other blind spot is rule change: platforms adjust dispute categories, windows and automation without notice, so the valid-reason list needs a quarterly check against each platform's current help pages. Google has already removed two whole categories in a single year. Run the log, recover the 8 to 15 percent while you are still on the channel, and let the dispute volume tell you when a channel has earned a spot on the de-platforming schedule. The recovered spend is best spent funding the owned channels that make disputing unnecessary in the first place. Sources: BGCollective, LSA Lead Credits for Contractors 2026; Coalmarch, Google LSA Automated Credits & Verified Badge Updates; Google Local Services Help, Automated lead credits; Bark Help Centre, Understanding lead pricing.

Joshua Agonya Pi'Rwot

Written by

Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator · Country Director, AVODA Group Uganda · EMBA

Joshua helps service-business operators turn scattered marketing into a clear path from first attention to booked call. He is Founder of Business Growth Accelerator and Country Director of AVODA Group Uganda.