Keeping Bulk Google Voice Accounts Active, and What a 50-Number Pool Costs to Maintain

Running bulk Google Voice accounts is mostly a maintenance problem, not a purchasing one. Buy 50 clean numbers, leave them alone, and within a few months the owning inboxes start collecting reclaim warnings and the pool starts losing lines, because an idle number is the easiest one to lose. The three rules that prevent most of that loss are simple: make a call or send a text from every number at least every 21 days, take each account over properly on the day it arrives, and keep a record of which number sits on which login.

Everything below is the operating side of a Google Voice pool. Grade definitions, activation rates by platform and market price bands are covered in our bulk Google Voice pricing guide, so this page assumes you already own numbers and now need them to still be there in six months.

Two ways a number is lost

Reclamation and restriction are different failure modes with different answers, and buyers routinely blame the second for losses caused by the first.

Reclamation is administrative. Google’s Voice policy says it may take a number back when the service goes unused, such as placing calls or sending texts, for three months. A warning with the reclaim date comes first, and for 45 days after that date you can still get the number back on voice.google.com, but in a bulk pool the warning lands in an owning account’s inbox that is easy to overlook. This is the single largest cause of shrinkage in bought pools, and it accounts for the majority of the “the numbers stopped working” complaints suppliers field. It is also entirely preventable.

Restriction is enforcement. Google’s Voice policy prohibits creating multiple accounts and selling or transferring Voice accounts, and when Google identifies a potential violation it may limit or terminate access, so a bought pool carries that exposure by its nature. When a restriction lands, stop using those lines, keep the wording of the notice, and claim any line that fails to sign in or take an SMS inside the seven-day replacement window. Losing one number is bad luck; losing eleven on the same afternoon is a decision about those accounts, and no maintenance routine reverses it.

Taking each account over on delivery

Most avoidable losses are decided in the first sitting, when a batch is opened. Do these four things for every account on the day it arrives, and the lines that fail later fail for reasons you can see.

Sign in and test the line. Open the delivery file, sign into the owning Google account, confirm the Voice number is attached, and send one text from it. A challenge on a new device is Google checking who is signing in; clear it from the recovery details in the file rather than trying to disguise the sign-in.

Make the login yours. Change the password, turn on 2-Step Verification, move the recovery email to an address you control, and sign out every other session. A password reset that routes to an inbox you do not hold is the same as no reset at all.

Keep recovery under your control. Use recovery addresses you or your team genuinely control, secure them with 2-Step Verification as well, and record which recovery address covers which account. Whoever holds a recovery inbox can reset every account that points at it.

Record the handover. Log the number, the owning login, the delivery date and the date of the first text in your inventory sheet. That sheet drives the keep-alive schedule below and turns a replacement claim into a one-message job.

The 21-day keep-alive rule

The reclamation timer tracks the number, not the account, which is why so many operators are surprised by it. Logging into the Google account weekly and doing nothing else will not save the line. The 21 days is our house rule, not Google’s: Google’s stated period is three months, and the margin is there because a bulk pool always has lines that slip.

What actually resets the clock

Activity on the number itself. Google names three actions that keep it: making a call, sending a text, or listening to voicemail. One sent message per number is enough, takes seconds, and costs nothing, since texts to US numbers are free. Logins, settings changes and profile edits are not on that list. Send the message by hand, because Google’s Voice policy prohibits sending messages through an automated process such as a script.

A schedule that scales past 50 numbers

Split the pool into three groups by the day of the month you bought or last touched each line, then run one group per week on a rolling basis. Every number gets touched every 21 days, and the work spreads evenly instead of landing on a single day.

1. Group the pool into thirds and assign each a week.
2. On that group’s week, send one outbound text by hand from every number in it.
3. Log the date against each number in your inventory sheet, and check the owning Gmail for a reclaim warning while you are signed in. Untracked pools are how numbers quietly disappear.
4. Any line that has gone past 25 days without a sent text, a call or a voicemail listen goes to the front of the queue, ahead of scheduled work, even if it has been receiving codes.
5. Numbers you have deliberately parked for later use still need this. Storage is not an exemption.

Skipping this on 50 numbers leaves every line exposed to reclamation once it passes three months without use, and replacing the pool costs $225 to $425 at list prices. The keep-alive routine costs about 40 minutes of operator time a week.

Pool tiers, and why a working pool is never fully deployed

Treat the pool as two tiers rather than one flat pile. Active numbers carry current work. Reserve numbers are undeployed stock held against replacement need, on the same keep-alive schedule. A line where a platform refuses or rate-limits a code, a text will not send, or Google sends a notice about how the account is used carries no more verification work: claim it only if it has failed to sign in or to receive an SMS inside the seven-day window, otherwise write it off, and move a reserve number into active work for new jobs, not to re-run the refused or rate-limited one.

A 50-number pool under that split runs roughly 40 active and 10 in reserve. If you need 50 numbers doing live work, buy 63 to 67. Sizing the order to the deployment count and nothing more is why pools run dry in month two.

Which MixAcc grade suits which job

Age on delivery changes what a number is suited to, not the rules it runs under. Our four Google Voice variants map cleanly onto workload.

