Spreading a robocall campaign across many calling numbers, accounts, or providers so that no single number generates enough volume to trigger detection or blocking.
The term borrows from email spam, where a "snowshoe" sender spreads mail across many addresses to stay below filtering thresholds. In voice, the campaign rotates through large pools of numbers, sometimes thousands of DIDs, each used only a handful of times before being retired. Calls may also be spread across many accounts or many upstream providers to dilute the volume any single entity sees.
Snowshoeing defeats defenses that look at individual numbers, such as complaint-based blocklists and per-number rate limits. It also makes it harder for analytics to build a reputation for the caller, since each number has almost no history. It also slows down tracebacks, since investigators may need to connect many apparently unrelated calls before a pattern becomes clear.
Detection has to work at a higher level: the customer account, the trunk, the IP address, the signing provider, or the shared content of the calls. Signs include an account that cycles through a large share of its number inventory, uniform call durations across many numbers, and synchronized bursts of traffic.
Why it matters to carriers
Originating providers often see snowshoe campaigns first, because the pool of rotating numbers usually comes from their own DID inventory. Watching how many distinct calling numbers each customer uses relative to its call volume, and questioning sudden number-pool growth during onboarding, can expose a campaign before it generates tracebacks.