Google Local Services Ads message leads are easy to underestimate.
They can look less urgent than calls, but they reach people who may be contacting providers after hours, cannot talk on the phone, or want to compare options without repeating the same story. Google also says message leads typically cost less than phone leads.
The opportunity is not simply to reply. It is to move a short, incomplete request through a repeatable path:
first response → service fit → location fit → urgency → contact details → human handoff
This guide explains how that path works and how to improve it without turning every conversation into a robotic questionnaire.
What is a Google LSA message lead?
A message lead is a customer request sent through a Google Local Services Ad instead of a phone call or direct booking.
According to Google’s guide to managing Local Services Ads leads, a message request can include the customer’s:
- Name
- ZIP code
- Job details
- Phone number
Google routes the conversation through an anonymized alias, so your business email address is not exposed to the customer. New requests can generate email and SMS notifications, depending on your settings, and your team can respond from Google’s lead workflow.
Message leads are not available in every vertical. Google currently excludes health care verticals and tax specialists, so confirm availability for the category and market you manage.
How LSA message leads differ from phone leads
Treating messages like missed calls produces poor results. The two formats create different customer behavior and different operational demands.
| Dimension | Message lead | Phone lead |
|---|---|---|
| Customer effort | Low; the customer can send a short request asynchronously | Higher; the customer must be ready to talk |
| Information at arrival | Usually partial but written | Often richer, if someone answers and runs intake |
| Response risk | Sits unread or receives a generic reply | Rings out, goes to voicemail, or reaches an unprepared person |
| Best next action | Reply, qualify, then move to a call when useful | Answer, qualify, and define the next step on the call |
| Useful success metric | Qualified-conversation and handoff rate | Connected-call and qualified-call rate |
Phone leads can show stronger immediate intent, but that does not make every message lead weak. It means the business must create momentum that a live call creates naturally.
How Google’s messaging response time works
Google may display an estimated response time on your ad after you receive at least two message leads within 90 days. The visible estimates range from “a few minutes” to “one day.”
The calculation depends on the business hours configured in the account:
- If business hours are set, Google calculates average response time during those hours.
- If business hours are not set, leads received from 7 a.m. to 9 p.m. are considered.
- More recent leads receive more weight in the 90-day average.
This makes accurate hours an operational control, not profile housekeeping. Do not claim hours that no one—or no approved automation—can cover.
Google does not publish a universal response-time target that guarantees a ranking improvement. It does say that responsiveness to inquiries and average response time contribute to ad ranking and profile quality. See Google’s Local Services Ads ranking factors.
The five-stage message-lead workflow
1. Acknowledge the actual request
Avoid opening with “How can we help?” The lead already told you something. Reuse the known service or problem so the customer knows the reply is relevant.
Hi [Name]—yes, we handle [requested service] in [area]. I can help the team get the right details. Is this needed today, or are you planning for a later date?
That response confirms fit and asks one easy question. It does not dump a form into the conversation.
2. Confirm the two hardest filters first
For most local service businesses, those filters are:
- Is the requested job a service you actually perform?
- Is the property inside the service area?
Do not collect six fields before discovering that the job is outside your scope. Start with the facts that can disqualify the request cleanly.
3. Ask for the minimum information needed to route the lead
The right intake depends on the category, but a useful baseline is:
- Exact service needed
- Service address or ZIP code
- Urgency or desired timing
- One category-specific detail, such as equipment type or property type
- Best callback number and contact name, if not already reliable
Ask one or two related questions at a time. A long wall of questions makes the interaction feel like work and increases abandonment.
4. Define the handoff, not a vague promise
“Someone will get back to you” creates no expectation. A better handoff explains what happens next without promising availability, pricing, or an appointment that has not been confirmed.
Thanks—I have the service address, issue, and timing. I’m passing this to the service team now. They’ll use [phone number] to confirm availability and the next step.
If a human needs to take over immediately, the handoff should include the conversation, not just a phone number.
5. Follow up with new information
“Just checking in” is easy to ignore. A follow-up should reduce the effort required to continue.
We can still review this request. Is the property in [service area], and is [time window A] or [time window B] better for a callback?
Stop follow-ups when the customer declines, the request is clearly ineligible, or your consent and communication rules require it.
For situation-specific scripts, use these Google LSA message response templates.
How to tell whether message leads are actually low quality
Do not judge the channel from a crowded inbox. Classify at least 30 days of message leads into mutually exclusive outcomes:
- Qualified and handed off
- Qualified but unreachable after handoff
- Wrong service
- Outside service area
- Duplicate or repeat request
- Spam or solicitation
- Customer chose another provider
- Unknown because intake was never completed
That last category matters. “Unknown” is often an intake failure disguised as a lead-quality problem.
Use four rates to evaluate performance:
| Metric | Formula | What it reveals |
|---|---|---|
| Engagement rate | Leads that reply ÷ first responses sent | Whether the opening message earns a response |
| Qualification completion rate | Completed intakes ÷ engaged leads | Whether the questions are usable |
| Qualified lead rate | Qualified leads ÷ total message leads | Actual channel quality |
| Handoff-to-booking rate | Booked jobs ÷ qualified handoffs | Sales follow-through after intake |
Also track median first-response time. An average can hide a handful of overnight or weekend leads that waited many hours.
If wrong-service and out-of-area requests dominate, fix targeting and profile settings. If “unknown” dominates, fix response coverage and intake. If qualified handoffs rarely book, inspect the human follow-up rather than blaming LSA messaging.
Should you turn message leads off?
Disabling messaging can remove low-effort requests, but it also removes a contact option and reduces the number of ways a customer can reach the business. Google explicitly says enabling message or booking leads can increase the likelihood of receiving a lead, especially at night and on weekends.
Before switching messages off, run this sequence:
- Correct services, service areas, and business hours.
- Measure message leads separately from phone leads.
- Improve the first response and shorten intake.
- Add reliable coverage for nights, weekends, and busy periods.
- Compare cost per qualified lead and cost per booked job—not raw lead volume.
Turn the channel off only when the economics remain poor after the workflow is fixed, or when the team cannot support safe and accurate responses.
When LSA message automation helps
Automation is useful when speed and consistency are the bottleneck. It should do more than send “Thanks, we received your message.”
A production-ready responder needs business-specific controls for:
- Services and exclusions
- Service areas
- Intake questions
- Qualification rules
- Follow-up limits
- Human takeover
- CRM or team handoff
- Prohibited promises about price, availability, or booking
LeadUp’s Google LSA message automation replies, runs the intake conversation, qualifies the opportunity, and hands the complete context to a person. It is designed to collect scheduling preferences, not promise an appointment or make business decisions for the company.
A practical 7-day implementation plan
Day 1: Export or review the last 30 days of message leads and classify every outcome.
Day 2: Correct services, service areas, hours, and notification recipients.
Day 3: Write one default opening response and three exception paths: urgent, out of area, and wrong service.
Day 4: Reduce intake to the smallest set of fields required for a useful handoff.
Day 5: Define who owns each handoff and how quickly that person must act.
Day 6: Add a limited follow-up sequence for incomplete conversations.
Day 7: Review response time, engagement, qualification completion, and booked outcomes. Fix the weakest transition in the funnel.
Final takeaway
Google LSA message leads are not a smaller version of phone leads. They are asynchronous conversations that need their own response standard, intake design, and measurement.
Respond quickly, but do not stop at speed. Confirm fit, ask only what matters, preserve context at handoff, and measure the full path to a booked job. That is how messaging becomes a qualified-lead channel instead of another inbox.