Number Pool Rotation and Burned Number Recovery: The Operational Cycle Every Outbound Team Needs

Why the Rotation Cycle Exists

Every outbound number accumulates a behavioral record at terminating carriers. That record is built from: total calls placed, answer rates on those calls, duration distribution of connected calls, complaint signals from recipients, and in the US and Canada, STIR/SHAKEN attestation status.

Carriers do not publish the exact scoring models they use, but the practical effect is consistent: high-volume numbers that are not answered at normal rates, or that generate short-duration connects (answer-then-hang-up patterns), accumulate negative signals faster than low-volume numbers with strong connect ratios.

A rotation cycle systematically removes numbers from active use before their behavioral record degrades to the point of producing labeling or significantly reduced answer rates. It replaces them with fresh numbers that start with a clean record.

The Two-Phase Cycle: Active and Rest

A well-designed rotation cycle has two phases for each number:

Active phase. The number is in active campaign rotation. It receives a controlled volume of outbound calls per day, below the threshold that would accelerate behavioral scoring accumulation. In a well-sized pool, this means each number handles 30–50 dials per day rather than 100+.

The active phase ends when one of three things happens: the number reaches its scheduled rotation date (e.g., 30 days of active use or 2,500 total dials), its per-number answer rate drops more than 15% below campaign baseline for five or more consecutive days, or a complaint or labeling signal is detected.

Rest phase. The number is removed from campaign assignment but kept provisioned. Zero outbound calls are placed from it. The rest period allows any volume-based behavioral scoring to potentially fade. Rest periods typically run 30–60 days.

After the rest period, numbers are either returned to active rotation (for numbers that rested due to rotation schedule, not degradation) or decommissioned (for numbers that were rested due to complaints or confirmed labeling).

The Replacement Provisioning Queue

Rotation only works if replacement numbers are available. Every number leaving active rotation—for rest or decommission—needs a replacement entering the active pool.

This means maintaining a provisioning queue: a list of pending number provisioning requests that keeps the active pool size constant as numbers rotate out. In markets with near-real-time provisioning (US, UK, most Western Europe), the queue can be thin—requests placed the day before rotation are available in time. In markets with registration requirements, the queue needs longer lead time.

Track the queue explicitly: how many numbers are currently active, how many are in rest, how many are pending provisioning, and what the target pool size is. When the queue runs short, the pool shrinks below operational size and agents start getting assigned burned or resting numbers because nothing else is available.

Recovery: Can a Burned Number Come Back?

Whether a degraded number can recover to normal answer rate performance after a rest period is an empirical question that carriers do not answer publicly. The operational observation from teams that have tracked per-number performance through rest cycles:

Numbers that degraded primarily from high call volume—not from complaints or labeling—sometimes return to near-baseline answer rates after 45–60 days of zero call volume. Numbers that were formally labeled or generated significant complaint signals do not recover reliably.

This means: do not decommission numbers immediately when they degrade from volume. Rest them first. If performance recovers after a rest period, they can return to active rotation at lower intensity. If performance does not recover after 60 days of rest, decommission.

Keep records. When a number returns from rest, track its performance separately from numbers that have never been rested. If it degrades faster in its second active cycle than its first, that is a signal that it does not fully recover and should be decommissioned earlier in future cycles.

Rotation and STIR/SHAKEN in the US and Canada

For US and Canadian outbound, STIR/SHAKEN A-level attestation is the mechanism that prevents carrier-level "Spam Risk" labels. Attestation is maintained at the originating carrier level—UnlimCall's origination network handles this for numbers provisioned on the platform. The network page covers how the attestation infrastructure works.

What rotation does for STIR/SHAKEN: keeping call volume per number below the behavioral scoring thresholds means that attested numbers do not accumulate the volume-based signals that lead to labeling even with active attestation. Attestation prevents formal labeling; rotation prevents behavioral scoring from degrading answer rates below what attestation alone can protect.

Documenting the Cycle

Every number in the pool should have a record: provisioning date, entry date into active rotation, current status (active/rest/decommissioned), total calls placed in each active cycle, answer rate history, and any incident notes (complaints, detected labeling, performance drops).

This documentation serves multiple purposes: it enables data-driven rotation decisions rather than calendar-based ones, it provides the audit trail for regulatory defensibility in markets that require caller ID documentation, and it gives you the historical record to evaluate whether rested numbers actually recover.

Flat-rate per-seat pricing removes the cost incentive to keep burned numbers in rotation. At $99/seat/month for US/CA, the DID provisioning cost is bundled with the calling cost. See the pricing page for per-market rates.