The political vetting contact must be named in the registration

JSONMarkdown

The requirementstatement

The contact name on an Aegis political vet must match an authorised name in the political registration — not the CSP's or the aggregator's.

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 political vetting contact name
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
Human checkHUMAN
Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass
Supply evidenceTERMINAL_EVIDENCE
Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities
TCRAegis
When it appliesapplicabilityText
Applies when the use case is POLITICAL.

Why this rule existsrationale

The vet verifies a named individual against the public filing, so the CSP contact who is doing the paperwork is exactly the wrong name to use. It is the natural one to use, because they are the person completing the form, and the failure comes back as an identity mismatch that reads as though the organisation itself was not recognised.

How to fix itremediation

Take the contact name from the political filing — the treasurer or the authorised representative named there — and use it on the vet, even if that person is not the one submitting. Confirm they are available to receive the couriered PIN.

Check this yourselfattestation

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

Is the contact name on the vet an authorised name from the political filing, and does that person know a courier is coming?

  1. 1Open the FEC or state filing and copy the treasurer's or authorised representative's name from it — not the name of whoever is completing the paperwork.
  2. 2Warn that person that a couriered PIN is on its way and confirm they will be there to receive it.

What wrong looks like: The CSP contact doing the form uses their own name. The failure returns as an identity mismatch that reads as though the organisation itself was not recognised.

Notesnotes

The authorised names are in the public filing rather than in the registration. What the user has to do is open their own FEC or state filing and copy the name from it, and warn that person that a courier is coming.

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 proprietorBlockingBLOCKINGBRD-002Legal name must match the IRS record for the EINBlockingBLOCKINGBRD-003Legal name must carry its exact entity suffix as filedBlockingBLOCKINGBRD-008Legal name must not carry an appended personal name or roleBlockingBLOCKINGBRD-009The legal name field takes the legal name, not the trading nameBlockingBLOCKINGBRD-011A legal business name may back only one brand across the whole registryBlockingBLOCKING

All brand rules

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

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works