VICIfast
All guides

The FCC's number cycling proposal, for call centers

The FCC is asking whether to prohibit or limit number cycling. What the proposal says, its status as of Nov 2026, and how to run a defensible caller ID pool.

VICIfastLast updated

"Will the FCC ban number rotation?" is a question outbound floors keep asking this year. Nobody can answer it yet. What we can do is read the proposal, say what it covers, and describe a number practice that holds up whichever way the FCC goes.

This page is for the sysadmin or ops lead who runs outbound campaigns on VICIdial and keeps hearing "the FCC is going after DID rotation." Every outside fact is in the Sources list at the bottom. Where we could not confirm a detail, we say so.

What is the FCC's number cycling proposal?

It is a Notice of Proposed Rulemaking, FCC 26-17, "Combatting Illegal Robocalls Through FCC Numbering Policies." The FCC adopted it on 26 March 2026 and the Federal Register published it on 8 May 2026. It is a proposal that asks questions. It is not a rule.

The docket numbers are WC Docket 26-49, plus 20-67, 13-97 and 07-243. Paragraphs 51 through 58 cover number cycling. The rest of the document is about numbering policy more broadly, including whether to limit how many times a number can be resold.

The practical meaning of "NPRM": the FCC publishes draft ideas, the public comments, and only then does the Commission vote on a final order. Nothing in this notice changes what you may do on a dialer today.

What does the FCC mean by "number cycling"?

The FCC describes numbers used "on a rotating basis" as few as one or two times. The target is a pattern where a number is dialed out briefly, then dropped and replaced with another, so that no number builds a history.

That is narrower than "using more than one caller ID." A campaign that spreads calls across 200 local numbers it owns, each used for months, does not look like the pattern the notice describes. A script that buys a number, burns it in a day and buys the next one does.

We are summarising a short passage, so read paragraphs 51-58 in the NPRM itself before you rely on our summary. The exact line between "cycling" and ordinary use is one of the things the FCC is asking commenters to help define.

What is the FCC asking about number cycling?

It asks whether to prohibit or limit number cycling, and it says plainly that "there may be legitimate uses." The questions are open. The notice does not propose a specific cap on how often a business may change numbers.

Three things in that framing matter to a call center:

  • Prohibit or limit are both on the table. A limit could be a cap, a minimum holding period, or a reporting requirement. The notice does not choose.
  • Legitimate uses are acknowledged. The FCC invites comment on what those are, which is the opening for operators to describe real campaigns.
  • Resale gets its own question. The notice floats limiting number resale to one level, so the party you get a number from could not itself have bought it from another reseller. That reaches DID supply, not dialer settings.

What is the status as of November 2026?

As of 4 November 2026, it is still a proposal. We found no final rule. A Mintz summary from July 2026 describes enforcement shifting upstream, toward the providers who supply numbers, but it describes the direction of travel, not a decision.

You should check for yourself, because this page can be stale the day after the FCC acts:

  1. Open the FCC's Electronic Comment Filing System and search proceeding 26-49.
  2. Repeat the search for 20-67, 13-97 and 07-243, since the NPRM was filed in all four.
  3. Look for a "Report and Order" or "Order" in those dockets. A comment or reply comment is not a decision.
  4. Check the Federal Register for a final rule that cites FCC 26-17.

We will update this page when the FCC acts. The date at the top is the last time we checked. We are not predicting an outcome.

Why do regulators and analytics firms care about rotation?

Because rotation lets a bad caller shed a bad reputation. The analytics companies that label calls for carriers have published numbers on this, and the FCC has cited the survey data too.

FigureSourceDate
About a third of scam calls use number rotationHiyaOct 2023
18% of reported US spam calls come from numbers with minimal call historyHiyaJan 2025
60% of 300 surveyed business leaders rotate numbers multiple times a month; 29% daily or automaticallyHiya survey, cited by the FCC2023

Read the third row carefully. Hiya is a vendor with an interest in the topic, and the survey asked businesses, not only bad actors. It says a lot of legitimate callers rotate. That is why the FCC acknowledged legitimate uses, and why a blunt ban is not the only outcome on the table.

Consumers are not helping either side. Hiya's State of the Call 2026 reports that 86% of unknown calls go unanswered. A number with no history looks like an unknown number to a person, and to an analytics engine.

