Call history on your listing, and the review ask

The argument about the listing has gone the same way for years. We say the Google My Business listing is the front door. The owner says they cannot see what it does. We open the insights screen, which reports views and searches, nobody has ever turned a view into a patient or a job, and the conversation stops there.

That is changing this month. Google is rolling call history out to business listings, and it does something the insights screen never did: it puts a log of actual phone calls in front of you, with the ones nobody picked up marked as missed.

It is the closest thing to a scoreboard Google has handed local businesses in a long time. It is also going to start some uncomfortable meetings, which is the point.

What call history is, and what it is not

Once it is switched on for your listing, Google logs the calls that came from the call button on your listing in Search and Maps. You get the date, the time, the number, and whether the call was answered or missed. It is rolling out, so it may appear in the app before it appears anywhere else, and some listings have it while others in the same city do not yet.

Four things it is not, because we have already been asked all four:

• It is not call recording. There is no audio and no transcript. It is a log.
• It is not call tracking. No dynamic number swapping, no campaign attribution. Calls from your ads and from your website are not in here. This is the listing only.
• It is not a reason to change your listing number. Keep the real business number on the listing. Swapping in a tracking number across your citations is still a good way to make a mess of your local search.
• It is not complete history. It starts when it starts. You cannot ask it about June.

The column nobody expects

In the accounts we run, the first week after a client turns this on is awkward. Businesses that are certain they answer the phone open the log and find missed calls stacked at lunchtime, in the last hour of Friday, and in the first thirty minutes of the day before anyone has taken a coat off.

Nobody is lying. The phone rang while two people were standing at the desk and a third was on hold, and the call that did not get answered left no trace until now.

Read it as a pattern, not as a performance review. Sort by hour, then by day. In almost every case one of three things is true, and each has a different fix:

1. A coverage hole. The same hour every day. Fix the rota before you fix anything clever.
2. An overflow problem. Calls missed only in the busy hours. That needs a second line, a rollover, or somebody who picks up when the first person is already talking.
3. An after-hours problem. Calls outside opening hours that nobody planned for. Either decide you are closed and say so clearly on the listing, or give those callers somewhere to go: messaging on the listing, a booking link, a text-back.

Do not try to solve all three in one week. Pick the worst hour on the log and cover it.

Why this lands on the review flow

Here is the connection that is easy to miss. Call history measures the calls you get. It cannot show you the calls you never got because someone picked a listing with more reviews, or better recent ones, or a real reply under the last complaint.

So the moment you can see what the listing produces, the review programme stops being a vanity project and becomes the input to the number you are now watching. Reviews are a large part of why the call button gets pressed at all.

And the same front desk that misses calls at lunch is the one you have asked to remember to request reviews. A flow that depends on memory loses to a ringing phone every single time. This month we are tightening review flows for clients specifically so they survive a bad Friday.

A review ask that survives a busy day

1. Pick one moment and write it down. Not “when it feels right”. Treatment is finished and the patient is standing at the desk. The invoice is signed in the driveway. One moment, the same one every time.
2. Ask out loud, send the link by text. The spoken ask is what gets the review. The text is what makes it easy. Both, within the hour, or neither works.
3. Use one short link. Pull the review link from your listing, shorten it, and save it in the message template so nobody has to find it twice.
4. Automate the sending, never the asking. In the GoHighLevel builds we run, the text fires off the appointment being marked complete. The human still asks. The system only removes the part humans forget.
5. Reply to every review inside two working days. Use the person’s name, mention the thing they mentioned, keep it short. The replies are read by the next person choosing between you and the practice down the road.
6. Never gate, never pay, never blast the whole list. Google shipped a core update on the 1st and a link spam update on the 26th, and the direction is the same everywhere: bought signals get found. A burst of reviews that disappears next week costs you the reviews and the credibility.

The businesses that do this well are not the ones with the cleverest software. They are the ones where the ask has an owner and a moment.

What to do this month

• Check whether call history has reached your listing, and switch it on. Check again next week if it has not.
• After seven days, read the log by hour and by day and write down your single worst hour.
• Fix that hour with staffing or a rollover before buying any tool.
• Turn on listing messaging if you have somebody who will answer it, so after-hours callers have a second door.
• Write your review moment on one line and tape it to the front desk. One moment, one script, one link.
• Set the review text to send automatically off appointment completion, then send yourself a test.

Call history will not fill your schedule. It will end the guessing about whether the listing does anything, and once the guessing is over the next question is always the same: how do we get chosen more often. That is what our review and reputation work and listing management are for, and the automation that makes the ask happen without anyone remembering usually ends up living in the CRM we build.