Google LSA Leads: The 60-Second Response Playbook
Local Services Ads leads are the most expensive calls you'll get — and Google watches how fast you answer. The 60-second response protocol that converts the lead and protects your ranking.
System 2 from the Leveraged Owner Starter Pack
Your phone rings with the LSA call — the Google Local Services Ads lead you paid a premium for, the homeowner who tapped "call" on your Google-guaranteed listing. It rings four times. You're under a house. It goes to voicemail. Google logs the unanswered call, the homeowner calls the next listing, and your LSA ranking quietly slips — because Google's algorithm noticed you don't pick up. LSA leads don't just cost money. They grade you.
This is part of Pillar A: Capture Every Lead — the LSA-specific companion to the complete missed-call text-back setup guide. System 2's speed discipline matters everywhere; on LSA it's existential.
Why LSA leads are different
- You pay per lead, not per click. Every LSA call or message costs you whether or not it becomes a job. An unanswered LSA call isn't a missed opportunity — it's money spent for nothing.
- Google tracks responsiveness. LSA's ranking factors include how reliably you answer and how quickly you respond to messages. Slow or missed responses don't just lose the lead — they lower your position for the next lead. It's a compounding penalty.
- The customer is comparison-shopping by design. The LSA screen shows multiple providers. The homeowner's behavior is: call one, no answer, call the next. You are literally lined up next to competitors, and the first to pick up wins. The mechanism backs it: a homeowner who reaches a real responder stops dialing down the list.
- Message leads have a response clock. LSA message/chat leads come with Google's response-time expectations visible to the customer. A slow reply is visible slowness.
The 60-second protocol (the target state)
For LSA, "within 5 minutes" is the floor — the ceiling is 60 seconds. Here's the protocol:
- LSA calls ring differently. Configure your phone system to announce LSA calls distinctly ("Google Local Services call") or route them to a priority ring group. The person answering must know this call costs money and grades us — that knowledge changes how fast they move.
- Answer live whenever humanly possible. LSA callers chose "call" — they want a human. The answering script is short: "[Business Name], this is [Name] — how can I help?" No phone tree, no hold, no "let me transfer you." Every second of friction is a hang-up risk.
- Missed LSA call → instant text-back in under 60 seconds. The missed-call text-back (System 1) is mandatory infrastructure for LSA. The text must identify the Google connection: "Hi, this is [Business Name] — sorry we missed your call! How can we help?" Speed here partially offsets the miss — and Google's message-response tracking sees the engagement.
- LSA message leads → reply within minutes, by text. The reply template below. Then call within 15 minutes if they don't respond to the text — the call converts message leads at multiples of text-only.
- Log every LSA lead in your CRM. Manually if needed — LSA leads that live only in the LSA app don't enter your follow-up sequences. The 5-minute response wins the call; the CRM entry wins the follow-up if they don't book immediately.
The LSA scripts
Missed LSA call text-back (under 60 seconds):
Hi, this is [Business Name] — sorry we missed your call! We saw you found us on Google. What can we help you with today? Reply here or call us right back at [number]. Reply STOP to opt out.
LSA message-lead reply:
Hi [Name], thanks for reaching out through Google! This is [Your Name] with [Business Name]. I can help with [their issue]. Are you available for a quick call now, or is there a better time in the next hour? Reply STOP to opt out.
The live-answer open: "[Business Name], this is [Name] — how can I help?" Then the booking questions immediately. LSA callers are ready to book — don't make them sell you on taking their money.
Protecting your LSA ranking (the operational side)
- Dispute invalid leads. LSA lets you dispute leads that weren't real opportunities (wrong service, spam, out of area). Dispute them — you shouldn't pay for them, and they pollute your response metrics. Review the LSA app's lead list weekly; disputing is a 5-minute habit that directly cuts cost.
- Keep your hours accurate. Google penalizes unanswered calls during your stated business hours. If you're not really answering Saturdays, don't claim Saturday hours — the ranking penalty for missed calls exceeds the visibility gain.
- Respond to LSA reviews. The LSA profile carries its own reviews — respond to all of them. Review count and responsiveness feed the ranking.
- Track cost per booked job, not cost per lead. LSA's per-lead cost looks high until you measure what matters: booked jobs per dollar. A $40 LSA lead that books at 50% beats a $12 lead source that books at 5%. Run your own numbers.
The after-hours LSA problem (and the fix)
LSA leads arrive 24/7 if your hours say so. The after-hours protocol:
- After-hours LSA calls get the triage text-back — same System 6 mechanics, with the Google acknowledgment: "sorry we missed you…"
- First-thing callback list, LSA first. The morning callback queue is sorted by lead cost — LSA leads get called before website leads, because they're the most expensive and the most likely to have called a competitor overnight.
- Consider pausing LSA overnight if you genuinely can't respond until morning and the lead cost doesn't justify it. Paying for leads you'll answer 8 hours later — after the customer called three competitors — is the worst LSA spend. Test a month with overnight hours off and compare cost per booked job.
Worked example: the LSA turnaround
Example: a 3-truck plumbing shop spending ~$1,500/month on LSA with a 20% answer rate on LSA calls — most went to voicemail during jobs. Their fix:
- Set LSA calls to ring the owner's cell and the CSR simultaneously (priority ring), with the "Google Local Services" announcement.
- Installed the missed-call text-back with the LSA-specific script — every missed LSA call got the text within 60 seconds.
- Built the morning callback list sorted LSA-first.
- Started disputing invalid leads weekly.
- Result within two months: answer/text-back coverage on LSA calls went from 20% to near-total, disputed credits cut the effective spend, and — the compounding part — their LSA ranking improved as responsiveness metrics recovered, bringing more calls at the same budget.
The mechanism is the MIT/Oldroyd finding applied to a graded channel: responding within 5 minutes makes you ~100x more likely to reach the contact than after 30 minutes (HBR 2011) — and on LSA, Google is watching you do it.
Compliance note
LSA text-backs are automated texts: 10DLC business-texting registration (carrier registration for texts sent by software; 1–7 day approval, ~$15–$20 in fees) required, opt-out language included, and the first text identifies your business. LSA message replies through Google's system follow Google's terms; your follow-up texts follow TCPA (federal telemarketing law) rules — no marketing texts before 8am or after 9pm recipient's local time. General information, not legal advice.
Related guides in this series
The LSA playbook inside Pillar A: Capture Every Lead — System 2's speed discipline, System 1's text-back infrastructure, System 6's after-hours triage. Compare with the Thumbtack/Angi speed guide for the marketplace counterpart.
Get System 1 free: the complete Missed-Call Safety Net
The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.
See everything inside the AI Automation Starter Pack ($27, one-time) here: https://leveragedowner.com/starter-pack/
The done-for-you version
This post is System 2 from the Leveraged Owner Starter Pack — the done-for-you version with the full LSA response setup guide, every script, the dispute checklist, and screen-by-screen setup instructions for all 8 systems.
Stats: ~100x more likely to reach the contact within 5 minutes vs. 30 minutes — MIT/Oldroyd, HBR 2011.