# BRD-117 — A public company must supply a business contact email

> A PUBLIC_PROFIT brand must carry a business contact email — it is mandatory and it triggers the Authentication+ 2FA.

- **Rule ID:** BRD-117
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.business_contact_email`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR, AWS, Telnyx
- **Applies:** Applies when the brand is a public company.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-117/

## Why this rule exists

For a public company this field is not a contact detail, it is the second factor: the PIN goes to it and the brand cannot reach VERIFIED without one. Omitting it does not produce a missing-field error people recognise — the brand sits in an authentication-required state, which reads as a queue rather than as a blank box.

## How to fix it

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.

## Example of a compliant value

```text
business_contact_email: jane.doe@acmecoffee.com — an individual mailbox on the company domain
```

## Common mistakes

- 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 codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| TCR | `501` | yes |
| Twilio | `30994` | yes |