Quick answer: "Sanction sweep" is the industry shorthand for the current US A2P enforcement wave: carriers have stopped treating 10DLC registration drift as a backlog item and started treating it as a suspension event. Unregistered traffic gets cut at the carrier edge, brands that have gone quiet get re-vetted, and campaigns whose declared use case drifted from what they registered get shut down pending secondary vetting. None of it is a new rulebook — it is the existing registration contract, enforced. The workable response is the same as with every carrier-fee wave: make your own registration state legible before the carrier's auditors do, because a swept campaign that can re-substantiate itself quickly loses days; one that cannot loses the number's sender reputation along with the downtime.
This is an industry-news explainer in the same family as the A2P carrier-fee roundup and the interconnect-fee decomposition — external enforcement movement every US sender sits under, plus the tenant-owned posture for staying registered. Nothing described here is an Orbit product change; the hooks at the end point at controls that already exist.
What the sweep is actually sweeping
"Deactivation" gets used as one word for four different carrier actions, and the remediation differs per action:
- Unregistered-traffic suspension. Traffic from numbers with no live campaign registration stops at the carrier edge. This is the oldest head of enforcement and the least negotiable: on the big US carriers, unregistered long-code A2P is simply not carried, and the sweep closes the tolerance windows that used to let it trickle through.
- Dormant-brand re-vetting. A brand that registered and then went quiet — little or no traffic, sometimes for quarters — gets flagged for re-vetting. The brand record is still there; the carriers are re-checking whether the entity behind it is still real, still reachable, and still the entity the vetting score was issued for.
- Use-case drift. A campaign registered as
CUSTOMER_CAREthat now sends promotions is drift, and it is the single most common sweep trigger after non-registration. The registered use case is a contract about what the traffic is; when the traffic stops matching, secondary vetting opens and the campaign can be suspended while it does. - Secondary vetting. A campaign flagged by any of the above — or by complaint-rate thresholds the carriers do not publish — enters a secondary-vetting state: suspended or throttled until the vetting authority re-scores the brand and campaign. The cost is not the re-score itself; it is the downtime if the campaign cannot re-substantiate its declared use case on short notice.
The fourth is where senders feel wrong-footed, because the campaign "was approved." Approval is a snapshot of a declared contract; the sweep is the carriers auditing the contract against the traffic, continuously.
Why the enforcement window opened now
Three pressures converged, and none of them is seasonal:
- Registration actually universalized. 10DLC stopped being a best practice and became the wire requirement for US long-code A2P. Once the carriers' unregistered-traffic blocks are universal, the marginal cost of also auditing the registered stock drops — the same machinery that blocks the unregistered can re-check the registered.
- Complaint economics. Carrier-side spam complaints and bundling disputes keep landing on the registered, approved layer, not the unregistered one. Re-vetting the registry stock is the carriers' own cost control: every dormant or drifted campaign removed from the network is complaint volume and regulatory heat they no longer carry.
- The vetting layer matured. The ecosystem around The Campaign Registry — vetting partners scoring brands, secondary vetting as a repeatable service — turned brand quality into something carriers can re-measure cheaply instead of trusting the original score forever. Cheap to re-measure means often re-measured.
The pattern matters for planning: this is not a one-time purge with an end date. Each pass is narrower than the last, but the mechanism — audit the registry against the traffic, suspend what diverges — is now the steady state. A sender's posture should be built for a recurring audit, not survived once.
What it means for a tenant running US A2P
The sweep changes the cost model of registration the same way the carrier-fee wave changed the cost model of pricing: the external layer moves, and the durable response is a tenant-owned pass you can re-run. Three consequences are worth writing down:
- Rejection handling moves from launch-time to run-time. A campaign that passed TCR vetting at launch can still be swept a year later for drift. The 10DLC rejection companion covers the classic rejection reasons — EIN mismatch, sample messages that do not match the use case, missing opt-out language, political verticals without a Campaign Verify token — and the same reasons, discovered by a carrier auditor instead of a reviewer, are what a suspension cites.
- The campaign's declared use case is now an operational invariant, not paperwork. Register
CUSTOMER_CARE, send care traffic. RegisterMARKETING, send marketing. A use-case change your product team ships — a support line that starts carrying offers — is a registration event whether or not anyone files it, and the sweep is what finds the unfiled ones. - Downtime is priced in re-substantiation time. A swept campaign that can answer "here is the entity, here are the samples, here is the opt-out handling" re-registers in the same 1–5 business day window a first submission takes. One that has to reconstruct the answers – or worse, discovers the answers have drifted too – absorbs the suspension as an outage.
The four-step audit — tenant-owned, re-runnable
Run this per brand, against the campaign registry record and your real traffic; nothing in it requires the carrier to tell you anything.
- Inventory the sending stock. List every US long code actually sending, and map each to a live campaign registration. A number that sends without a registration is a suspension waiting to be scheduled; a registration that no longer maps to numbers is dormancy you chose.
- Match declared use case to observed traffic. For each campaign, read the registered
usecaseand a sample of what it actually sends. If the traffic has drifted — care campaigns carrying promotions, marketing campaigns carrying service messages — re-register the use case or constrain the traffic before an auditor classifies it. - Re-check the entity record. Match the brand's legal name and EIN against the tax record exactly, character for character, and make sure the shelf information a re-vet would find (website, contact points, opt-out narrative) still resolves to the entity that registered. Re-vetting fails on stale shelf information as readily as on drift.
- Dry-run the suspension question. For the campaign that matters most, answer in writing: if this campaign suspended today, what would re-substantiate its declared use case by tomorrow? The answers — current samples, the live opt-out handling, the current use case — are either at hand or they are the audit finding.
Where tenant-owned controls meet the sweep
Nothing about the sweep is an Orbit policy — it is carrier-side enforcement on US long-code A2P, and it applies to every sender on every platform. What the platform layer does is keep the registration itself legible and manageable instead of filing-cabinet state:
- The registration surface. The 10DLC registration guide walks brands and campaigns end to end, and the dashboard wizard keeps the brand record, the campaign declaration, and the assigned numbers queryable rather than passed around as screenshots. A re-vet that asks "what is this campaign?" is cheaper to answer when the answer is a live record.
- The rejection playbook. The rejection-and-revet guide covers the re-submission loop — what to fix, in what order, and how a corrected re-submission reads differently to a reviewer. The same loop, run preemptively, is step 2 of the audit above.
- Re-registration over re-porting. A swept campaign that re-substantiates quickly keeps its numbers and their sender reputation; one that has to re-register from scratch loses both. The audit's output is not a compliance memo — it is the difference between a re-submission and a re-port.
Frequently asked questions
What is a 10DLC sanction sweep?
The industry term for the current US carrier enforcement wave on long-code A2P: unregistered traffic suspended outright, dormant brands re-vetted, and campaigns whose traffic drifted from their registered use case shut down pending secondary vetting. It is enforcement of the existing registration contract, not a new rule.
Can a campaign that passed TCR vetting still be swept?
Yes. Vetting approves a declared contract — the use case, samples, and opt-out narrative as filed. Carriers audit the traffic against that declaration continuously, and a campaign whose traffic drifted can be suspended even though its original review passed. Approval is a snapshot; enforcement is ongoing.
What are the most common sweep triggers?
Unregistered sending, use-case drift (for example a CUSTOMER_CARE campaign sending promotions), dormant brand records with stale or unresolved entity details, and secondary-vetting flags on complaint-rate or anomaly signals the carriers do not publish. The organized response is the four-step audit above, run on your real traffic rather than the original filing.
Does this affect toll-free or short codes?
The sweep described here targets 10DLC — US long-code A2P. Toll-free verification and short-code programs are separate registration regimes with their own audit cycles; the audit method above transfers, but the registry being audited is the long-code one.
Is this a Devotel Orbit product change?
No. This is an industry explainer about carrier-side enforcement on US long-code A2P, in the same family as the carrier-fee wave and SMS-pumping posts. The linked guides cover registration and re-vet tooling that already exists; nothing in the platform changed or shipped with this post.
The takeaway
The sanction sweep is the registry being audited continuously instead of once. Senders who treat registration state as live operational state — what use case each campaign declared, what it actually sends, whether the entity record still re-vets clean — absorb the wave as routine maintenance. Senders who treat it as filing-cabinet state absorb it as an outage. The news is external; the audit is tenant-owned.