Google cannot hear your phone ring, but it can see who gets the next call

A client asked us a question recently that we could not stop thinking about. How would Google know whether a business answers its phone, when the number on the profile is the business's own line and Google never hears the call?

Our answer is a theory, and we hold it firmly. Google cannot hear the call, but it can see what the caller does next. A caller who taps Call and is back in the results a few seconds later, tapping the next business, has told Google the first business did not pick up.

The short answer

• Once a caller taps Call, the conversation leaves Google's app. Google cannot hear it.
• Google can still see the tap, the return to the results and the next business called.
• Google already says missed calls can hurt rank in its paid Local Services Ads. We think the free map results read the same signal another way.
• Reviews and SEO cannot answer a phone. If your profile says open 24 hours, someone has to pick up at 2 AM.

Google loses the call the moment you tap it

When someone taps Call on a Business Profile, Google hands the number to the phone's dialer and the call runs on the phone network, between the caller and you. A Business Profile usually lists the business's own number, so there is no Google forwarding line in the middle to time the ring or hear a hello.

Google can count the tap. It shows you the count in the profile's performance report (Google's guide to profile performance). What it cannot see from the profile alone is whether anyone answered.

What happens after the call is different. The caller's phone goes back to the screen they came from, and their next move is in Google's own app.

The call is answered

1. 1 Search Garage door repair near me
2. 2 Tap Call Google counts the tap
3. 3 Dialer Google cannot hear this part
4. 4 No return The job is booked, the search is over

The search ends here

The call rings out

1. 1 Search Garage door repair near me
2. 2 Tap Call Google counts the tap
3. 3 Dialer Ringing, then voicemail
4. 4 Back in seconds The caller returns to the results Google sees the short call
5. 5 Tap the next one A competitor gets the call

The next business gets the job

Our model of what Google can observe from its own app. Google has not published how it uses this.

Why we think Google reads the call that never connected

Google says local results are "mainly based on relevance, distance, and popularity" (Google's own local ranking guide). Answering the phone is not on that list, and Google has never said it is. So treat what follows as our reading, not a published rule. The word "mainly" leaves the door open.

Three things make us confident the signal is in play. First, where Google can track the call, it already ranks on it. Its help for Local Services Ads, the paid listings at the top of many trade searches, says it plainly: "If you regularly fail to answer calls or respond to messages, your ad ranking may be affected" (Local Services Ads help).

Second, Google has wanted this data on the free profiles too. It once kept a customer call history inside Business Profiles, and it retired that feature in July 2024 (Google's notice on call history).

Third, Google learns from what searchers do next. The Justice Department's post-trial brief in its search case describes a system called Navboost that remembers clicks from the prior 13 months (the brief, as filed). A visitor who bounces straight back from a slow website and clicks the next result is the classic case. A caller who comes straight back from a phone that rang out and taps the next business looks the same from where Google sits.

Reviews and SEO cannot answer the phone

Here is where we land with every owner who asks. You can have the reviews, the photos, the categories and a well built website, and still lose the job while the phone rings. All of that work brings the caller to the moment of the call. If nobody picks up, the work paid for a competitor's lead.

We have argued before that more of the same optimization is rarely the fix, as with service pages that grow longer without ranking better. Answering the phone is the opposite of a page tweak. It is the one thing that turns every other signal into revenue, and we think it feeds the ranking back too.

The hours on your profile make it sharper. A profile that says open 24 hours is a promise to the person searching at 2 AM with a door stuck open or a lock that will not turn. Google's guidelines ask for your "regular customer-facing hours of operation" (Google's profile guidelines), and a 24 hour listing that sends that caller to voicemail breaks the promise at the worst moment. Our post on emergency locksmith local SEO walks through why those late searches matter so much to a trade.

If you want to see what the unanswered ones are costing, you can work out what your missed calls cost with our free calculator. It takes your own numbers and gives you one figure.

Every review and every ranking you earn ends at the moment the phone rings. If nobody answers, you paid for a competitor's lead.

What we found when we read our own call logs

This is the part we did not expect. We run an AI phone agent for a garage door company we work with, and by its own records it answered calls day and night. When we read the call platform's logs line by line in October, some callers had heard nothing but ringing.

The agent was not the problem. Our own setup was. Each call waited for our integration to send the agent its instructions, and the phone platform gives that step a fixed time budget. When our side ran slow, the platform never connected the call. The caller heard ringing or silence and hung up, and from the outside it looked exactly like a business that does not answer.

We changed the order. The agent now starts the moment the call comes in, and the caller's history and today's calendar reach it a beat later, while it is already saying hello. Then we closed the last gap: a call that drops, never connects, or ends during the greeting now gets called back.

1. Second 0

   The call drops

   It never connected, the caller hung up during the greeting, or a caller with a real need left before booking.

2. About 1 minute

   First callback

   The agent says who it is and why it is calling before anything else, and leaves a short voicemail if nobody picks up.

3. An hour later

   Second try

   If the first callback did not reach anyone, it tries once more.

4. Next morning

   Last try

   A final call at a reasonable hour. A request not to be called ends the sequence for good.

Every call, callback and result lands in the owner's email and in a shared sheet, so the owner sees the history of each caller in one place. An urgent caller, say a broken spring with the door shut, goes straight to the owner's phone instead of being booked for later.

Why we build our agents instead of buying one

Plenty of CRMs and phone systems now sell an AI receptionist you switch on in an afternoon. For a lot of businesses that is fine. It answers, takes a message and beats voicemail.

Our approach is different, and the difference shows up in moments like the one above. We build each agent from the base layers rather than reselling a finished product. The phone line runs on Twilio. The agent runs on Vapi, a voice agent platform we configure call flow by call flow. Google Apps Script ties it to the owner's email, sheets and calendar. Because we hold every layer, we could read the logs, find the delay and change the order of the call ourselves.

The same goes for the parts a caller hears. We test different AI models against the same scripted calls and compare how fast each one answers and how it handles the hard cases. We pick the voice from the full ElevenLabs library, and with the owner's permission we can build a voice from their own.

Both answer the phone. The difference is who can change what happens on the call.

On the call	A ready-made AI receptionist	An agent we build
What it says	The vendor's script with your details	Your rules, written with you, changed when you ask
The AI model	Whatever the vendor chose	Tested on your call types, swapped when a better one wins
The voice	A menu of preset voices	Any voice in the library, or one built from yours
Where calls land	The vendor's app	Your email, your sheet, your calendar
When a call drops	Usually a missed call notice	A callback with the caller's history in hand
Adding a feature	Wait for the vendor's roadmap	We build it and test it on real calls

None of this makes an off the shelf product wrong. If yours answers fast, books jobs and passes urgent calls to you, keep it. We build ours because our clients ask for things a closed box cannot do, and because when something breaks we want to be able to open it.

Answer first, then Optymize the rest

Our rule for a client with a Business Profile is short. If the profile shows hours, the phone gets answered in those hours, by a person or by an agent, and a dropped call gets a call back. Rankings, reviews and pages come after that, because they only pay off when someone picks up.

That is how we Optymize a local business, and it is why phone answering sits next to Business Profile management in our work. If you want an agent built around your rules instead of a vendor's, see how we set up AI phone agents.

This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.