Google AI Is Calling Your Business: Prep Your Voice Agent

What happens when Google's AI calls your business?

Google's AI now phones local businesses on behalf of searchers, asks for prices and availability, and hands the answers back to the person who searched. If an AI voice agent answers your line, that call is now one AI talking to another, and most agents aren't set up for it. The searcher never hears your voice. They read a summary that puts you next to two or three competitors.

It started as a Search Labs test called "Ask for Me" with nail salons and auto repair shops. Google then rolled it out to Search users across the US, and coverage has been reported to include restaurants, pet groomers and dry cleaners. It's free for the searcher, with higher limits for Google AI Pro and Ultra subscribers.

We build Retell agents that answer inbound calls for service businesses. When we walked through one of these calls from the agent's side, a default setup gets three things wrong: the agent tried to qualify the caller, it offered to transfer to a human, and the post-call workflow created a "new lead" in the CRM. None of that is what you want.

Here's what the call is, how we configure agents to handle it, and how to keep it out of your numbers.

How does Google's AI identify itself on the call?

Every call opens by announcing that it's an automated system calling from Google on behalf of a user. That's Google's commitment after the original Duplex demo drew criticism for sounding too human. It also means your agent can detect it from the first sentence instead of guessing.

What Google's own Business Profile help page on automated calls says about them:

• What it asks: business hours, whether a service is available, pricing, and appointment or reservation details on the customer's behalf.
• Recording: the calls are monitored and recorded for quality assurance.
• Frequency: Google limits repeat calls for the same information and avoids late night and early morning hours.
• Where it doesn't run: it's not available in Indiana, Louisiana, Minnesota, Montana or Nebraska.
• What it never asks for: payment, card numbers or passwords. A "Google" caller asking for those is a scam.

So the call is short, polite, recorded and narrow. It wants three facts and it wants them clearly.

Should you opt out of Google's automated calls?

Stay opted in if you compete on price or speed. Opt out if every job is a custom quote and a range would mislead people. That's the whole decision for most businesses.

The case for staying in is simple: the searcher asked Google to shop around, and Google picks who to call from the local results. If you opt out, you aren't removed from the comparison. You're just the business with no answer next to the ones that gave one.

The case for opting out is narrower. A custom cabinet shop, a commercial roofer or a law firm with intake rules may not be able to give a range that holds up. A wrong number in Google's summary is worse than no number.

To opt out, open your Business Profile, choose More, then Business Profile settings, then Advanced settings, and turn off the options under Google automated calls and text messages. You need a verified profile to see them. You can also tell the caller "Please remove my business from your list." Phone tree mapping calls, where Google dials in to learn your IVR menu, have their own opt-out line at +1-650-206-5555.

Our default recommendation is to stay in and configure the agent properly. A service business is far more likely to lose this comparison because nobody picked up than because its price was wrong.

What should your voice agent say to Google's AI?

Give the range, the one variable that moves it, the next opening and how to book. Then stop talking. Google's AI is collecting comparable answers from several businesses. Long answers don't win. Clear ones do.

A good answer from a brake shop's agent sounds like this:

"Front brake pads and rotors usually run $280 to $420 depending on the vehicle. We have openings tomorrow morning and Thursday afternoon. Customers can book online at our website or call this number."

A default agent, though, is built for humans who are shopping. Out of the box, it will:

• Ask qualifying questions ("What's the year and model?") that a Google system may not be able to answer, which stalls the call.
• Refuse to quote because the prompt said "never give prices on the phone," so the summary shows you as "didn't share pricing."
• Offer a transfer to the front desk, tying up a person for a call with no customer on the line.
• Promise a callback to a number that belongs to Google, not the customer.

The fix is a dedicated branch in the prompt, not a rewrite of the agent. Here's the block we add, adjusted per client:

## If the caller is Google's automated system
If the caller says it is an automated system or assistant calling
from Google on behalf of a customer:
- Answer only what it asks. Use the price ranges and availability
  in the knowledge base. Never invent a number that isn't there.
- Give a range and the main thing that changes it. Do not ask the
  caller qualifying questions unless it offers the details itself.
