On this page
Google Local Services Ads is usually the most expensive lead source a local service business runs, and it is the one most likely to be handled badly after hours. Calls get a voicemail. Messages sit in the Local Services app until someone opens it.
Google is explicit that responsiveness affects the experience and encourages businesses to reply promptly, and the app shows customers an estimated response time. The message side is the part you can fully automate. Here is how to think about it.
Understand the two kinds of LSA lead
Calls. Someone taps to call from your ad. If nobody answers, you get a missed call and often a voicemail. Automation here means routing and follow up, not a machine answering the phone.
Messages. Someone sends a job request through the ad instead of calling. This lands in your Local Services inbox with the job type, location, and whatever they typed. This is a text conversation, which means it can be answered automatically and answered well.
Most teams cover calls with a person or an answering service and leave messages uncovered, which is backwards. Messages are the easier half to solve.
What Google gives you natively
Inside Local Services you can set an away message and manage your inbox with the app, including notifications on your phone. That is worth configuring, because an away message is better than nothing and it sets an expectation.
What it does not do is have a conversation. The customer replies with a question, and the thread waits for a human. If that human is on a job until 6pm, the estimated response time your prospect sees is not the one they experience.
Automating the message side properly
The setup is straightforward once you decide what the automated reply is allowed to say.
Write your price boundaries. List the jobs you are willing to quote a range for in a message, and the ranges. Everything else gets collected and handed to a person. This one decision prevents most of the damage automation can do.
Pick your qualification questions. For LSA leads, job type usually arrives with the lead, so your first question is normally address or urgency. Keep it to one question per message.
Set your service area and hours. LSA already targets geography, but job specific exceptions are common. Write them down.
Define handoff triggers. A job that qualifies, a customer who asks for a person, anything outside the price list, and anything that reads as a complaint. Those should reach your team by text, WhatsApp, or email with the full transcript attached, not a summary.
Set the follow up rules. A quiet thread is not a dead thread. One nudge a few days out, one the next week, one final one after two weeks, each referencing what was already discussed. Stop on opt out, an explicit no, or a human takeover.
InstantResponse.AI handles LSA message leads this way alongside Yelp Requests and Thumbtack. The rules and tone are configured on the AI customization page, and the difference between open ended AI replies and strictly scripted ones is covered on the AI mode vs non AI mode page.
Do not forget the calls you already paid for
LSA calls are where the budget usually goes, and they are also where the least review happens. When call data is available in the connected account, you can pull recordings, transcripts, and summaries into the same place as your message leads. That gives you three things worth having:
A record of what was actually said. Disputes about whether a price was quoted stop being arguments.
A view of the calls nobody returned. Every missed call is a lead you paid for. Seeing them as a list rather than a notification changes behaviour.
Coaching material. Reading five transcripts of calls that did not book teaches more than any script.
The Google LSA Auto Responder page covers what is available on the call side and how the review workflow looks.
A realistic rollout
Week one, turn on instant message replies with a conservative script. No prices, just acknowledgement plus one question plus a clear promise of when a person will follow up. Read every thread yourself.
Week two, add price ranges for the two or three job types you quote most often. Keep reading threads.
Week three, add follow up. This is where recovered leads show up, and it is also where tone problems become obvious, so review the nudges specifically.
Week four, look at the numbers: reply time, customer reply rate, threads reaching your team qualified, and spam filtered out. Adjust the copy, not the software.
What not to automate
Some things should always go to a person. Anything involving safety, anything where the customer is upset, anything that requires a judgement call about liability, and anything where the price depends on something a photo cannot show. Write those into your rules before you go live rather than after an awkward thread.
Also keep in mind that platform policies and local rules apply to how you contact people, and customers who opt out should stay opted out. That is a configuration decision, not an afterthought.
The point
LSA leads cost real money and the message side is the cheapest place to stop losing them. Answer in seconds, ask what you would ask, hand off cleanly, and review the calls you already paid for. None of that requires changing how you sell. It only requires deciding, in advance, what a good first reply says.
If you want the wider picture across every paid channel, the AI auto responder hub ties Yelp, LSA, and Thumbtack together, and Speed to Lead for Local Service Businesses covers the reasoning behind fast first replies.
If LSA is not your only paid channel, How to set up an auto responder for Yelp Requests and How to respond to Thumbtack leads faster apply the same rules to Yelp and Thumbtack.