Google's own help page defines the Calls metric on a Business Profile as the number of times a customer clicked the call button, which is not the same as the number of conversations that happened. That gap is where Google Business Profile automation for a booked job either works or quietly fails. A tap is only a signal, and what your company does right after it decides whether the signal becomes a visit on your calendar. This article follows one customer request through every step, so you can see which parts to automate and which to keep in human hands.
Key Takeaways
- A Business Profile counts a tap on the call button as a call, so a counted call and a real conversation are two different things.
- Every touchpoint from a missed call to a booked job should write to one customer record with a status, or the automation has nothing to act on.
- Follow-up texts need carrier registration under A2P 10DLC and a human handoff for emergencies, complaints and unusual pricing.
- The booked status in your own system, not the Bookings metric in Google, is the number that shows whether the journey works.
What a Google Business Profile inquiry really is
Google's Business Profile performance help page lists the interactions it tracks: calls, messages, bookings, website clicks and directions. It defines Calls as clicks on the call button and Website clicks as clicks on the website link. It also says bookings only appear when they are managed through a booking provider, and that only the metrics that apply to your business are shown.
For a trades company, that means a homeowner does one of three things on your profile. She taps call, taps your website, or asks for directions to your office. The first two are inquiries. The third is a softer signal. All three are the start of a journey you can map and, in parts, automate.
One old option is gone. The Google chat and call history notice states that those features stopped being available in Business Profile on July 31, 2024. It adds that businesses keep receiving calls from the profile and can still track engagement such as web traffic or directions requests. If an older guide tells you to answer customers in Google chat, skip it. The inquiry now lands on your phone or your website, and your own systems have to catch it.
The journey starts on a page you control, so the basics matter first. Correct hours, the right phone number and clear services keep the first tap honest. Our Google Business Profile management service covers that setup, and everything below assumes it is in place.
Stage one and two: the tap and the first reply
Take an invented example, not a client. A homeowner in Van Nuys finds a leaking water heater early in the morning, searches for a plumber, and sees a few profiles. She taps call on yours. Nobody picks up, because both of your techs are under a sink.
This is stage one, and it is where the journey usually ends. The tap is counted in the Calls metric, yet no one on your side knows she exists. If you want the longer view of how Google decides which profiles she sees in the first place, our piece on Google Maps ranking changes covers it.
Stage two is the first reply. The automation here is small and plain on purpose. A missed call triggers a text from your business number. It names your company, asks what is going on, and offers a link to request a time. A person reads whatever she writes back. The goal is not to replace you. The goal is to make sure she hears from you before she taps the next profile.
A human answering still wins when it is possible, and we compare the options in AI receptionist vs answering service. Automation covers the gaps: jobs in progress, lunch, after hours, and the days when several calls arrive together.
Google Business Profile automation that logs every request
Stage three is capture. Every touchpoint should create or update one record: the missed call, the text reply, the web form, the booking request. Without that record, your Google Business Profile automation for a booked job is just a pile of texts on someone's phone.
A customer follow-up system holds the record. Our CRM and customer follow-up service is built around that idea. At minimum the record needs a name, a number, the service, the zip code, the source and a status.
Keep the status list short
Status is the field people skip, and it drives everything after it. Six values are enough: new, contacted, estimate scheduled, quote sent, booked and lost. Add more and nobody updates them, which leaves the automation acting on stale information.
Tag the source
Use a tagged website link on the profile so a visit from Google is not mixed up with a visit from a truck wrap or a yard sign. Google's help page says Website clicks counts clicks on the website link, so a tagged link lets your analytics show what those visitors did next. Do the same with a dedicated tracking number if you want calls separated by source.
Stage four: follow-up that sounds like your company
Once a request has a record, the follow-up runs from the status. Estimate scheduled sends a confirmation with the day, the arrival window and the tech's first name. The day before the visit, a reminder invites a reply to reschedule. After the visit, the quote goes out the same day.
Quotes are where jobs are lost, because the homeowner goes quiet. A short sequence handles it: a check-in asking if she has questions, a second message a few days later, then stop. We lay out wording and timing in quote follow-up for contractors. The point is that nobody has to remember. Our AI automation workflows service connects these steps so a status change sends the right message.
Keep each text short and written in your voice. Ask one question per message, and include your company name so she knows who is writing. Never send something that reads like a machine pretending to be a person.
Any text sequence also needs consent and carrier registration. Twilio's A2P 10DLC documentation says anyone sending SMS or MMS over a 10DLC number from an application to the US must register, and that unregistered traffic gets additional carrier fees. Ask whoever builds your system to show you the registration, not just promise it.
Stage five: the booked job and what comes after
A job is booked when it is on the calendar with a confirmed arrival window and the status changes to booked. That change should trigger three things: a confirmation to the customer, a note to your tech with the details from the inquiry, and a timer for the review request.
Reviews close the loop back to the start of the journey. After the job is done, a text with a direct link to your Google review page asks for feedback. Our reputation improvement service handles that request flow. Those reviews feed the profile that the next homeowner taps.
Do not send a review request when the job went badly. Route that customer to a person first.
One measurement trap is worth knowing. Google's help page says the Bookings metric counts completed bookings managed through a booking provider, so for most trades companies it stays empty. Your own booked status is the real number. Each month, compare three counts: taps from the profile, records created, and jobs booked. The gap between the first two shows requests that never got captured. The gap between the last two shows where follow-up or pricing needs work.
Map your own profile to booked jobs
Tell us how inquiries reach you today and we will show which steps to automate and which to keep with your team.
Where Google Business Profile automation should stop
Automation fails when it pretends to know more than it does. Keep a person in three places. Emergency calls such as a gas smell or active flooding should alert someone immediately. Quotes outside your standard pricing need a human decision. Any complaint needs a human voice. In each case the system should go quiet and notify you rather than guess.
Keep the map honest too. If your profile shows you open and nobody answers, automation only hides a staffing problem. Fix hours and coverage first, then automate the gaps that remain.
Finally, read the messages. Once a month, open a handful of real conversations from start to finish. If a text sounds off, edit it. If a status was never updated, find out why. A flow that is reviewed stays useful, and a flow that is ignored slowly starts sending the wrong message to the right customer.
Questions about Google Business Profile automation
Google Business Profile automation is a set of rules that react when a customer calls, taps your website or requests a visit from your profile, then log the request, send a reply and schedule follow-up without manual work. A person still handles the conversation itself.
No, because Google ended the chat and call history features in Business Profile on July 31, 2024, according to its help page, so replies now have to happen through your phone, text or website.
Usually not, because Google's help page says the Bookings metric counts only bookings completed through a booking provider, so a job scheduled by phone or your own form will not appear in that number. Track the booked status in your own customer system instead.
Yes, if the texts go from an application over a 10DLC number to US phones, because Twilio's documentation says that traffic must be registered for A2P 10DLC or it draws extra carrier fees. Your builder should handle the registration and show you its status.
Emergency calls such as a gas smell or active flooding, complaints, and any quote outside your standard pricing should alert a person right away, while the automation stays quiet and does not guess.
Compare three counts each month: profile taps from Google's performance page, customer records created in your system, and jobs marked booked, because the gaps between those counts show where requests are being lost.
Customers should be told who is texting, since every message names your company and reads like a short note from your office, and a real person takes over as soon as the customer replies with a question.
