RingBill

1. One-liner

Tells contractors which unanswered Google LSA calls Google billed them for, and which hours to stop advertising.

2. Trend signal — why now?

On 24–25 August 2026 Google emailed every Local Services Ads (LSA) advertiser a billing change effective 1 October 2026. The operative sentence, quoted by PPC Land from the email: “missed calls placed during business hours will be charged as valid leads if a user stays on the line for more than 20 seconds.” Second sentence, from the same email via Search Engine Roundtable: “If an initial call doesn’t qualify as a charged lead, any follow-up calls between your business and the user that meet the valid lead criteria will be charged.” Google Ads Liaison Ginny Marvin clarified on X: “The advertiser will only be charged 1x for any follow-up calls they make to the user within 15 days of the initial interaction.”

Until now Google’s own “How leads work” page defined a missed call as a valid lead only if “you return the customer’s message with a text message, email, or call.” A ring-out cost nothing. From October a ring-out during your stated hours costs the same as a booked job.

The money involved is not small. SearchLight Digital’s February 2026 benchmark tracked $6.72M of LSA spend across 888 contractors and 126,650 leads: blended CPL $53, HVAC $51, plumbing $57, electrical $39. Multiple call-analytics compilations put the home-services missed-call rate at roughly 27% of inbound calls, with pickup under 18% after hours. Clear Click’s Alistair Mains (27 August 2026) did the arithmetic for UK clients: a business paying £25 a lead that answers 80% of calls sees “the same hundred calls cost £2,500 instead of £2,000.” His one-line rule: “your true cost per usable lead becomes your lead price divided by your answer rate.”

Practitioner reaction was immediate and sour. Agency operator Anthony Higman posted the email on X with “BWHAHHAH Google LSA Gonna Charge For Missed Calls Now LOL.” Joe (@theJoeShmow): “More teriffic #LSA news.” InvisiblePPC’s Avi told agencies to go pull two numbers before October: “How many LSA calls were missed during the last 30 to 60 days? When are they being missed?” Nobody has a tool that answers that question from the LSA data itself.

The recourse side was already broken before this change. Google removed manual lead disputes in mid-2024. Its automated-credits page says charged leads “may be issued credits automatically if later determined to be low quality” and that “Google no longer supports credits for ‘job type not serviced’ and ‘geo not serviced’ leads.” Olly Olly’s Elisabeth Spencer (11 June 2026) on the surviving “Rate this lead” survey: “It is feedback, not a dispute. It cannot overturn a charge the system already reviewed and decided to keep.” Adsquire’s field report: “So far we have had this work on about 20% of bad leads so far.” Blue Grid Media puts feedback-to-credit conversion at “roughly 15–25%.” SearchLight reports contractors get “approximately 6-7% of their LSA spend back in credits.”

Two things make this buildable now rather than in 2024. First, the Google Ads API exposes everything a contractor needs to audit Google’s bill: LocalServicesLead carries lead_charged, lead_status, creation_date_time, credit_details.credit_state and lead_feedback_submitted; LocalServicesLeadConversation carries phone_call_details.call_duration_millis and call_recording_url. Second, v19 added LocalServicesLeadService.ProvideLeadFeedback, whose response field is credit_issuance_decision: “Decision of bonus credit issued or rejected. If a bonus credit is issued, it will be available for use in about two months.” The survey reasons are enumerated: GEO_MISMATCH, JOB_TYPE_MISMATCH, NOT_READY_TO_BOOK, SPAM, DUPLICATE, SOLICITATION. The dispute is a programmatic call with a same-second verdict. Nobody sells that to a two-truck plumber.

One more dated forcing function: Google is folding LSA into Google Ads as a pay-per-lead Performance Max campaign, first wave August 2026 for US plumbing, HVAC, electrical, appliance repair, cleaning, lawn, roofing, pest and moving. The standalone LSA dashboard contractors learned is going away in the same quarter the billing rule changes.

Provenance:

