A Local Services Ads lead is only worth what you paid for it if someone actually responds — fast. That makes it worth a few minutes to manage LSA lead notification recipients deliberately: who gets alerted when a call or message comes in, on what device, and with what backup if the first person misses it. Get this wrong and you pay per lead for calls that no one returns. This guide covers routing notifications so leads land with someone who acts.
Why notification routing is a speed-to-lead problem
Google weighs responsiveness, and the odds of booking a lead drop with every minute it waits. Notifications are the trigger for your whole response process: if the alert goes to an inbox nobody watches, or to one person who is on a roof, the lead sits. Managing recipients well is really about compressing the time between “lead arrives” and “human engages.”
Calls vs. message leads
Phone leads ring in real time, but message leads sit until someone reads them — and they decay quickly if ignored. That is why message-lead notifications especially need to reach a person who is watching and empowered to reply, not a general mailbox checked once a day.
How to manage LSA lead notification recipients step by step
- Find the notification/contact settings. In your LSA account settings, locate where lead alerts and contact details are configured.
- Set the primary recipient. Choose the person or role that owns first response — ideally someone reachable during business hours who can act immediately.
- Add backups. Include a second recipient so a missed alert has a fallback, not a dead end.
- Match channels to how people work. Ensure alerts reach the devices your responders actually watch during the day.
- Plan after-hours routing. Decide who — or what automated response — handles leads outside staffed hours.
- Test it. Send a test or watch the next real lead to confirm the right people are alerted quickly.
One note before you start: Google periodically redesigns the Local Services Ads dashboard and renames menu labels, so the exact wording of a button or the order of screens may differ from what you see here. Where a step depends on a specific control, we describe what it does rather than promise an exact label — if your screen looks different, check Google’s current Local Services Ads help center for the latest steps.
Routing patterns that work
| Setup | Good for | Watch out for |
|---|---|---|
| Single owner-operator | Solo trades | No backup if you are on a job |
| Primary + backup | Small teams | Define who acts when both are alerted |
| Dedicated intake person | Higher lead volume | Coverage during breaks and time off |
| Automated first-touch + human | After-hours, overflow | Automation must hand off cleanly |
The right pattern depends on your volume and staffing, but every good setup shares two traits: a clearly accountable first responder, and a backup so no lead depends on one person being available.
Avoid the shared-inbox trap
Routing leads to a general info@ mailbox that everyone can see but no one owns is a classic way to lose leads — each person assumes someone else has it. Assign a named owner. Diffuse responsibility is slow responsibility, and slow responsibility loses booked jobs and dents your responsiveness signal.
Keep it current
- Update recipients when staff change so alerts never route to someone who left.
- Cover vacations and sick days with a temporary backup.
- Periodically confirm alerts still reach the devices people actually watch.
- Review after-hours routing seasonally as demand and staffing shift.
Point notifications at accountable people, back them up, cover the after-hours gap, and revisit the list as your team changes. That is how you make sure the leads you already paid for actually get answered.
Write down who owns first response
The simplest safeguard against dropped leads is a one-line rule everyone knows: who responds first, and who backs them up when that person is unavailable. Post it where your team sees it. When responsibility is explicit, leads stop falling into the gap between “I thought you had it” and “I thought you did.” Pair that clarity with a quick monthly check that alerts still reach the right devices, and you close the most common leak in the whole funnel — the paid lead nobody answered.
Frequently asked questions
Who should receive Local Services Ads lead notifications?
A clearly accountable first responder who is reachable during business hours and empowered to reply immediately, plus at least one backup. Avoid routing leads only to a shared mailbox that no single person owns, which slows response.
Why do message leads get missed more than calls?
Phone leads ring in real time, but message leads sit until someone reads them and decay quickly if ignored. Message-lead alerts need to reach a person who is actively watching, not a general inbox checked once a day.
How do I handle LSA leads after hours?
Route after-hours notifications to whoever is on call or to an automated first-touch that acknowledges the lead and sets expectations. Silence outside staffed hours means paying for leads that go cold before anyone responds.