A public company must supply a business contact email
The requirementstatement
A PUBLIC_PROFIT brand must carry a business contact email — it is mandatory and it triggers the Authentication+ 2FA.
- 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.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
- TCRAWSTelnyx
- When it appliesapplicabilityText
- Applies when the brand is a public company.
Why this rule existsrationale
How to fix itremediation
Supply a named individual's mailbox on the company domain, monitored by someone who will act on a verification mail within days. Done when the field is populated and that person knows a PIN is coming.
A compliant exampleexample
business_contact_email: jane.doe@acmecoffee.com — an individual mailbox on the company domain
Common mistakespitfalls
- The PIN expires (BRD-227), so an address that is technically valid but monitored monthly fails the verification just as surely as an empty field.
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 |
| Twilio | 30994 | Yes |
Rules you will hit next
One other rule reads brand.business_contact_email. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
BRD-117 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.