What is a 'Snowshoeing Detected' violation in 10DLC and what triggers it?

'Snowshoeing Detected' is a carrier enforcement designation indicating that similar message content is being distributed across multiple registered numbers or campaigns to stay below individual campaign detection thresholds. Triggers include: sending nearly identical messages from multiple phone numbers, registering multiple campaigns with duplicate content profiles, coordinated volume bursts across numbers that individually appear compliant, and campaign content that mirrors other flagged senders in carrier databases.

How do I fix a 10DLC campaign suspension caused by Snowshoeing Detected?

Remediation requires: (1) immediately cease all message delivery on flagged campaigns, (2) reduce the number of numbers sending similar content to a single compliant campaign, (3) document the legitimate business reason for your message volume and distribution pattern, (4) review message content for sufficient personalization to distinguish individual messages from template broadcasts, (5) submit a formal remediation plan to your messaging platform for carrier review. Resolution typically takes 7–21 business days.

Can legitimate high-volume SMS campaigns trigger a false Snowshoeing Detected flag?

Yes. High-volume campaigns with templated content can be flagged for snowshoeing even when completely legitimate. False positives occur when: identical template-based messages are sent in volume bursts, personalization tokens fail and produce identical message text, or campaign sending patterns correlate across multiple numbers in ways that resemble distribution tactics. Meaningful personalization, staggered sending, and pre-registration content review reduce false positive risk.

What content and sending practices prevent Snowshoeing Detected flags?

Prevention best practices: include meaningful personalization in each message (recipient name, account detail, specific appointment information), avoid identical message text across large sending batches, maintain consistent sending volume rather than burst patterns, limit similar content to a single registered campaign rather than distributing across multiple numbers, and ensure campaign content profile matches approved sample messages. MyTCRPlus provides sending pattern guidelines that reduce snowshoeing detection risk.

Does a Snowshoeing Detected flag affect other campaigns under the same brand?

Snowshoeing violations that indicate intentional evasion behavior can affect the entire brand registration — not just the flagged campaigns. Carrier compliance teams use snowshoeing signals as indicators of deliberate policy circumvention, which can trigger brand-level trust score reductions and enhanced scrutiny on all associated campaigns. Isolated false positives typically affect only the flagged campaign, but documented patterns trigger brand-level review.

Fix "Snowshoeing Detected" 10DLC Violations

Understanding the "Snowshoeing" Flag

"Snowshoeing" is a spam tactic where high volumes of messages are spread across many phone numbers to dilute the volume per number and evade spam filters (like a snowshoe spreads weight over snow). Carriers now use advanced algorithms to detect this pattern.

Violation Type Evasive Behavior

Consequence $1,000+ Fine / Block

Urgency Critical - Immediate Halt

Why Legitimate Brands Get Flagged

Local Agent Model

Insurance or real estate firms assigning unique numbers to hundreds of agents without proper "Number Pool" registration.

Load Balancing

Attempting to bypass daily throughput caps by rotating sender IDs (a direct violation of 10DLC rules).

Identical Content

Sending exact-match template messages from 50+ numbers simultaneously triggers pattern matching.

How to Fix & Prevent Snowshoeing

To resolve this violation, you must restructure your campaign to align with carrier expectations for high-volume or multi-number use cases.

1

Consolidate to High Throughput

Instead of 50 numbers sending 200 messages each, move traffic to 1-5 numbers. Increase your Trust Score to unlock higher daily caps (up to 200k/day).
2

Register a Number Pool

If you must use many numbers (e.g., local branches), file a Number Pooling Request with T-Mobile. This requires a fee and manual review to whitelist your use case.
3

Separate Use Cases

Ensure marketing traffic and transactional traffic are on separate campaigns. Do not mix them on the same number pool.

Technical Thresholds

Understanding the limits helps you stay within the safe zone.

Parameter	Standard Limit	Violation Trigger
Numbers per Campaign	49 Numbers	50+ without approval
Message Similarity	Varied content	100% identical across 10+ nums
Burst Rate	Defined by Trust Score	Exceeding TPM cap across pool

Prevention Strategy

Avoid future flags by adopting a transparent sending strategy.

Sticky Sender ID

Keep the conversation with a customer on the same number. Do not rotate numbers for the same recipient.

Campaign Segmentation

Register separate campaigns for distinct use cases (e.g., "Agent 1", "Agent 2") if feasible, rather than one massive pool.

Respect Throughput

Design your sending logic to respect the TPM limits of your campaign tier, queuing messages rather than blasting.

Clean Up Your Traffic

Don't risk a permanent ban. Use our diagnostic tool to analyze your traffic patterns and identify snowshoeing risks before carriers do.

Diagnose Now

Frequently Asked Questions

Is number pooling illegal?

No, using multiple numbers is legal if you have a valid business reason (e.g., local presence for agents). It becomes a violation when used primarily to evade throughput limits.

How much is the Number Pooling fee?

T-Mobile charges a $200 fee to review a Number Pooling Request. This fee is non-refundable, even if the request is denied.

Can I appeal a snowshoeing block?

Yes, but you must provide concrete evidence of your legitimate use case and proof that you have corrected the traffic patterns. This often requires legal or compliance team intervention.

Message Validator

Check for content flags.

Validate Now

Number Pool Limits

Understand the 49-number cap.

View Limits

Trust Score Sim

Boost your approved throughput.

Simulate Score

Legal Disclaimer: This content provides general information about carrier "snowshoeing" policies and compliance strategies. It does not constitute legal advice. Definition and enforcement of snowshoeing violations are at the sole discretion of mobile carriers. MyTCRPlus does not guarantee immunity from blocking or fines.

Fix "Snowshoeing Detected" Violations