Answer rate is a paid-visibility input, not only an operations metric

What the documentation actually says

Google's About ad rankings page for Local Services Ads sets out the inputs that determine whether an ad shows and in what position. Among them is a bullet naming a business's responsiveness to customer inquiries and requests, and directly beneath that bullet sits an explanatory sub-line: "Missed calls may negatively affect your responsiveness." A separate ranking factor, profile quality, is described on the same page as taking in "Your rating, number of reviews, average response time, use of high-quality images, the verification checks you have completed, and any other information about your business that may influence user preferences" ^[SRC-10]. Two things are worth noting precisely: the bullet and the sub-line are a bullet plus its explanation rather than one continuous sentence, and average response time is a named profile-quality input in its own right.

Where this sits in the stack

This is the paid ad-rank documentation for a specific Google product. It is not organic local SEO guidance, and reading it as such is a category error that will send an operator to the wrong remediation. The claim it supports is narrow and strong at the same time: inside the Local Services Ads auction, an operational property of the business — how its phone behaves — is documented as an input to placement. What is documented as an input here is not only the advertiser side of the transaction — bid, creative, landing experience — but a property of how the business itself behaves on the phone.

The chain, stated mechanically

1. An inbound call originating from a Local Services Ads unit enters the business's phone path.
2. The call connects to a CSR, or it abandons in queue, rings out, or lands in voicemail or an answering service.
3. Google's documentation names responsiveness among ad-rank factors and states that missed calls may negatively affect it, with average response time named under profile quality.
4. Ad rank governs whether the profile is shown, and in what position, for a given query and location.
5. Position governs how much charged lead volume the same budget produces.
6. The field service management platform records a change in lead volume, with no field on any record explaining why it changed.

Why it gets misdiagnosed

The chain crosses an ownership boundary at exactly the point where it becomes visible. Phone coverage is an operations concern, reported on staffing and hold-time surfaces. Lead volume and cost per lead are a media concern, reported in the ad account. Neither report contains the other's variable, so the same event produces two unrelated-looking symptoms: operations sees a busy week, media sees cost per lead drifting. Compounding it, where the booking-rate metric operations checks is computed over connected calls only, the very calls driving the paid signal are absent from the operational denominator — the mechanics of that are set out in what your booking rate denominator excludes and in the Home Services industry record.

Eligibility is a second, unrelated dependency that looks identical

Before responsiveness matters, the profile has to be serving at all. Google enumerates Local Services Ads categories for the United States, and the home-services trades appear on that list as named categories ^[SRC-08]. Google separately documents per-category business screening and verification: state or province license checks across Home Services, insurance requirements enumerated per category — certain categories requiring general and professional liability, others general liability only, others none — and an additional service professional check for electrician, garage door, locksmith, HVAC and plumber ^[SRC-09]. The systems consequence is that a lapsed license record or an expired certificate of insurance can change delivery. In a lead report, that produces the same shape as a responsiveness problem: fewer leads, no explanation. Any diagnosis that does not check document state first is guessing between two causes.

What you can verify from your own systems

• Pull answered and unanswered inbound counts by day, and by hour of day, from the phone system or call tracking platform — keeping after-hours calls in the series rather than filtering them out.
• Pull the Local Services Ads lead-delivery report and charged-lead counts for the same days, alongside budget and any budget changes made in that window.
• Pull whatever responsiveness and response-time indicators the Local Services Ads interface exposes for the profile.
• Line the series up on one timeline and look for shared windows — do the coverage gaps and the delivery dips start and end together, or independently?
• Overlay license and insurance document expiry dates on the same timeline, because a verification lapse produces a delivery change that is indistinguishable from a ranking change in the lead report.

What none of this proves

• Google publishes the factors, not their weights. Co-movement between answer rate and lead delivery cannot be read as the documented mechanism operating at any particular strength.
• Seasonality, competitor budgets, query mix and the auction itself move charged-lead counts independently of anything the business changed.
• The documentation describes ad rank inside Local Services Ads. It is not evidence about organic local pack ranking, and it should not be repurposed as such.
• A profile that slips on responsiveness and a profile that stops serving for a verification reason present the same way in a lead report until document state is checked.
• None of this establishes what an answered call would have been worth. A call log carries no job value, so the operational cost of a coverage gap is not derivable from the call data alone.

Building follow-up on top of a missed call

The obvious systems response — detect the missed call, message the caller, create a lead object — is sound as architecture and regulated as behaviour. Under 47 CFR 64.1200, autodialed or prerecorded telemarketing calls and texts require prior express written consent; revocation may be made by any reasonable method clearly expressing a desire not to receive further calls or text messages; and revocation must be honored within a reasonable time not to exceed ten business days ^[SRC-14]. Whether a given automated response is telemarketing is a legal determination for counsel, not a configuration setting. What is a configuration setting is whether consent state, revocation time and suppression status exist as fields on the contact record before the automation is enabled — and whether the missed call creates a durable object in the field service management platform at all, or only a notification somebody reads.

This lives at the seam between paid acquisition and intake, which is why it belongs with acquisition and conversion systems rather than with either the phone vendor or the media buyer alone. The series above come from exports only the operator can pull, so lining them up is internal work. A Revenue Scan covers the public half of it — the profile, the published numbers and what a prospective customer encounters — which is where a diagnosis starts, not where it finishes.