• Signal 1 (demand + deadline): Google email, effective 1 Oct 2026, missed calls >20s during business hours charged as leads; follow-up calls charged; key-press exception — https://ppc.land/google-charges-local-services-advertisers-for-missed-calls-over-20-seconds/ and https://www.seroundtable.com/google-lsa-missed-subsequent-calls-41940.html — 2026-08-25
• Signal 2 (feasibility): Google Ads API LocalServicesLead (lead_charged, credit_details), LocalServicesLeadConversation (call_duration_millis, call_recording_url), and ProvideLeadFeedback returning credit_issuance_decision — https://github.com/googleapis/googleapis/tree/master/google/ads/googleads/v22 (resources/local_services_lead.proto, services/local_services_lead_service.proto) — 2026-09-06
• Signal 3 (economic): $6.72M LSA spend across 888 contractors, 126,650 leads, $53 blended CPL, ~6–7% of spend returned as credits — https://searchlightdigital.io/google-local-service-ads-cost-per-lead/ — 2026-02
• Signal 4 (economic, incumbents charging): LSA management priced $149–$800/mo; AI answering $79–$1,200/mo; LSA Command sells a “Refund Engine” — https://bluegridmedia.com/lsa-management-for-contractors , https://lsacommand.com/ — 2026-09-06
• Signal 5 (recourse gap): Google automated credits page; manual disputes removed 2024; no credits for job-type/geo mismatches — https://support.google.com/localservices/answer/15100654 — 2026-09-06
• Signal 6 (policy boundary): LSA requirements prohibit “diverting customers to a different phone number to avoid paying for a lead” — https://support.google.com/adspolicy/answer/6245891 — 2026-09-06 Category: Platform shift

3. The opportunity

Google is the counterparty on both sides of this bill. It decides whether a ring-out crossed 20 seconds, whether it fell inside the hours you typed into a profile screen two years ago, and whether to credit it back. The contractor sees one number in a billing tab. That is the vendor-conflict-of-interest shape: the party that bills you is the only party that can audit the bill, and its documented credit rate is 6–7% of spend while practitioners flag 20–25% of leads as junk.

Every incumbent sells around this hole, not into it:

• AI answering services (Avoca $25–$299/mo per call bundle, Goodcall $79/mo, Smith.ai $95–$800/mo, TheKeyBot $149–$1,200/mo) sell prevention. They take the LSA forwarding number and answer. Good product, wrong question for the October bill: they don’t tell you what Google charged you for, and half of contractors will not put a bot in front of their phone.
• LSA management agencies ($149–$800/mo) do the hours edit and the “Rate this lead” clicking by hand, monthly, for the accounts that pay them. Blue Grid literally advertises “dispute management” as a line item. This is the law-firm-sells-the-manual-version pattern.
• LSA Command bundles an AI answerer with a “Refund Engine” that “puts up to 10% of your ad spend back in your pocket.” It targets pool companies, publishes no price, and does not touch business hours or the missed-call rule.
• PrimeLSA sells an agency dashboard plus “professional IVR systems” as a service.

What none of them sell: a weekly, per-account answer to “which of my charged leads were calls nobody answered, which hours generated them, and what should I change in the profile this week.” The lever that matters after 1 October is the stated business hours and ad schedule, because Google says the charge only applies inside them, and Google will never build a tool that tells you to narrow them. That is the product.

Two hard boundaries, both in Google’s own text, shape it. The key-press exception (“the 20 second timer starts once the customer presses the key”) is real, but the LSA requirements also prohibit “diverting customers to a different phone number to avoid paying for a lead.” So RingBill does not sell a fee-dodging IVR. It sells the ledger, the hours verdict, and the feedback filing. If a contractor has a legitimate departmental menu, RingBill measures it. It does not install one.

4. Target market

• Primary customer: Owner or office manager of a 1–15 truck plumbing, HVAC, electrical, garage-door or locksmith business in the US or UK, spending $2K–$15K/month on LSA, answering the phone themselves or with one CSR. No agency, or an agency that charges under $300/mo and does not touch leads.
• Why they buy: Clear Click named the three exposed profiles exactly: “Lean teams where one or two people answer the phone between jobs, on site, or from a van”, “businesses with stated hours exceeding actual staffing coverage”, and “single-line setups without routing options.” TheKeyBot on locksmiths: “The customer standing next to a locked car is the definition of a caller who will not wait, will not leave a voicemail, and will not call back.” From October those callers cost $40–$90 each whether or not anyone picks up.
• Rough TAM reasoning: Census counts 208,058 plumbing/HVAC establishments (NAICS 238220) and 120,172 electrical (238210) in the US. Trade press puts LSA adoption among home-service contractors near 70% by late 2025. Even discounting that claim by half, there are more than 100,000 US LSA accounts in the core trades, before roofing, pest, cleaning, locksmiths, lawyers and the UK. SearchLight’s 888-account sample averages $7.6K/month spend. A 27% miss rate at $53 CPL on a 150-lead month is roughly $2,100 of newly billable ring-outs, before credits.
• Why now for them: The bill changes on 1 October 2026. The dashboard they know is migrating into Google Ads in the same quarter. The manual dispute button died in 2024. Their agency, if they have one, is writing blog posts about it rather than pulling their answer rate.

