The best Google LSA message template does not merely prove that someone saw the lead. It earns the next reply.
That means each message should do three things:
- Show that you understood the request.
- Reduce uncertainty for the customer.
- Ask for the smallest useful next step.
Below are 16 templates for teams responding to Local Services Ads manually, followed by the rules for adapting them without sounding robotic.
Replace every bracketed field before sending. Only make claims your business can support.
These examples are a human response playbook—not a description of how LeadUp replies. LeadUp uses an AI agent that interprets the incoming request and conversation context, then generates an appropriate response within each business’s rules.
Before you use these templates
Google says responsiveness to inquiries and average response time can influence LSA ranking and profile quality. It does not publish a guaranteed response deadline. Read the full Google LSA response-time guide for the calculation and measurement framework.
For a manual workflow, use templates to remove drafting time, not thinking. Your approved version of each reply should reflect:
- Actual services and exclusions
- Service areas
- Business and after-hours coverage
- Minimum job or property requirements
- Questions needed for a useful handoff
- Rules for price, scheduling, and emergencies
First-response templates
1. Standard service confirmation
Hi [First name]—thanks for reaching out. Yes, we handle [requested service] in [city/ZIP]. To get this to the right person, is the work for a [home/business/vehicle/other relevant type]?
Use when: The service and area appear to fit, but one routing detail is missing.
Why it works: It confirms relevance before asking the customer to do more work.
2. Urgent home-service request
Hi [First name]—I understand you need help with [issue] in [area]. Is there active leaking, no heat/cooling, a safety concern, or another condition the team should know about right now?
Use when: The job may require urgent triage.
Guardrail: Do not tell the customer a situation is safe. Follow the business’s approved emergency escalation language.
3. Request with too little detail
Hi [First name]—we may be able to help. What service do you need, and what ZIP code is the property in?
Use when: The incoming message is “need a quote,” “call me,” or similarly incomplete.
Why it works: It asks for the two facts most likely to determine basic fit.
4. After-hours response
Hi [First name]—we received your request for [service]. I can collect the details now for the [service/scheduling] team. What is the service ZIP code, and when would you prefer a callback?
Use when: Intake is covered, but a person cannot promise service or an appointment.
Guardrail: Say when the team will review the request only if that timing is guaranteed.
Qualification templates
5. Service-area confirmation
We serve parts of [region]. What is the service address or ZIP code? I’ll use it only to confirm coverage and route the request correctly.
Use when: City-level information is too broad or absent.
6. Job-type qualification
Thanks. Which best describes the work: [option A], [option B], or [option C]? If none fit, send a short description and I’ll route it correctly.
Use when: A small set of categories determines the next intake path.
Why it works: Options are easier to answer than an open-ended questionnaire, while the final sentence leaves room for exceptions.
7. Property or customer-type qualification
Is this for a [residential/commercial] property, and are you the [owner/tenant/property manager]?
Use when: Property type or authority to approve work changes eligibility.
Guardrail: Remove any option that is irrelevant or inappropriate for the business.
8. Timing and urgency
When do you need the work completed: today, within the next few days, or on a later planned date?
Use when: Timing affects routing but is not an emergency assessment.
9. Detail needed before a quote
Pricing depends on [the factor that genuinely changes scope]. Could you share [one or two specific details]? The team can then review the request without guessing.
Use when: The customer asks for a price before enough information exists.
Guardrail: Do not imply that a firm quote will be available remotely unless that is true.
Price-question templates
10. “How much does it cost?”
The price depends on [scope factor], so I don’t want to give you an inaccurate number. What [specific detail] applies to your job, and what ZIP code is the service location?
Use when: A price cannot be responsibly stated yet.
11. Customer requests a price range
The team needs to confirm [scope factor] before giving an accurate range. I can collect that now: is this [option A] or [option B], and when are you hoping to have the work done?
Use when: A category has distinct job paths.
Why it works: It explains why more information matters instead of dodging the question.
Follow-up templates
12. First follow-up after an incomplete reply
Hi [First name]—we can still review your [service] request. What ZIP code is the [property/job] in? Once I have that, I can confirm whether it belongs with our team.
Use when: The customer did not answer the first qualifying question.
13. Follow-up after qualification
Thanks—we have the key details for your [service] request. Is [phone number] the best number for the team to use, and is [time window A] or [time window B] better for a callback?
Use when: The request fits and the next step is a human callback.
Guardrail: A callback window is not an appointment window. Keep the wording accurate.
14. Final close-the-loop message
I don’t want to keep messaging if your plans changed. If you still need help with [service], reply with [single missing detail] and we can continue. Otherwise, no response is needed.
Use when: An approved follow-up sequence is ending.
Why it works: It is respectful, creates a simple re-entry point, and avoids pressure.
Disqualification and handoff templates
15. Respectful out-of-area or wrong-service response
Thanks for the details. We do not currently provide [requested service] in [location], and I don’t want to mislead you about coverage. You may want to search Google Local Services for a provider that lists [correct service/area].
Use when: The request is clearly outside approved scope.
Guardrail: Do not claim Google instructed you to decline the request. Google’s platform policy says providers choose their own customers.
16. Qualified human handoff
Thanks, [First name]. I have your request for [service] at [location], needed [timing], plus [important detail]. I’m sending this to [team/role] now. They’ll contact you at [phone number] to confirm availability and the next step.
Use when: Required intake is complete.
Why it works: It summarizes what was captured and sets an accurate expectation.
Turn manual templates into a flexible conversation flow
A static script asks every lead the same questions. A useful intake tree changes based on the answers.
Start with this structure:
- Known service fits? If no, decline accurately. If uncertain, ask one clarifying question.
- Location fits? If no, close the loop. If yes, continue.
- Urgency changes routing? If yes, collect the approved triage detail and escalate.
- Category-specific requirement met? Ask only the question needed for that service.
- Contact and timing complete? Confirm the callback information.
- Qualified? Send the context to the correct human owner.
For the complete channel workflow and measurement model, read Google LSA Message Leads: How They Work and How to Convert More.
Five template mistakes that lose replies
Asking for information Google already supplied
If the request includes a name, ZIP code, phone number, and job detail, do not restart intake from zero. Confirm the known information and ask only for what is missing.
Sending a six-question wall of text
One or two related questions per turn feels conversational and creates more chances to clarify ambiguous answers.
Pretending automation is a dispatcher
Never confirm a booking, technician arrival, price, or coverage unless the responding system has verified authority and current data to do so.
Moving to a phone call too early
“Call us” transfers all the effort back to the customer. Collect enough context to make the callback worth answering.
Following up without adding value
Replace “just checking in” with the one missing question, a clear next step, or an easy choice.
Why fixed templates stop scaling
Templates become difficult to maintain when several services, locations, client accounts, and exception paths are involved. At minimum, an intelligent response system should understand:
- Business name and client account
- Requested service
- Supported and excluded services
- Service area
- Business hours
- Intake questions by job type
- Qualification criteria
- Handoff destination
- Follow-up limits
- Whether a person has taken over
That is the difference between selecting canned replies and using an AI agent for operational message automation.
LeadUp’s Google LSA autoresponder does not select from the templates in this guide. Its AI agent interprets each lead’s message and the conversation so far, generates context-aware replies using the individual business’s services and rules, collects missing details, qualifies the opportunity, follows up, and delivers the complete context to a team or CRM. A person can pause the agent and take over when judgment is needed.
Review your templates with real conversations
Every month, inspect at least 20 message threads and ask:
- Which opening message earned the highest customer reply rate?
- Where did customers stop responding?
- Which question was repeatedly misunderstood?
- How many conversations ended before service and location fit were known?
- How many qualified handoffs received a timely human response?
- Which statements required a correction by the sales or service team?
Change one part of the intake flow at a time. Measure engagement, qualification completion, qualified handoffs, and booked jobs—not response speed alone.
Final takeaway
For a manual team, an LSA template should remove friction while preserving judgment. Confirm what the customer already said, ask the smallest useful question, and hand off a complete summary without inventing promises.
Use the 16 replies above as training examples or manual starting points. When the possible situations outgrow a template library, a context-aware AI agent can adapt the same conversation principles to the individual lead without forcing every exchange through fixed copy.