- State the next available opening and how to book: the website
  booking page or this phone number.
- Do not transfer the call. Do not offer or promise a callback.
- If asked to stop calling, confirm politely and end the call.
- Keep each answer under 30 words. End the call once it says
  thank you or goodbye.

The knowledge base matters more than the prompt. The agent can only quote what you've written down. Before turning this on, we sit with the owner and agree on ranges for the five to ten services people actually search for, plus the variable that moves each one (vehicle size, nail length, dog weight, number of rooms). It's a short conversation, and it's the most useful part of the setup.

If you haven't designed transfer rules yet, read how we hand AI voice calls to a human first. The Google branch is an exception to those rules, so they need to exist.

Why Google's AI calls shouldn't count as leads

The caller is a Google system, not the customer. There's no contact to follow up, no ad click behind it and no revenue it can turn into directly. Treat it like a lead and it'll quietly damage three things.

• Your CRM. A post-call workflow that creates a contact for every answered call will create one for Google, with Google's caller ID. Your sales team then texts a number that doesn't belong to anyone shopping.
• Your follow-up automations. Missed-call text-back and post-call SMS fire on the same trigger. If you run missed-call text-back, make sure it skips these calls too.
• Your ad platforms. If answered calls get uploaded as offline conversions, every Google AI call becomes a "conversion" with no ad click behind it, or worse, gets matched to the wrong session. That's the same problem we wrote about in invalid leads training Smart Bidding: the algorithm learns from conversions that never become revenue.

The real customer shows up later, when they read Google's summary and call or book. That second call is the one your call tracking and attribution setup should catch.

How do you tag Google AI calls automatically?

Classify the call in post-call analysis, then branch on that field in the workflow that consumes the webhook. Don't try to filter by caller ID. Google hasn't published a fixed number for these calls, and the opening announcement is the reliable signal.

In Retell, post-call analysis lets you define custom fields the model fills in after the call ends. We add two:

• is_google_automated_call (boolean): true when the caller identified itself as an automated system from Google.
• google_call_topic (enum): pricing, availability, hours, booking, other.

Then, in the n8n workflow that receives the post-call webhook:

1. Branch on is_google_automated_call before anything else runs.
2. On true: skip CRM contact creation, SMS follow-up and conversion uploads. Write a row to a separate log with the date, the topic and the transcript link.
3. On false: run the normal lead pipeline.

Keep that log. Once a week, someone should read the transcripts and check that the agent quoted the right ranges. It's the closest thing you'll get to seeing what Google tells searchers about you, since you never see the summary itself.

The topic field tells you what searchers are comparing you on. If most calls ask about availability and not price, your booking lead time is the thing to fix, not your rates.

What about businesses without a voice agent?

The same call goes to whoever picks up, and most of the time that's nobody. Google's AI moves on to the next business on the list. You don't get a voicemail you can return, because there's no customer number to call back.

That's the uncomfortable part of this change for small service businesses. The phone used to be a channel you could answer later. Now part of the shopping happens in a two-minute window while a Google system works down a list.

You don't need an AI agent to handle it well. A front desk with a written price sheet and the same "range, variable, opening, booking link" script works fine. But if your line goes to voicemail half the day, this is the clearest case we've seen for putting an agent on it. We covered the setup in how we build Retell voice agents for service businesses.

Does this connect to Ask Maps and AI search?

Yes. It's the same shift: Google's AI answers for you, using whatever information it can find or get on the phone. With Ask Maps replacing Business Profile Q&A, the written facts on your profile feed the AI's answers. Automated calls fill the gaps the profile doesn't cover, mostly pricing and same-week availability.

So the practical order is:

1. Put prices and service details on your Business Profile and website where Google can read them without calling.
2. Configure your phone answer, human or AI, for the questions that remain.
3. Measure the calls that follow, which is where the revenue actually is.

Get a free automation audit

If an AI voice agent answers your phones, or you're thinking about adding one, we'll check how it handles Google's automated calls, whether those calls are leaking into your CRM and ad conversions, and what your agent says when asked for a price. Get a Free Automation Audit and we'll walk you through what we find on a 30-minute call.