5. Product sketch (MVP)

• Connect in two minutes. Contractor signs in with the Google account that owns the LSA profile. RingBill pulls 90 days of leads, call durations and recordings through the Google Ads API. No phone-number change, no answering bot, no agency access required.
• Answer-rate map. Hour-by-day grid of LSA calls: answered, missed, and missed-over-20-seconds, overlaid with the stated business hours and ad schedule from the profile. Shows the contractor the Tuesday 12–1pm hole they never knew they had.
• October exposure number. Dollars per month of missed calls that will be charged under the new rule at the account’s real CPL, updated weekly. This is the free tier and the sales pitch.
• Hours verdict. Recommends the ad-schedule and business-hours edit that removes the most billable misses for the least lost lead volume, with the exact click path in the LSA profile (Profile & Budget → Ad schedule; Edit business hours). Re-runs every Monday as staffing changes.
• Charge audit. Every charged lead cross-checked against Google’s own rule: was it inside stated hours, was the call over 20 seconds, was it a 15-day follow-up already charged once. Charges that contradict the rule get a one-page support-ticket packet with the lead ID, timestamp, duration and rule citation.
• Feedback filer. AI listens to the recording of each charged lead and drafts the survey reason (SPAM, SOLICITATION, DUPLICATE, JOB_TYPE_MISMATCH, GEO_MISMATCH, NOT_READY_TO_BOOK). Contractor taps approve; RingBill files ProvideLeadFeedback before the 30-day window shuts, logs the credit_issuance_decision, and watches credit_state until the money lands.
• Weekly text. “You were charged for 9 unanswered calls this week ($477). 6 were between 12–1pm Tue/Thu. 3 feedback filings credited, 2 rejected. Narrowing Thursday lunch would have saved $190.”
• Agency view. One screen across every client account with exposure, answer rate and open feedback, for the LSA management shops that currently do this in Looker Studio by hand.

6. AI angle — what’s load-bearing

Two places, both essential. First, the recording classifier: deciding whether a 47-second unanswered call was a robocall, a solicitation, a duplicate of yesterday’s caller, or a real customer asking for a service you don’t offer is a listening job. Google’s own model does it and credits 6–7% of spend; RingBill’s job is to catch the other 15–20% practitioners say is junk, with the correct enumerated reason attached, because the wrong reason gets rejected. Second, the hours verdict: turning a 24×7 grid of answer rates, lead values and lost-volume estimates into one recommended schedule edit a plumber will act on is a judgment call, not a report.

Strip the AI and you have a Looker Studio dashboard, which agencies already build and contractors already ignore.

7. Localization angle (if any)

US-first because that is where the PMax migration and the bulk of LSA spend sit. The UK is the second market on day one: the change applies there (Clear Click’s client math is in pounds) and UK LSA spend is under-served by tooling. Canada, Australia and Germany run LSA too. No language work needed beyond English at launch; recording classification is English-first with Spanish soon after for US trades.

8. Business model — path to $1M–$5M ARR

• Pricing: $79/month per LSA account. Includes the audit, hours verdict, feedback filing and weekly text. Free tier: the October exposure number and the answer-rate map, read-only, no filing.
• Agency plan: $39/account/month at 10+ accounts, white-labelled weekly report.
• ACV: ~$950 per contractor; ~$470 per agency-managed account.
• Rough math to $1M ARR: 1,050 direct contractors at $79/mo. Against 100,000+ US LSA accounts in the core trades, that is ~1% penetration. Or 600 direct plus 900 agency-managed seats.
• Rough math to $5M ARR: ~4,000 direct accounts plus ~3,000 agency seats, plus a $149 tier for multi-location and legal (lawyer leads run $50–$200+; the audit is worth more when the lead is worth more).
• Expansion path: per-location pricing for multi-branch operators; legal vertical at higher price; a call-answering partner referral fee (RingBill knows exactly which hours a client should buy coverage for and can sell that slot to Avoca or Goodcall); and once the PMax migration lands, extending the audit to Google’s pay-per-lead PMax charges generally.

