Google LSA Updates to Message Lead Callbacks

Google is changing how phone-based follow-up works for message leads in Local Services Ads (LSA) across the United States and Canada. If your business responds to LSA message leads by phone, this update affects how those calls get tracked, and potentially how your responsiveness and ranking are measured. Today, when a consumer submits a message lead and shares a phone number, businesses call that number directly. Under the new system, Google replaces the consumer’s number with a Google forwarding number and a unique extension code tied to that lead. To reach the consumer, you’ll dial the Google forwarding number and enter the extension code found in the LSA dashboard. Google then connects the call to the consumer’s real number, similar to how rideshare or food delivery apps mask a customer’s number from a driver. This lets Google connect both the inbound and outbound legs of the conversation to the same lead, tracking the full engagement. There is one important exception to note, however. If you call back from the same phone number that received the original SMS lead notification, the extension code isn’t required. Google recognizes that number automatically.

Why Google Is Making This Change

Historically, Google had no visibility into what happened after a lead was delivered. It couldn’t tell whether a business called back, or how the conversation went. By routing calls through its own forwarding infrastructure, Google can now measure call activity, such as whether a call connected and how long it lasted, as a signal of lead responsiveness. The stated goal is to use that signal to improve future lead quality and better distinguish genuinely valuable leads from low-intent calls. It’s part of a broader shift toward a more complete, closed-loop tracking system within LSA. It’s also worth noting that Google has confirmed that it’s related to tracking call duration only, not recording or reviewing call content.

Rollout Timeline

The change is already live for leads managed through LSA Provider Web. In the next few weeks, it will extend to the Leads API and webhook integrations, which is how many CRMs and call-tracking platforms receive lead data today. So what does this mean for your business? First, the most important adjustment is a small one with real stakes. When returning a message-lead call, use the Google-supplied phone number and extension code from the LSA message itself, not the number the customer typed in. That tracking number is what tells Google you followed up. Call the consumer’s personal number directly instead, and Google has no way to see it, which can make it look like you didn’t respond even if you did. Here are a few other things to know:

• Calling back from the same number the SMS lead came in on skips the extension-code step entirely.
• No action is required to turn this on. Google is rolling it out automatically to all LSA advertisers using message leads.
• If your call tracking, CRM, or routing tools pull lead data via the LSA Leads API or webhook, expect the phone number field to change format once Google extends this update to those channels. It’s worth checking with your provider to confirm they can handle the new forwarding number format.
• Done correctly, this setup gives Google a full picture of the conversation, which should translate to more accurate responsiveness scores and reporting, including how quickly leads were followed up on and how many converted into calls.

A Note for Businesses Using Third-Party Call Tracking

If you use a third-party call tracking platform (Telmetrics, Marchex, CallRail, and similar) and that provider’s tracking number is registered as your business number in LSA, this update plays out slightly differently. The caller-ID recognition shortcut should still apply. If you call back from your registered tracking number, Google should skip the extension-code step the same as with any other registered number. However, the callback itself, dialed through Google’s forwarding number and extension, is technically an outbound call. Most call tracking platforms are built to log calls arriving on a tracking number, not calls placed out from it, so this leg of the conversation likely won’t show up in your call tracking reporting, even though Google is measuring it on its end. The call will still connect normally for you and the consumer. The gap is in visibility: your tracking platform’s dashboard may not reflect message-lead callback activity the way Google’s own lead reporting will. If that reporting gap matters for your attribution or QA process, it’s worth confirming directly with your call tracking provider how they plan to handle it.

In Summary

This update gives Google more visibility into what happens after a message lead lands, and it changes the mechanics of how businesses should follow up. The fix is simple: always call back using the number and extension code in the LSA message, not the consumer’s raw number, and check in with any call tracking or CRM integration once the API and webhook rollout reaches your systems. Getting this right protects your responsiveness score and keeps your reporting accurate as Google continues building out LSA’s tracking capabilities.