Those are list prices; for a larger order, ask for the full-order rate. The aged grade costs roughly 89% more than USA Mix, and the case for it is not that age exempts a line from anything: an aged number sits on the same three-month clock and under the same rules as a fresh one. The case is that it arrives with 30 or more days of history behind it, which suits lines you intend to keep for years as recovery numbers or staff lines. For one-and-done verification work the mix grade is the correct purchase and paying up is waste. Rates for adjacent account categories sit in our 2026 PVA cost breakdown.

Habits that cost bulk pools the most

Three habits cause most of the self-inflicted losses in bulk operations, and none of them is fixed by making the activity look different.

The first is automation. Scripts that send texts or place calls from Voice numbers are prohibited by Google’s Voice policy, and a keep-alive routine run through one puts every line it touches at risk. The routine above is quick enough to do by hand.

The second is the shared login. Twenty-five accounts passed around a team with the passwords in a chat thread produce challenges nobody can answer and settings changes nobody can trace. Give each login to one named person and keep the credentials in a password manager.

The third is forgotten parked stock. A line pulled from the shelf after four months may already be past its reclaim date. Before putting parked stock back to work, sign in, confirm the number is still attached, and check the owning Gmail for a reclaim warning; if you are inside the 45 days after the reclaim date, get the number back on voice.google.com before buying a replacement. When a line locks instead, our locked-account playbook sets out what is worth salvaging and what to claim.

Reading the early warning signs

Google does not publish early-warning signs, but three things are worth stopping for, and each is a reason to stop and look rather than push on.

Verification codes arrive late or not at all. The cause may be the sender rather than the line: Google notes that some websites, such as banks or subscription services, won’t send texts to Google Voice numbers, and some platforms refuse VoIP numbers outright.

Logins that previously went straight through begin demanding a recovery challenge. Clear it from recovery details you hold, and if recovery still points at the address in the delivery file, move it to yours in the same sitting.

Outbound texts fail with Google’s own error: “Message not delivered. You’ve sent too many messages.” or “Message not delivered. See Acceptable Use Policy.” Google says repeated violations can lead to suspension.

What comes next depends on the signal. A login challenge you clear from recovery details you hold, with no notice from Google, leaves the account intact, and so does a slow code with no refusal behind it. A code the platform refuses or rate-limits, a text Google will not send, or a notice about how the account is used ends that line’s verification work: check the owning Gmail, claim the line only if it has failed to sign in or to receive an SMS inside the seven-day window, and otherwise write it off. Do not re-run a refused or rate-limited job on another number to get past the limit.

When a number is not worth recovering

Some losses should be written off immediately rather than chased. A reclaimed number is gone once the 45 days after its reclaim date have passed; inside that window, search for it by city or area code on voice.google.com and get it back before buying a replacement. A number whose owning Google account is suspended is also gone. Google’s appeal is meant for the owner (“If you own the account, you can request access to it again”), and Google’s Voice policy does not allow a Voice account to be transferred to you, so do not try.

Worth recovering are lines where the account is intact but challenged, and lines where the recovery email is under your control and can clear the verification. That is the practical dividing line: if you hold the recovery path, spend 15 minutes; if you do not, replace the unit and move on. Replacement stock at $4.50 to $8.50 is cheaper than an hour of your time.

Budgeting the upkeep, not just the purchase

The purchase is the largest cash line in a maintained pool, and most of what comes after it is time rather than cash. Texts to US numbers from Google Voice are free, so keep-alive traffic costs nothing but the minutes: about 40 minutes a week across 50 numbers on the schedule above, plus a few hours on delivery day to take each account over.

The ongoing cash line is replacement. Budget extra in the first month: dead-on-arrival units surface in the first week, when the seven-day replacement window covers them, but lines that fail after day seven are yours to replace. After that, attrition to plan for, assuming the routine above is actually followed, is 3 to 6% of a pool per quarter to reclamation and enforcement combined: about 1.5 to 3 lines from 50 on average, or roughly $7 to $26 a quarter at MixAcc list prices. Neglect is what makes a pool expensive. Without keep-alive traffic, every line that goes three months without a call or text is exposed to reclamation, and replacing all 50 costs $225 to $425, four to eight years of replacement on a well-kept pool. That gap is the argument for maintaining a smaller pool properly rather than a large one carelessly. Fifty well-kept numbers outproduce two hundred neglected ones by a wide margin, and cost less to run.

How MixAcc supplies pools built to be maintained

Every Google Voice number we ship carries bundled Google account access, meaning login, password and recovery email, because a line you cannot administer cannot be maintained. Delivery files list the creation date and area code per unit so you can build the keep-alive schedule on day one rather than reconstructing it later. All four variants stay in continuous supply, orders of 50 units or more can name target area codes, and most orders ship the same day.

Replacement runs 7 days on every grade, which covers dead-on-arrival units rather than lines lost to neglect three months later. List prices run from $4.50 to $8.50 a line; for the full-order rate, ask us on Telegram at @nexkyc or WhatsApp at +1 (737) 307-6751. Payment is crypto, bank transfer, or card payment against an invoice.

Tell us your monthly verification volume, the platforms you are verifying on, and whether the numbers will be parked or used continuously, and we will size the order to consumption instead of selling you shelf stock that expires. Live rates are on the Google Voice accounts page, and if you are still choosing a supplier, our rated list of bulk Google Voice sources sets out what to check before paying.

Reach us on Telegram at @nexkyc, on WhatsApp at +1 (737) 307-6751, or by email at allmixacc@gmail.com. Send the brief and a quote with a delivery window comes back inside 24 hours.