Google Local Services Ads calls: numbers, routing and QA

Route and track Google Local Services Ads calls by pointing LSA to your own tracking number (a phone number you own for routing and reporting) inside a call-routing platform (software that forwards and distributes your calls). Set the LSA business phone to that number, then use your platform’s logs and recordings to measure outcomes. When you’re done, you’ll have one number per market, schedule- and state-based routing, recordings for QA, and clean reports your client can trust. Plan about an hour, including test calls.

How Google Local Services Ads calls reach you

Google shows a Google forwarding number (a number Google controls for attribution) to the searcher. When someone taps Call, Google forwards that call to the business phone you set in your LSA profile. If you make that destination a number you own, you control how and where the call rings. You can also record it with consent and see your own analytics alongside Google’s dashboard.

We’ll use a simple running example: a plumbing firm covering Phoenix and Tempe. On weekdays, calls ring a 3-agent desk. After hours, calls go to the owner’s mobile. On weekends, calls wait in a short queue (the caller waits on hold), then go to voicemail if no one answers.

Provision one tracking number per market or location

Pick local numbers that match each service area for reporting clarity and brand fit. Google still shows its own forwarding number to searchers, but it will forward to your tracking number. If you run more than one LSA profile or office, assign one tracking number per location. Local often feels closer for home services and legal. Toll-free can help national brands that want one identity across markets.

If your agents are in India, the Philippines, Thailand, Bangladesh, or Pakistan, get US numbers for each market and forward to your team’s phones, a SIP endpoint (an internet phone your team registers), or a browser softphone (a phone in the web browser). Place a quick test call from the US to confirm clear audio both ways and low post-dial delay (seconds from tapping Call to first ring). Keep each number exclusive to LSA so every call on it is from those ads. That makes reporting and disputes straightforward.

One short aside: CallFlow provisions US local and toll-free numbers from a prepaid wallet with no subscription.

Set it up step by step:

1. List your markets and profiles. Create one LSA tracking number per city or service area (e.g., Phoenix, Tempe). Label each clearly.
2. Choose local vs toll-free. For our plumber, pick a Phoenix and a Tempe local number. Reserve toll-free only if your brand needs it.
3. Point each tracking number to your current answering setup for now (desk, SIP, or mobile). This keeps service live while you add rules later.
4. In your LSA dashboard, open Settings > Profile > Phone number (menu names vary by country). Change the business phone to your new tracking number for that market. Google will still display its own forwarding number to searchers, but it will now send calls to your tracking number.
5. Make a short test call from a local area code to the tracking number directly. You’re testing delivery to your agents first. If international, also test from the US to your remote team.
6. Place a test through the LSA ad once Google updates the business phone. Confirm the call routes the same way as a direct call to the tracking number.
7. In your routing platform, name each number, enable recording (we’ll add consent next), and set a whisper (a short message your agent hears before connect) so agents know it’s an LSA call, like “Phoenix LSA.”
8. Document which LSA profile maps to which tracking number. You’ll use this map for reports and disputes.

Route by schedule, state, and capacity

Set business-hours and after-hours windows so calls reach the right person the first time. For weekdays, ring the desk for 20–25 seconds so an agent can catch it. If no one answers, set an overflow (where the call goes if no answer) to the next target or a short queue (the caller waits on hold). After hours, send calls to the owner’s mobile with a 25-second ring, then to voicemail. On weekends, try a 30-second queue before voicemail to catch late calls.

For state- or city-based crews, route by caller state (area code/region detection) so Phoenix jobs reach the Phoenix desk and Tempe jobs go to the Tempe desk. If you don’t serve a caller’s state, play a short message or send them to voicemail, then log the outcome in your CRM. For more options, see route calls by state.

