Vetting is not a remedy for a rejection
The requirementstatement
External vetting exists to raise throughput, not to reverse a rejection, and it is not guaranteed to raise anything.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- the reason a vet is being ordered
- 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
- BandwidthAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Correct the brand data the rejection pointed at, or file an identity appeal with documentation. Order the vet afterwards, and only if the throughput you need is above what a verified brand gets by default. Done when the identity status is resolved before any vet is bought.
A compliant exampleexample
Fix the legal name to match the CP-575, then re-verify — rather than ordering a standard vet against the same unchanged name
Notesnotes
Rules you will hit next
Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.
BRD-212 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.