TL;DR
Yes. A call an AI receptionist picks up is an answered call, not a missed one, and missed calls are what Google says may hurt an ad's responsiveness. No Google page treats an automated pickup as a miss. Get the current handling from the client's Local Services Ads representative in writing, and protect the first minute of every call.
Why agencies ask before they deploy
When an agency puts an AI receptionist on a client's line, the compliance questions arrive before the performance questions. Does Google score the pickup? Can the assistant text the caller afterward without a consent problem? Does the client need a recording notice? What happens when a caller asks whether they're talking to a bot? And can this go live without changing the number printed on the client's trucks?
Most have plain answers once you separate what the platform does from what the client is responsible for. This page works through each one for agencies putting Voice Assist for agencies on client lines, and every answer ends with that split.
Businesses with a dedicated or automated response system convert 70% or more of inquiries, compared with 40% to 50% for businesses without one.
What Google's ranking page actually says
Google's help page on how Local Services Ads are ranked lists the factors that decide "how likely your ad is to result in a lead." One of them reads: "Your responsiveness to customer inquiries and requests: Missed calls may negatively affect your responsiveness." That's the whole of what Google publishes on the point. The page doesn't define how a call is judged answered, and it doesn't mention automated pickups one way or the other.
Two things follow from that. First, a call that rings out on a client's Local Services Ads number is a missed call by any reading, and Google says missed calls can hurt. Second, a call an assistant picks up is answered, and no Google page carves out automated pickups as a separate category. The lead rules already account for automated answering, since the how leads work page describes calls that reach an automated phone menu and still counts them as leads once the caller engages. So the answer an agency can stand behind is yes, with its reasoning shown. An answered call isn't a missed call, the client's LSA representative can confirm the handling in writing, and the way to protect the ranking either way is to get the call picked up quickly and handled well.
Google uses a few terms on these pages that get blurred in agency conversations, so it's worth pinning each one to Google's own wording.
Ranking. Google's ad rankings page, quoted above, lists two things: the bid, and how likely the ad is to result in a lead. The second one is where responsiveness, relevance, message and booking options, and profile quality sit, and missed calls land in responsiveness.
Responsiveness. The factor Google names, and the only ranking factor the page ties to missed calls. A client whose line rings out after 5pm is building that record one evening at a time.
Valid lead. Google's how leads work page counts a phone lead when you answer the call, or call the customer back and speak with them. It also charges for a call you missed during business hours if the caller stayed on the line for more than 20 seconds. So a client can pay for a lead nobody spoke to, and the difference is whether they also got the job.
Lead credits. The same page says charged leads are reassessed over time and may be credited automatically if they turn out to be low quality. That's the mechanism behind "disputing" a lead, and it's why the recording of every call matters.
Two-party consent. A state rule rather than a Google rule. In some states every person on a recorded call has to be told it's being recorded, which is what the greeting is for.
TCPA, 10DLC, and TCR. Three layers on texting. The Telephone Consumer Protection Act is the federal law on consent for automated messages. 10DLC is the carriers' registration system for business texting from ordinary ten-digit numbers, and The Campaign Registry runs those registrations. Carriers treat that texting as consent-based, which means a business texts people who asked to hear from it and honors STOP when they change their mind.
The questions agencies ask, one by one
Does an AI pickup count as an answered call for LSA?
Yes. An answered call isn't a missed call, and missed calls are the factor Google names. The ranking page doesn't single out automated pickups one way or the other, and the lead rules already handle calls that reach an automated menu, so there's no published basis for treating an assistant's pickup as a miss. Still get the current handling from the client's Local Services Ads representative in writing for the account file, because unpublished handling can change without an announcement. The alternative on most client lines is voicemail, which is a missed call by any reading.
Treat the first minute as the thing that matters regardless of how Google scores it. A caller who reaches an assistant that talks over them or can't get them to a person will hang up and dispute the lead. A pattern of that hurts a client with or without a ranking penalty. By default, Voice Assist answers the calls routed to it and transfers to a person on request, and the disclosure lives in the greeting the client approves, with the demo greeting showing the pattern. The client owns the greeting, the LSA account, and the conversation with Google about how pickups are scored.
Can the assistant text the caller afterward, and is that a consent problem?
Automated texts in the United States sit under the Telephone Consumer Protection Act and its rules on consent, and business texting also runs through 10DLC registration, which lets carriers block unregistered or spam-like traffic. A follow-up text to someone who just called the business stands on different footing from a marketing blast to a purchased list. Even so, consent language, an opt-out path, and registration still apply, and the rules change. Have the client's counsel review the texting flow rather than taking any vendor's word for it.
By default, Voice Assist replies to inbound texts and sends texts within a conversation the caller started, and it can't send at all until the account's number is registered under 10DLC. CallRail's texting setup guide shows the registration status on the Voice Assist page and a required legal disclaimer the assistant sends to new contacts. The client is responsible for consent capture and for the wording of any text that goes beyond the conversation the caller began.
Does the client need a recording notice?
Call recording law is set state by state, and some states require every party's consent to record. Businesses that record calls typically play or speak a short notice at the start, and an AI receptionist that records should do the same wherever the client operates. Confirm which states the client's callers are in, adopt the strictest applicable standard, and put the notice in the greeting.
By default, Voice Assist records calls and produces a transcript and summary, which is what makes it useful as an audit trail. The notice lives in the greeting. CallRail's call flows guide explains that the greeting set up for the assistant is copied into the Voice Assist step of each call flow and can be edited there. The wording can match the strictest state the client serves. The client decides which recording notice their callers hear and whether recording is on for a given line, and their counsel confirms the state requirements.
What happens when a caller asks "are you a bot?"
The answer should be yes, said plainly, and the assistant should already have said so in its first sentence. Callers who find out mid-conversation that a friendly-sounding "Lucy" is software feel tricked, and that reaction, rather than the fact of automation, is what produces hang-ups and complaints. An assistant that discloses up front, answers the question honestly when asked, and offers to connect the caller to a person keeps the call.
By default, Voice Assist speaks the greeting the client approves, and the agency demo shows what that greeting should sound like: "Hi, this is Sparkle Marketing Group. I'm Lucy, a virtual assistant. How can I help?" Transferring to a person is part of the plan. The client chooses the assistant's name, writes the disclosure into the greeting, and approves what it's allowed to say about the business.
Can we deploy without changing the client's published number?
Yes, in the way most businesses already route calls. The client's existing number stays on the website, the trucks, and the Google Business Profile. Calls to it forward to the assistant under the conditions the client sets, such as after hours or when the line is busy. Nothing the customer sees changes, and the client's staff keep answering during the hours they choose.
By default, Voice Assist takes the calls that are routed to it. The same call flows guide covers the three usual patterns: a schedule step for after hours, an overflow step that hands the call over after a set ring time, and an always-on mode that answers every call. CallRail recommends keeping that ring time to fifteen seconds or fewer. The client decides the forwarding rules and which hours the assistant covers.
What should the client tell Google, and when?
Ask the client's Local Services Ads representative two things: how an automated pickup is treated for responsiveness, and whether any lead capture on the client's side changes when an assistant answers. Get both answers in writing and keep them with the account notes, because the rule may change.
What this means for the agency
Compliance questions are usually a client's way of asking whether they'll get in trouble for letting an agency put software on their phone. The answers above reduce to a short list the agency can commit to. Disclose in the first sentence, transfer on request, record with the right notice, text only within a conversation the caller started and with counsel's sign-off, and forward the existing number rather than replacing it. An agency that can say those five things, and show the recordings that prove them, has answered the compliance conversation before the client's lawyer joins it.
There's also an upside hiding in the same deployment. If a client schedules campaigns around the front desk, their ads stop at close on the logic that nobody can answer after that. A line that's answered around the clock removes the constraint. The client can keep campaigns running into the evening while competitors who kept the old logic go dark. Every one of those calls reaches something that picks up instead of adding to the client's missed-call record.
What to look for in any AI receptionist you put on a client's line
Whatever platform you use, check for these before it touches a Local Services Ads number.
- Disclosure in the first sentence, not buried in a menu.
- A transfer path that works when the caller asks for a person, with a clear fallback when nobody picks up.
- Recording, transcript, and summary for every call, so you can prove what was said if a lead is disputed.
- Texting that stays inside the conversation the caller started, with an opt-out.
- Spam and robocall filtering before the call counts against anything.
- Lead source captured on the call, so the booked appointment can be traced to the ad that produced it.
"We told our clients to first try Voice Assist out on weekends and after-hours. That way, they don't have to change their current solution, and they can easily evaluate how it performs."
– Scott Berry, President, MarketCrest Source: CallRail customer story: MarketCrest
How Voice Assist handles the compliance questions
Voice Assist is CallRail's AI receptionist, sold on its own at voiceassist.callrail.com and set up per client. The plan lists at $95 a month on the Voice Assist pricing page, with a 14-day free trial and no credit card to start. It answers around the clock, asks the intake questions the client approves, books appointments, transfers to a person, texts back, and saves a recording, transcript, and summary for every call. On the questions above, its defaults are the ones agencies want, and each one has a public page behind it.
1. The LSA question. A call the assistant picks up is an answered call, and CallRail's unanswered calls report definitions treat it that way: a call answered by a person or an automated system counts as answered, and only voicemail and abandoned calls count as missed. Google publishes no separate rule for automated pickups, so the client's report shows answered calls and the representative's written answer covers the scoring. File it with the account notes.
2. Disclosure and transfer. The agency demo opens with "I'm Lucy, a virtual assistant," and the client approves the exact greeting. The call flows guide describes a Human Request intent. When the caller asks for a person, the assistant hands off to the forwarding number the client sets, with a voicemail step as the fallback if nobody picks up. A lead screening branch can send a qualified caller straight to a person.
3. Ring time. CallRail's Voice Assist FAQ explains that calls can show as unanswered when the caller hangs up during the ringing phase, before the assistant picks up, and it recommends shortening the ring duration. On an LSA line, that caller is a miss on the client's report and a missed call by Google's own wording.
4. Recording notice and texting. The greeting in the Voice Assist step carries the recording notice, and texts go out only after 10DLC registration and only with the disclaimer to new contacts, as described above.
5. Data. The agencies page states that the client's conversations stay the client's and that every call and transcript is encrypted in transit and at rest. It also lists SOC 2 Type II and the ISO standard for AI management systems. The same support FAQ states that CallRail does not allow the language model to use Voice Assist call data to train its models, which answers the question a client's lawyer asks second.
Voice Assist does all of that without a Call Tracking subscription. Agencies that already run Call Tracking on the client's Local Services Ads number get one more thing. The answered call sits next to the ad that produced it, so the booked appointment traces back to the listing in the same report the client already reads.
Where it's lighter: Voice Assist doesn't give legal advice, and neither does this page. It also can't quote you a Google rule for how an automated pickup is scored, because Google hasn't published one, which is why the written answer from the client's Local Services Ads representative belongs in the account file. The client's counsel confirms consent language and recording notices for the states involved.
The LSA line audit, before go-live
Run these on the client's Local Services Ads number the week before the assistant takes its first call. Each takes minutes, and together they're the proof you hand the client's compliance contact.
- Hours match. The business hours in the client's LSA profile match the hours in the call flow, so the assistant covers everything outside them and nothing Google expects a person to answer.
- Ring time. The overflow step hands over within a few rings, because a caller who hangs up while it's still ringing is a miss on the client's report and a missed call by Google's wording.
- Disclosure and transfer test. Call the line and confirm the first sentence says it's a virtual assistant, then ask for a person during hours and again after close, time the handoff, and check the fallback.
- Recording notice. Confirm the greeting states the call is recorded, in the wording the client's counsel approved.
- Texting status. Confirm 10DLC registration shows complete on the Voice Assist page before any text goes out, and read the disclaimer the assistant sends.
- Dispute file. Agree where recordings go when a lead looks invalid, so the credit request has evidence.
- The written answer. File the LSA representative's answer on how an automated pickup is scored, with the date.
- Week one review. Book a thirty-minute call to listen to five recordings together before expanding the hours.
Frequently asked questions
Q: Is missed call text back legal?
A: Sending an automated text to someone who just called a business is generally permitted in the United States. The sending number has to be registered under 10DLC, and the message has to give the recipient a way to opt out. Registrations get rejected and the rules shift, so the client's counsel should review the flow. A text after a missed call also doesn't undo the missed call itself, which is the LSA problem in the first place.
Q: Do Local Services Ads calls going to voicemail hurt the client's ranking?
A: Google's help page names responsiveness as a ranking factor and says missed calls may hurt it. It doesn't publish how much, so treat every call that rings out as a cost, both the lead the client paid for and the responsiveness signal.
Q: Do two-party consent states apply to an AI receptionist that records?
A: Yes, in the same way they apply to any recorded business call. Confirm the states the client's callers are in, adopt the strictest standard among them, and put the notice in the greeting. The client's counsel makes the final call on wording.
Q: How does this connect to the answer-rate problem agencies keep running into?
A: The compliance questions and the answer-rate questions are the same deployment seen from two sides. Once the assistant is live, the client's missed calls turn into answered, qualified, and booked calls on a report, and that report is what settles the lead-quality conversation with the client.
Start with the questions, then the line
Get the LSA answer from the client's representative in writing, have counsel look at the texting and recording flow, and pick a client line that rings out after hours. Once those three things are done, the rest is a forwarding rule and a first week of recordings to review together. If you'd rather hear the defaults before you put them in front of a client's lawyer, try Voice Assist free on a test line, no credit card required. Run the audit above against your own recordings first.
