Someone searches "emergency plumber near me" at 7:40pm, finds your Google Business Profile, taps the "Message" button, and types: "Water heater's leaking, can someone come tonight?"
That message lands in an app you don't have open. Nobody sees it until 9am the next morning. By then, they've already called two competitors and one of them picked up. The lead is dead, and you never even knew it existed.
Full disclosure: I work for Ready, and we build SMS tooling for exactly this problem. But the core issue here isn't a product gap — it's a routing gap. Inbound conversations from Google, web chat, and Facebook are scattered across four different apps that nobody watches in real time. This post is about pulling those into one inbox that gets answered fast, and the consent details that come with replying.
Why Google Business Messages leaks leads
Google Business Messages (GBM) is a legitimate high-intent channel. Someone messaging your profile from a "near me" search is usually mid-purchase — they've compared you to two other results and picked yours to reach out to. That's a warm lead, not a cold one.
The problem is where the message goes. GBM notifications live inside the Google Maps app or the Google Business Profile app on one person's phone. If that person is on a job site, off shift, or just not looking, the message sits. There's no shared queue, no escalation, no way for a second person to grab it.
And the response-time math is brutal for local service work. Reply speed for these inbound messages behaves a lot like speed-to-lead on web forms — the difference between answering in 2 minutes and answering in 2 hours is the difference between booking the job and being ghosted. A customer with a leaking water heater is not going to wait until morning for you.
The same problem, five times over
GBM isn't the only orphaned inbox. A typical local service business is quietly ignoring inbound across:
- Google Business Messages — one person's phone, no shared visibility
- Website chat widget — often routes to an email nobody checks
- Facebook / Instagram DMs — a different app, a different login
- Missed calls — voicemail that never gets returned
- The "text us" number on the truck — goes to a personal cell
Each channel has its own login and its own notification style, so nobody wins the race to reply. The fix isn't "check them more often." It's collapsing everything into one place where replies happen over SMS, which is the channel people actually open.
Route it all into one SMS inbox
The pattern that works: pipe every inbound conversation into a single unified inbox, and reply by text. Text has the open rates and reply rates the other channels wish they had — for opted-in, expecting-a-reply conversations, replies often land in the 30–50% range, and people answer within minutes rather than days.
Ready's unified conversations inbox is built for this. Inbound replies land in-app, and for connected GoHighLevel accounts they two-way sync into GHL as well, mapped per location so a multi-location business or an agency managing several clients keeps each one isolated. Instead of five apps and one overloaded person, you get one queue that anyone on the team can watch and answer.
The practical flow looks like this:
- Customer messages your Google profile or web chat.
- That conversation surfaces in your Ready inbox.
- A human — or an AI-assisted reply — responds within a minute or two.
- If it's a job, you book it or hand it to whoever's dispatching.
Where the AI reply agent earns its keep
Nobody sits on the inbox at 9pm. That's the gap AI closes.
Ready's inbound AI can run in three modes: off, suggest (it drafts a reply a human approves), or auto (it responds on its own). For after-hours coverage, auto mode handles the first touch so the customer gets an answer in seconds instead of a 12-hour silence:
"Thanks for reaching out — we can get someone out for the water heater. What's the best address, and is it actively leaking right now? I'll get you on the schedule."
That reply keeps the lead warm, gathers the details your tech needs, and buys you time until a person picks it up in the morning. It's a newer capability, and I'd be honest with you: for complex quotes you still want a human. But for "capture the lead and don't let it go cold," an auto first-reply beats an empty inbox every time.
If you'd rather handle it live, the same logic applies to missed calls — an auto-text-back that fires inside 60 seconds turns a missed ring into a text thread instead of a lost job.
The consent question you can't skip
Here's the part most "just route it to SMS" advice skips: replying by text creates a message-consent situation you have to handle correctly.
When someone messages your Google Business Profile, they've initiated a conversation on that channel. Replying to answer their question is one thing. But if you then start sending them promotions, review requests, or reminders by text, you're now doing marketing SMS — and that needs actual opt-in, not "well, they texted us first."
A clean way to handle it: reply to the question, then ask for explicit consent before you add them to anything ongoing.
"Happy to help! Want me to text you appointment reminders and updates for this job? Reply YES to opt in — msg & data rates may apply, reply STOP anytime."
That "reply YES" captures the opt-in, and Ready records the attestation so you've got an audit trail. From there:
- Automatic STOP handling honors opt-outs and propagates them, so a contact who unsubscribes can't be messaged again across campaigns.
- Quiet-hours enforcement holds sends outside permitted local hours, which reduces TCPA exposure on that 7:40pm-turned-8am reply.
- Consent capture logs the opt-in for bulk and API sends.
None of that makes you lawsuit-proof — compliance is ultimately the sender's responsibility — but it's the difference between "we reply to inbound and get proper consent before marketing" and "we blast whoever texted us and hope." If you're capturing numbers at the register too, the same care applies — the "text us your number" sign isn't valid consent on its own.
What it actually costs to run
The inbound-and-reply model is cheap because you're not blasting a list — you're answering warm conversations one at a time.
On Ready's Standard tier that's $0.02/segment plus a $0.0045 carrier pass-through, so $0.0245 per 160-character segment. Say you handle 400 inbound conversations a month and each one runs ~6 segments back and forth:
400 × 6 × $0.0245 = $58.80/month to answer every lead that would otherwise have died in an unwatched app.
If even a handful of those are $400 service jobs you'd have lost, the math isn't close. And you start with 2,500 free credits, no card required, which covers a few hundred conversations before you pay anything.
Two things to watch on cost: emoji or other unicode drop a segment from 160 to 70 characters, so a chatty reply with a 👍 can quietly double your segment count — worth keeping your templates GSM-7 plain text. And getting registered matters: unregistered traffic gets carrier-filtered, so run these on a proper 10DLC campaign with the use-case that matches what you send.
The practical takeaway
Google Business Messages, web chat, and Facebook DMs are all sending you warm, high-intent leads — you're just not seeing them in time. The fix is three moves:
- Route every inbound channel into one SMS inbox so nothing sits in an app nobody watches.
- Answer fast — a human in minutes during hours, an AI-assisted reply after hours so the lead never goes cold.
- Capture consent before you market, and let automatic STOP, quiet-hours, and attestation logging keep the reply side clean.
You don't need to overhaul anything to start. Point your inbound conversations at a unified inbox, answer the next lead in two minutes instead of twelve hours, and see how many jobs you were quietly losing. You can try Ready free with 2,500 credits and no card, or read the GHL setup guide if you're routing through GoHighLevel.