Google Local Services Ads Will Charge For Missed Calls On October 1

Google is changing how Local Services Ads charge you, and this one hits your budget directly. Starting October 1, 2026, a missed call can count as a valid lead and show up on your bill even if nobody at your business answers it. Here is exactly what qualifies, what does not, and what you should fix in the next few weeks.

What Changes On October 1

Google will begin charging for certain missed calls and follow-up calls in Local Services Ads when those calls meet its valid lead criteria. The change takes effect October 1, 2026.

The number that matters is 20 seconds. If a call comes in during your business hours and rings longer than 20 seconds, it can qualify as a valid lead and get charged. Nobody has to pick up for that to happen.

Here is how the criteria break down:

• Missed calls over 20 seconds. Charged when they arrive during your business hours and meet Google's valid lead criteria.
• Missed calls under 20 seconds. Not charged. A caller who hangs up after a few rings does not cost you anything.
• Incomplete key-press routing. If you run a phone menu with multiple departments and the caller never presses through to the right one, you are not charged for that call.
• Follow-up calls. If the first call does not qualify as a charged lead, a later call between you and that customer can be charged if it meets the valid lead criteria.

That last one is the piece most people are going to miss. You are no longer looking at a single billable moment per customer. A conversation that starts as an unqualified call and continues later can still turn into a charge.

Why Google Says It Is Doing This

Google's framing is about responsiveness. The company says the change is meant to help customers connect quickly with a trusted local professional, and to reward businesses that demonstrate excellent responsiveness.

I understand the logic. If you run Local Services Ads and you let the phone ring, you are wasting a lead Google worked to send you. Charging for it puts pressure on you to answer.

Here is my problem with it. A ring is not a lead. Now the trigger is partly a clock. If your front desk is with a customer, or you are on a job site with one line, that ring can cost you money without producing a single thing you can follow up on.

What This Actually Costs You

Run the numbers on your own account before you decide how worried to be. Pull your Local Services Ads call log, count the calls in the last 60 days that went unanswered during your posted business hours and rang longer than 20 seconds, then multiply that count by your average cost per lead.

That is roughly what this change would have added to your bill over two months. For a lot of local businesses the number is small. For anyone running a single line with no overflow, it is not small at all.

Keep in mind, your posted business hours are doing real work here. If your hours in Google are wider than the hours you actually have somebody available, you are paying for that gap starting October 1.

What To Do Before October 1

The other thing worth doing is getting your measurement honest. If you are not already tracking calls properly, you will not be able to tell whether your October cost per lead moved because of this policy or because of something else in the account. My guide to phone call tracking with Google Tag Manager covers the setup, and if you run a local site, the walkthrough on conversion tracking for local websites will get the rest of your actions recorded.

One of the biggest mistakes I see is treating Local Services Ads as a set-and-forget channel because Google handles so much of it. This is the kind of change that quietly moves your cost per lead while you are looking at your Google Ads search campaigns instead.

Question to Answer:

How many calls did your business miss during your posted business hours in the last 60 days, and are the hours listed in your Local Services Ads profile hours you can actually answer?

Read the source