If your agency manages Google Local Services Ads for five or more businesses, a client question about results can turn into a search through account screens, call notes, and CRM records. A report showing lead totals helps, but the owner still wants to know which inquiries became booked work.
When comparing LSA reporting software for agencies, start with the decisions your team needs to make. Can you explain a change in lead costs? Identify an unanswered inquiry? Show how a booking was attributed? Establish whether lead feedback actually reached Google?
Use the checks below to evaluate those questions before committing your client portfolio to a tool.
Start with a report you can reconcile
Google's native reporting includes charged leads, spending, credits, and lead-type breakdowns. These provide a starting point for checking a third-party report. Google explains the available reporting fields here.
Ask the vendor to select one authorized client account and a completed reporting period, then show the same figures in Google and the proposed software. Check the account identifier, date range, time zone, filters, and last successful refresh.
Have the vendor explain any differences rather than dismissing them as a sync issue. A credit may be recorded after the original charge. A report may group leads by creation date while another screen shows a different reporting basis. The explanation should be specific enough for your account manager to repeat to a client.
Also establish whether the spending figure already includes credits. Subtracting credits again can make a report understate cost. Keep unresolved differences visible until someone reconciles them.
Require evidence behind booked jobs
Define what your agency means by a booking before comparing conversion rates. An appointment request, a confirmed estimate, a scheduled job, and completed paid work are different outcomes.
For each booked job, the reporting workflow should let your team identify:
- The originating lead and the correct client account.
- The outcome recorded by the client or their system.
- When the outcome changed and where the evidence is stored.
- Any cancellation, duplicate, or later correction.
A call summary saying that someone wants an estimate is useful context, but it does not establish a confirmed booking. Ask how the tool handles uncertain outcomes and whether your team can correct a mistaken classification.
Agree on the denominator for every metric. For example, cost per booked job can use reconciled advertising spend divided by attributable booked jobs from the same lead cohort. Do not silently divide this month's spend by bookings generated from older leads. If you report period activity instead, label it clearly.
Where the client has not supplied booking or revenue data, show that information as unavailable rather than zero. That keeps an incomplete handoff from looking like poor campaign performance.
Separate CRM status from Google lead feedback
Three records can describe the same inquiry: the agency's internal notes, the client's CRM status, and feedback submitted to Google. They serve different purposes.
A CRM tag called “Booked” does not, by itself, establish that anything was sent to Google. Similarly, a lead-quality rating does not prove that revenue was recorded or that an offline conversion was imported.
Google documents a dedicated lead-feedback method and a field indicating whether feedback was submitted. That is a specific integration capability, not proof that every product offering a Google connection implements it. See Google's Local Services API guidance.
If feedback is part of the software proposal, request a demonstration of the complete path: the source lead, the approved rating, the submission result, and any failure that requires attention. Ask separately about booking updates or conversion imports. “Syncs with Google” is too broad to answer these questions.
Keep lead quality and credits distinct
An inquiry can be a poor sales fit without qualifying for a credit. Google's current guidance says it no longer supports credits for “job type not serviced” or “geo not serviced” leads. It also lists category and regional exclusions. A feedback submission should never appear in a client report as money recovered unless the credit is actually recorded. Read Google's automated lead-credit guidance.
Ask the vendor to show separate fields for the agency's assessment, submitted feedback, and Google's recorded charge or credit status. A client should be able to understand which conclusion came from your team and which came from Google.
Test the agency workflow as well as the chart
Before buying, have the person who prepares your client reports complete this short evaluation:
- Open the intended client account without exposing another client's information.
- Reconcile one reporting period against the source records.
- Trace a reported booking back to its evidence.
- Identify an unanswered lead and who owns the next step.
- Find a failed or incomplete synchronization.
- Produce the client-facing output and inspect it before delivery.
Confirm which actions are available today, which require manual work, and which are proposed features. Ask about exports, reporting access after cancellation, and any separate charges for accounts, users, or integrations.
Record the time your team spends completing the test. Compare it with your existing process instead of relying on a generic time-saving claim.
Bring your reporting questions to LSA Command
The best next step is a walkthrough built around the questions your clients actually ask. Start with LSA Command's lead performance reporting overview, then ask to review your required fields and workflow before deciding on fit.
If you manage five or more businesses, book an LSA Command agency walkthrough. Bring one client's current reporting workflow, your CRM, and the question your reports struggle to answer. Use the session to assess fit and confirm the setup your agency would need, without sharing passwords or unnecessary customer details.