Protect your team with daily caps and concurrent caps (max live calls per target). If the 3-agent desk is at two live calls, push the next call to the queue or to the owner’s mobile. When teams share load across markets, use weighted routing (send more calls to certain targets) or round-robin (rotate evenly). Keep the whisper short—“LSA Phoenix” or “LSA Tempe”—so agents greet callers with context.

If you’re building this fresh, start with a simple schedule and a single overflow, then watch the logs for a week. Tighten ring times and caps where you see missed calls or long waits. If you need a primer on hour windows and overflow order, skim schedule-based call routing.

Record, label, and review LSA calls for QA

Turn on call recording only with a consent prompt that fits your country or state. Many US states require all-party consent; several countries have their own rules. Add a brief pre-connect announcement (“This call may be recorded for quality”) or train agents to request consent at the start. For a quick guide, see US state call recording rules for businesses. Also review Google’s Local Services policies on phone leads and recordings in their Help Center: Google Local Services Ads Help.

Use clear number names and campaign labels you can filter in reports, and record outcomes in your CRM. Simple, consistent outcomes work best: “Booked,” “Reschedule,” “Not service area,” “No show.” Train agents to log the outcome in your CRM before they hang up if they didn’t book, or have the dispatcher update it after the job is set.

During launch week, run spot checks with live monitoring on active LSA numbers. Listen for greeting quality, hold times, and whether the whisper helped. If agents miss calls right before closing, shorten the desk ring timer and increase the queue to catch late calls. If caller ID looks wrong, use real-time logs to check what caller ID came through each leg (each hop in the call path). That trace shows whether you need a routing change or a number swap.

Report outcomes your client or manager will trust

Send scheduled daily or weekly email summaries filtered to just your LSA numbers. When you send scheduled reports, set or export them in the client’s timezone if your platform allows it, so timestamps match their day. Include links to recordings for calls where you have consent. If you manage many locations, one email per market keeps the team focused on their own queue. You can automate this; see scheduled call reports.

Track a short scorecard that busy managers read. Five lines are enough:

• Answer rate (all LSA calls that reached a person)
• First response time (seconds from ring to answer)
• Talk time (median is fine)
• Recordings reviewed (count this week)
• Qualified leads and bookings by market

Show where caps hit and when after-hours volume spiked. If your Phoenix desk hit its concurrent limit between 4–5 pm, that’s a staffing note for next week. Keep rejection or dispute notes aligned with the LSA dashboard so billing, refunds, and QA tell the same story.

Multi-buyer and pay-per-call from LSA

If you resell Local Services Ads phone leads, set up buyers (targets) with their own schedules, states served, and duplicate-caller rules. Pick routing that matches your contracts: priority routing for a top buyer, or a weighted split across several. Always set daily and concurrent caps, a recording consent path, and a clean overflow to a house queue or voicemail to avoid dead ends. For a step-by-step, see set up pay-per-call.

Give each buyer a portal view with only their calls. Send buyer-specific scheduled reports with recordings when you have consent. Keep a short whisper per buyer (“LSA Phoenix — Buyer A”) so agents can greet by brand when needed. If you get Google Guaranteed calls during peak times, raise caps on your best-performing buyer first, then allocate the rest by weight.

Launch it and verify in one day

Do three checks:

• Place two live test calls to each tracking number from different area codes (e.g., Phoenix and Tempe). Confirm the right desk answers during business hours and the owner’s mobile after hours. If your team is abroad, confirm audio is clear both ways.
• Trigger at least one overflow (let the desk ring out) and one weekend queue test. Confirm the ring timers you set match what you hear, and that calls land in voicemail with the right greeting.
• Open your real-time logs. Confirm caller ID, recording status, and which route was taken. Spot-check a recording to ensure your consent prompt captured.

From here, watch the first week’s reports and adjust caps, schedules, and whispers. Keep numbers dedicated to LSA so your attribution stays clean as you add more markets.

If you want to stand this up fast, you can get a number and start routing in minutes with CallFlow. Or talk through edge cases with our team at Contact.