Google Maps Messages: Where Chat Lives Now and How to Answer It
Google Maps messages are best understood as a routing problem, not a chat feature: the customer taps a contact button on your Business Profile and lands in SMS or WhatsApp, and everything that happens after that tap is yours to own. Native chat inside Business Profiles is gone. What replaced it moves the conversation onto channels you already control, which sounds like an upgrade until you check who is watching the other end of the phone number.
The Buttons on Your Profile and What Sits Behind Them
Start with what actually exists on a Business Profile today. As of July 31, 2024, Google removed the native chat and call history features from Google Business Profiles, so businesses can no longer message customers directly through their profile, per Google Business Profile Help. The thread that used to live inside Maps, with its own badge and its own notification, is not there anymore. Google now lets a business list a WhatsApp and a text message contact option on its profile, added in February 2025, which you can read about in the same Google Business Profile documentation. Those buttons do not run on Google’s messaging stack. They hand the customer to a carrier SMS thread or to WhatsApp, and the profile is just the signpost. That distinction decides everything that follows, because a signpost cannot hold a conversation, remember a history, or escalate itself to a colleague. For a closer look at the mechanics, our own notes on enabling chat from Maps walk through the setup side.
How the routing actually works
A searcher opens your listing on a phone, taps the message option, and their phone opens its native SMS composer with your number already filled in. One tap later they are typing in a channel that has nothing to do with Google, no shared thread visible to your team, and no record on the profile itself. The message arrives at your Twilio or Telnyx-provisioned number like any other text, which means the quality of the experience is set by your inbox, not by Google.
The channel you choose matters to Google
Here is where configuration starts to bite. If a business adds both WhatsApp and text message options to its Google Business Profile, only the text message option is shown to customers, according to Google Business Profile Help. You can list both in the backend if you like. The searcher sees one. Set up your profile expecting WhatsApp traffic that the button will never deliver.
Why This Is Harder Than It Looks
The difficulty is not the tap. It is that the tap removes Google from the loop at the exact moment you most want a system holding the thread. A customer who found you through Maps has no logged-in session with you, no stored preference, and no indication of which employee they contacted last time.
There is a second layer of fragility in the geography. Google Business Profile messaging via WhatsApp or SMS appears only to searchers on mobile devices, not on desktop search results, per BrightLocal. So a business that tests its own profile on a laptop, sees nothing, and concludes the setup failed has drawn the wrong conclusion twice: once about the button, and once about how much of its audience it can actually reach.
Then there is the vocabulary problem. Teams ask for “chat” and get an SMS thread, then staff it with the wrong expectations. SMS is not a live chat widget. It arrives in the same stream as order updates and appointment reminders, so a customer may leave it unread for hours and answer at night, and your team needs a way to pick the thread back up without losing the name attached to it. Treating the button as a chat window produces missed replies; treating it as an inbound lead source, logged and assigned, produces a follow-up.
Setting Up the Handoff So a Message Reaches a Person
The setup is boring and the boring parts are what fail. Run it in order and verify each step from a phone, not a desktop browser.
- Confirm the message option appears on your Business Profile as a customer sees it, by opening the listing on a mobile device and looking for the contact buttons.
- Decide which single gateways handle the traffic: a dedicated business number for SMS, and a WhatsApp Business number if your region and audience support it.
- Provision that SMS number through a carrier gateway you have registered, not a personal mobile, so ownership of the number does not walk out the door with a step-down employee.
- Connect the number to a shared inbox where more than one person can read and reply, and assign a first responder for each shift.
- Write one short auto-reply that names your business, sets an expectation for a human reply, and asks the question that lets you answer in one round trip.
- Test the whole path from a phone that has never contacted you, and check that the message lands in the shared inbox with the sender’s number attached.
That fourth step is where most small teams stop short. A shared inbox is the difference between a channel and a phone somebody remembers to check. If the only place the message appears is a single device, every shift change creates a gap.
Where People Go Wrong
A business publishes a line and routes the button to a number nobody owns. The messages arrive, the customer waits, and the listing quietly accumulates the reputation of a place that does not answer. Naming a rotation and a backup before the button goes live costs an hour; discovering the gap through complaints costs more.
Some teams list WhatsApp and SMS both and assume two doors. Google serves one, so the WhatsApp configuration becomes dead configuration that the team still staffs and still checks, splitting attention without splitting reach. Pick the channel your customers actually use on mobile, then put your effort behind it rather than behind both.
There is the naming trap inside the inbox itself. Two customers named similar things, both arriving as bare phone numbers, and the agent answering the second one with the first one’s history. Threads tied to a number and a name rather than to a lookup are what prevent this, and it is worth checking how your tool stores the identity before you trust it.
And there is the review blind spot. Teams spend the setup effort on the message button and never look at what appears one tap away, so a Maps inquiry that turns into a bad experience lands as a public review with no reply attached. A profile is a single surface: the message, the question, and the review are three ways the same customer reaches you, and our article on where reviews live now covers how that surface changed.
The Numbers Behind the Shift
The timeline is short and specific, which is unusual in a category full of vague promises. Native chat and call history came out of Business Profiles on July 31, 2024, per Google. WhatsApp and text message contact options arrived in February 2025, per Google.
Those two dates sit eighteen months apart, and they tell you the direction rather than the size of the opportunity. Google removed the thing it had to operate and replaced it with buttons that hand traffic to channels businesses already pay for. The practical read: the volume was never the question, the ownership was. A business that had learned to ignore a Google chat badge now has that same demand arriving as an SMS it cannot ignore, because it looks like every other text on the phone.
The regional carve-out deserves its own line. Those 2025 buttons are available on mobile search worldwide except in the Philippines, Vietnam, Thailand, Taiwan, Japan and Korea, per Google. If you operate in one of those markets, the Maps route is closed to you and WhatsApp, Instagram, or plain SMS from your own listings and website carry the load.
About Sociocs
We built Sociocs as a business texting and omnichannel customer engagement platform, and this routing problem is the one we spend our days on. The text message button on your profile lands in an inbox our team can share, alongside WhatsApp Business messaging with click-to-chat, Instagram DMs, Facebook Messenger, Telegram business messaging, and Google Reviews and Google Q&A management. One place to answer the Maps inquiry and the review that follows it. If you want the background on the retired product, our explainer on what Google Business Messages was sets the context.
Choose something else if you run a single-location shop with one person answering every message on one phone and no intention of adding a second person. A shared inbox solves a coordination problem you do not have yet, and the Free tier on our pricing page is there when that changes.
When you are ready to map your channels to one queue, get in touch and we will walk through the setup with you.
Frequently Asked Questions
Can customers still message a business directly inside Google Maps?
No. Native chat inside Business Profiles was removed on July 31, 2024, per Google Business Profile Help. What a customer taps now is a contact button that opens their own SMS app or WhatsApp, so the conversation continues on a channel your business provisions and staffs rather than inside Google’s interface.
Why does my Google Business Profile show only one message option?
Google shows only the text message option when a business configures both WhatsApp and text messaging, according to Google Business Profile Help. That is expected behavior, not a bug in your setup. If you need WhatsApp traffic, drive it from your own website or Instagram rather than waiting for the profile button to surface it.
Why can’t I see the message button when I check my listing?
The WhatsApp and text message options appear only to searchers on mobile devices, not on desktop search results, per BrightLocal. They are also unavailable in the Philippines, Vietnam, Thailand, Taiwan, Japan and Korea, per Google. Verify from a phone in your target market before concluding anything is broken.
What number should the message button point to?
A dedicated business line provisioned through a carrier gateway, connected to a shared inbox rather than a personal mobile. That keeps the number with the business when staff change, and it lets more than one person answer during a shift. Registration requirements for high-volume US texting apply to that number, so plan the gateway before you publish it.