Is it legal to rotate DIDs today?

Nothing in the proposal makes ordinary use of multiple caller IDs unlawful today. Two rules already apply, and neither mentions rotation by name: the Truth in Caller ID rules and the telemarketing caller ID rule.

  • 47 CFR 64.1604 (Truth in Caller ID). It bars transmitting misleading or inaccurate caller ID information "with the intent to defraud, cause harm, or wrongfully obtain anything of value." Intent is the test.
  • 47 CFR 64.1601(e). A telemarketer must transmit a caller ID that lets the person called make a do-not-call request during business hours. A number that rings nowhere does not meet that.

So the risk is not "I own more than one number." It is "my numbers can't be called back" or "I am using numbers to hide who is calling." A pool of numbers you own, that ring back to your floor or your IVR, is in a far stronger position under both rules as written.

This is where we say it once: talk to your counsel. We are a hosting company, and we are describing public rules, not advising on your campaigns.

What does a defensible number practice look like on a VICIdial floor?

A stable pool you own, used for reasons you can state, rested instead of churned. Five habits cover it, and none of them depend on how the FCC rules.

  1. Own the numbers, and make them answerable. Each caller ID should ring somewhere that identifies your business and takes a do-not-call request. Test it. This is the 64.1601(e) point.
  2. Use local numbers because your contacts are local. An area-code match is a reasonable business reason. "So the number doesn't have a label yet" is not one. See area-code caller ID (AC-CID).
  3. Rest, then warm up, instead of replacing. A number that has gone quiet can often come back. Matt Florell, VICIdial's author, reported at Astricon 2021 that a label takes "2 to 21 days" to clear after a number stops being used. The procedure is in How to rest a flagged caller ID in VICIdial.
  4. Replace only what does not recover. Retire a number after it fails a rest and a test, not on a schedule and not the first time it dips.
  5. Write down why each number exists. Campaign, area code, date acquired, date rested, date retired. If anyone ever asks why you hold 300 numbers, the answer is a spreadsheet and not a story.

Florell's same talk also warns that "a minimum of 5 minutes and 200 phone calls can get you flagged." Volume per number matters as much as how many numbers you have. A daily per-number cap is part of a stable pool.

Spam Likely vs Scam Likely covers the labelling side, and How to get Spam Likely removed covers what you can and can't do about a label.

How is the DID Reputation Center built around that?

It is designed for a stable pool, not for churn. The DID Reputation Center reads every outbound call from your VICIdial server's own call logs and reports how often a person picks up on each caller ID. It infers likely labels from those pick-up rates. It does not read carrier labels and does not file appeals.

The free health view comes with every VICIfast server. The optional Full Controls, which you can trial in a mode that only shows what it would do, act per campaign:

  • Rest. An at-risk number is rested for 7 days, 14 the second time, and given small test calls before it returns.
  • Warm-up. New numbers ramp up gradually, under a daily per-number call limit.
  • Local coverage. At least one local number is kept per area code.
  • Replacement, capped. With VICIfast numbers, a number that did not recover can be swapped for a fresh one, free, up to 10% of the account's numbers a month. A number that fails two rounds of test calls is kept out.
  • A record. Every change appears in Activity with Undo and is logged in VICIdial's admin log under the user VICIfast.

The 10% cap is deliberate. It keeps the product from becoming a rotation machine, which is the pattern the FCC is asking about. Pricing is $499 per server per month with a two-week free trial, and it is included at no charge for accounts with 1,000 or more VICIfast numbers.

It does not make calls compliant, and it does not remove labels. It shows you which numbers are in trouble and keeps a written trail of what you did about it. The CID group mechanics it manages are in CID Groups: rotating caller IDs across a campaign and CID Group failover.

Will the FCC ban number rotation?

We don't know, and we are not going to guess. The notice leaves both "prohibit" and "limit" open and concedes legitimate uses exist.

What you can do now costs nothing if the answer turns out to be "no change": keep a pool you own, make each number answer, rest before you replace, and keep records. If a rule does arrive, a floor that already works this way has little to change.

Last checked 4 November 2026. This page will be updated when the FCC acts on FCC 26-17.

Sources