A political token is used once and once only

The requirementstatement

Each Campaign Verify token is single-use and unique to one brand and CSP; a second use requires a reissue or a fresh political vet.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: the Campaign Verify token
Where it liveslayer: BrandBRAND
How Ekas settles itdetectability: External recordEXTERNAL_DATA; The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
What the fix involvesfailureClass: Wait on someone elseTERMINAL_EXTERNAL; Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities: TwilioTCR
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Standard vetting tokens can be spread across duplicate brand instances (BRD-218) and political ones cannot, so an operator who learned the first behaviour applies it to the second and the reuse is refused. Getting another token is not a self-service action — it means going back to Campaign Verify — which is why this costs days rather than minutes.

How to fix itremediation

Use each token on exactly one brand at one CSP. Where the same organisation registers through two providers, request a second token from Campaign Verify rather than importing the first one twice — and request it before you need it.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twilio	21722	Yes
TCR	543	Yes

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Has this Campaign Verify token been used on any other brand or at any other CSP?

1Keep a record of which brand each token went to. The refusal on a second import does not say where the first one was used.
2Registering the same organisation through two providers means requesting a second token from Campaign Verify — before you need it, since it is not self-service.

What wrong looks like: Standard vetting tokens can be spread across duplicate brand instances, so an operator applies the same habit to a political one. The reuse is refused and getting another costs days.

Notesnotes

Absorbs OPS-320, which contrasts single-use political tokens with the multi-use standard tokens in BRD-218. Whether a token has already been consumed is registry state we cannot see. What the user has to track is which brand each token went to, because the refusal on the second import does not say where the first one was used.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

BRD-001A legal company name is required for every entity but a sole proprietorBlockingBLOCKING BRD-002Legal name must match the IRS record for the EINBlockingBLOCKING BRD-003Legal name must carry its exact entity suffix as filedBlockingBLOCKING BRD-008Legal name must not carry an appended personal name or roleBlockingBLOCKING BRD-009The legal name field takes the legal name, not the trading nameBlockingBLOCKING BRD-011A legal business name may back only one brand across the whole registryBlockingBLOCKING

All brand rules

BRD-246 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.