9. Go-to-market wedge — first 100 customers

• Deadline email to scraped LSA advertisers. Google’s LSA results pages list every “Google Verified” business by city and trade. Scrape plumbing, HVAC, electrical and locksmith advertisers in the 40 largest US metros (target 8,000 businesses) and email the owner, subject line “Google starts charging you for missed calls on Oct 1 — here is your number.” The CTA is the free exposure audit (OAuth connect, number in two minutes). Expect 4–6% connect rate on a dated, dollar-denominated warning; convert 20% of connects to paid once they see a four-figure exposure. That is 60–100 paying accounts from one list.
• Agencies as resellers, not competitors. Fifteen LSA management shops (Blue Grid, Footbridge, Cornerstone, Promotive, Digimatiq, Clear Click, InvisiblePPC and the rest that blogged about the change in the last two weeks) each manage dozens to hundreds of accounts and are telling clients to “pull your answer rate now.” Offer the agency plan white-labelled with a two-week free run across their book. Three agencies at 40 accounts each is 120 seats.
• Contractor Facebook groups and Reddit. “HVAC Business Owners,” “Plumbing Business Owners,” r/HVAC, r/Plumbing, r/PPC. Post the anonymised answer-rate maps from the first 50 audits (“here is what 50 plumbers’ missed-call hours look like, and what it costs them in October”). This is the content the agencies will screenshot for us.
• Answering-service partners. Avoca, Goodcall, Smith.ai and TheKeyBot want the same customer. RingBill is the diagnostic that proves the missed-call hours exist; offer them the free audit as their top-of-funnel and take a referral fee when a contractor buys coverage for the hours RingBill flagged.
• Google Ads community and Search Engine Roundtable comments. Every thread about the October change and every “charged for a lead I never answered” post after 1 October gets a reply with the free audit link. Low volume, high intent.

10. Build complexity — justification

Medium. The Google Ads API developer token (Basic access, 15,000 ops/day) and OAuth flow are standard but the approval loop takes days to weeks and the reporting-only use needs to be positioned correctly against Google’s required-minimum-functionality policy. Reading leads, conversations, durations and recordings is plain API work; transcribing and classifying recordings is off-the-shelf speech-to-text plus an LLM with a six-value output; the hours verdict is a small optimisation over a 168-cell grid. Two people, 8–10 weeks to a v1 that produces the exposure number and files feedback. Hardest unknown: how an unanswered call is represented in LocalServicesLeadConversation after 1 October (duration of ring time versus zero), which the validation sprint tests on a live account.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Reads the advertiser’s own data with their OAuth consent; files feedback via a Google-provided endpoint. Deliberately excludes fee-avoidance call routing, which Google’s LSA requirements prohibit.
Ethical — no harm / dark patterns	✅	Helps an advertiser audit a bill and narrow ads to hours they can answer. Callers get answered more, not less.
Market exists (evidence above)	✅	$6.72M/month across one agency’s 888 accounts; incumbents charge $149–$1,200/mo around the problem; Google’s own credit rate documents the gap.
1–5 person team can build this	✅	Two engineers, one with Google Ads API experience.
Launchable with <$50K / ₹40L	✅	API access is free; transcription cost per account is cents; scraping and email under $2K.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	From 1 October every ring-out during stated hours is a $40–$90 line item. Real, dated, weekly. Not 17+ because a contractor can buy an answering service or edit hours by hand, and some will.
Demand evidence	15	11/15	Incumbents charging on both sides ($149–$800 management, $79–$1,200 answering, LSA Command’s refund engine), Google’s documented 6–7% credit rate, practitioner “20% of flagged leads” reports, trade-press coverage within 48 hours of the email. Missing: verbatim contractor complaints about this charge, because it is not live yet.
Build feasibility	15	11/15	Standard API + OAuth + transcription. Developer-token approval and the unknown representation of unanswered calls in the conversation resource are the two friction points.
Distribution clarity	15	11/15	Named lists (LSA results pages by trade and metro), named agency resellers who are already writing the content, a dated fear to lead with. Conversion math is an estimate.
Revenue mechanics	15	11/15	$79/mo sits well under both incumbent price bands and under one month’s newly billable misses for a typical account. 1,050 accounts to $1M is achievable against 100K+ targets. Churn risk if Google softens the rule.
Time to first revenue	10	7/10	Free audit converts to paid on the exposure number; Oct 1 makes September the buying month. 4–8 weeks from launch if the token clears.
Defensibility	10	4/10	Copyable by LSA Command, PrimeLSA or any agency with a developer. Head start, the classified-recordings corpus and agency distribution are the only moats.
Total	100	70/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · sales-heavy

