Website and contact email must be in place before an identity-plus vet
The requirementstatement
The brand website and business contact email must be populated before an Authentication+ or RBM vet is ordered.
- 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
- brand.website + brand.business_contact_email
- 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
Populate the brand website and the business contact email, and let the update settle on the brand record, before placing the vet order. Done when both fields read back from the brand and the mailbox has been tested (BRD-119).
A compliant exampleexample
website: https://acmecoffee.com · business_contact_email: jane.doe@acmecoffee.com — both present before the order
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| TCR | 501 | Yes |
Rules you will hit next
Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.
BRD-223 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.