A pizza shop in a strip mall runs its main line on a Google Voice number the owner set up years ago on a personal Gmail account. It rings his cell, his wife's cell, and the counter cordless. It works. Then he signs up for a voice agent, points the forward at it, and the next fifty callers hear a ring, a pause, and dead air.
That's call screening doing exactly what it was designed to do, and it's the single most common reason a Google Voice forward to an automated answerer appears broken on day one.
What breaks and why
Google Voice sits between the caller and whatever devices you've listed as forwarding destinations. Before it bridges the two, it can play a prompt to the answering party asking who's calling or asking for a keypress to accept. A human hears that prompt and responds. Software does not. The agent picks up, hears a Google prompt instead of a customer, and the call never bridges.
The fix is to turn screening off for that destination. It lives in the Google Voice settings under call options, and it is per-account rather than per-number in the personal tier, so switch it off and then re-test with a call from a phone that has never called your restaurant before.
The second thing that breaks is voicemail. Google Voice has its own voicemail and it will happily grab a call the moment the forwarding destination doesn't answer fast enough. If your voice agent answers on the second ring and Google Voice's voicemail timer is short, you can end up in a race where some calls land in a Google voicemail box nobody checks. Push the Google Voice ring duration to its maximum and disable its voicemail greeting so the agent is the only thing that answers.
Third, do not leave the old destinations in the forwarding list once the agent is live. A number that rings the agent and the owner's cell simultaneously means both answer, the caller talks to whoever wins, and your order records develop holes. If you want a person in the loop, do it with an escalation rule inside the agent rather than with parallel ringing. That distinction is the whole subject of simultaneous ring versus AI answering.
The actual setup, in order
Do it in this sequence, on a slow afternoon, not during a Friday rush.
- Turn off call screening in Google Voice.
- Add the agent's number as a forwarding destination and verify it with the code Google sends.
- Remove every other forwarding destination.
- Set the ring duration to the longest available option and disable Google Voice voicemail.
- Call from an outside line and place a real order end to end. Then call again and ask for a human, to confirm the escalation path.
The verification step in item two is worth flagging, because Google sends a numeric code to the destination number and expects someone to enter it. Your voice agent isn't going to read that code back to you. Ask your provider to pull the verification code from the call log, or have them enable a temporary passthrough. Every reasonable provider has done this before. Setup on our side typically finishes inside 24 hours, and this is one of the two or three steps that actually needs a human on both ends.
Why the personal tier is a bad long-term home for your main number
Free Google Voice is a consumer product. That's not a knock on it. It's just a description of the support you get when something goes wrong at 6:40 on a Friday.
There's no phone number to call. There's no account manager. If the account gets locked because someone forgot the recovery email, the number your delivery listings and your Google Business Profile point at is unreachable, and so is your restaurant. Personal-tier numbers can also be reclaimed after long periods of inactivity, which is not a risk for an active restaurant but is a real risk for a second location you opened and haven't launched yet.
Emergency calling behavior on internet-based numbers also differs from a traditional line, and it's worth confirming what happens if a staff member dials 911 from whatever device that number lives on. That's a life-safety question, not a telecom-preferences question.
None of this means rip it out tomorrow. It means the number is the asset and the platform is not, and you should know how to move the number.
Porting the number off, and when to bother
Porting means moving the number itself to a different carrier, so it stops living at Google and starts living wherever you actually answer calls. Once ported, there's no forward, no screening, no double voicemail, and no extra ring cycle.
The mechanics differ between the free tier and the Workspace version, and there's typically a release step with a small fee on the consumer side. The general process is the same as any port: you give the receiving carrier your account details exactly as Google has them, they submit the request, and the number moves. Porting your restaurant's phone number covers the paperwork and the failure modes.
Bother with it when the number is on printed menus, on your storefront, on your Google Business Profile, and on third-party listings. At that point the cost of the number being unreachable for a day is much larger than the cost of a port. Don't bother if you're still testing whether a voice agent fits your operation at all. Forward first, port once you've decided.
What to test before you trust it
Forwarding is invisible until it fails, so build a habit of checking it.
Call your published number once a week from a phone that isn't yours, at a time when you're busy. Listen for how long it rings before the agent speaks. Place an order and confirm it lands in your POS with the right modifiers. Then hang up mid-sentence on the next call and confirm that shows up in your logs as an abandon rather than as a completed order.
Watch your caller ID too. Forwarded calls sometimes present the Google Voice number rather than the customer's, which breaks callback and can make your outbound returns look like spam. If your returns start getting flagged, fixing a spam-likely label on your restaurant's caller ID is where to start.
If a week of that goes clean, the forward is fine and you can stop thinking about it. If any of it is inconsistent, the forward is the first suspect, not the agent. A layer of consumer software between your customer and your kitchen is a layer you eventually want gone.