Import the same token into every instance of the same brand
The requirementstatement
Where the same brand is registered by more than one CSP, the same vetting token must be imported into each instance.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- the vet token across brand instances
- Where it liveslayer
- BrandBRAND
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- What the fix involvesfailureClass
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Import the same Aegis standard token into each duplicate brand instance, rather than ordering a fresh vet per CSP. Done when every instance of the brand reports the same vetting score.
A compliant exampleexample
vetting token: the same Aegis certificate imported into both the Twilio and the Telnyx brand instances
Common mistakespitfalls
- Political tokens are single-use (BRD-246) and cannot be spread this way — the reuse rule is specific to the Aegis standard class.
Rules you will hit next
Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.
BRD-218 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.