Key assumptions to validate (3–5)

1. Assumption: The Google Ads API shows enough about an unanswered call (duration, timestamp, recording of ring/voicemail) after 1 October to distinguish a charged missed call from an answered one. How to test: Connect three live LSA accounts in the first week of October and reconcile every charged lead against the office phone log by hand.
2. Assumption: Contractors will connect a Google account to a stranger’s tool for a free number. How to test: Send the deadline email to 500 scraped advertisers in September; kill threshold is under 3% connect rate.
3. Assumption: ProvideLeadFeedback filed with the correct enumerated reason gets credited materially more often than the 15–25% practitioners report from the UI. How to test: File 200 feedbacks across the pilot accounts over 30 days and log credit_issuance_decision; need ≥30% issued to make the filer a headline feature rather than a footnote.
4. Assumption: A Basic-access developer token is granted for a reporting-plus-feedback tool without the full RMF build-out. How to test: Apply in week one with the exact use case described; if Google demands campaign-management features, ship read-only reporting first and file feedback through the UI with a browser extension.
5. Assumption: LSA agencies will resell rather than clone. How to test: Offer five agencies the white-label plan in September; two signed books of 20+ accounts each validates the channel.

Risk flags

1. Platform dependency: Everything rides on one Google API and one Google billing rule. Google can soften the 20-second rule, publish its own missed-call report, or restrict recording URLs. The Rescinded-order trap applies: watch the LSA help centre weekly for reversal.
2. Regulatory / policy risk: The LSA requirements ban fee-avoidance diversion. RingBill must stay on the audit-and-advise side of that line; any feature that looks like gaming the timer invites account suspensions for customers and a token revocation for us.
3. Market timing: If the PMax migration changes how LSA leads surface in the API (new resources, retired fields), the v1 data layer needs a rewrite mid-launch.
4. Incumbent response: LSA Command and PrimeLSA are one sprint from a “missed-call audit” tab. The window is the six months in which they are busy with PMax migration and answering-bot upsells.

14. Structured verdict

Score:                  70/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Engineer with Google Ads API scar tissue + a partner who has sold to plumbers or run an LSA agency
Time to revenue:        4–8 weeks after developer token approval
Capital to launch:      $8–15K (₹7–13 lakh)
Top 3 assumptions to validate first:
  1. Unanswered charged calls are distinguishable in the API after 1 Oct — reconcile 3 live accounts against phone logs in week one of October
  2. Deadline email converts ≥3% of scraped LSA advertisers to an OAuth connect — 500-send test in September
  3. Correctly-reasoned API feedback credits at ≥30% — 200 filings, log credit_issuance_decision
Kill criteria:
  - Abandon if Google withdraws or materially softens the missed-call charge before 1 December 2026
  - Abandon if fewer than 15 of the first 500 emailed advertisers connect an account
  - Abandon if the API cannot distinguish answered from unanswered charged calls and Google refuses recording access for the use case

15. Next step — 1-week validation sprint

• Day 1–2: Apply for the Google Ads API developer token with the exact reporting-plus-feedback use case. Meanwhile, borrow read access to two friendly contractors’ LSA accounts (any HVAC or plumbing owner in your network who spends over $2K/mo) and pull 90 days of leads and conversations by hand through the API explorer. Build the answer-rate grid in a spreadsheet and put a dollar figure on their October exposure.
• Day 3–4: Scrape 500 “Google Verified” plumbing and HVAC advertisers in five metros from LSA results. Send the deadline email with a Calendly-style “get your number” link that collects OAuth consent. Separately, DM five LSA agency owners who blogged about the change with the two spreadsheet audits as proof and ask for a white-label trial across ten accounts.
• Day 5: Decide go / no-go on three numbers: connect rate on the 500 emails (need ≥3%), whether the two live audits produced a four-figure monthly exposure a contractor reacted to, and whether at least one agency said yes to a trial. Two of three is a go; if the token is refused outright with an RMF demand, pivot the v1 to read-only reporting and revisit.