# BRD-178 — Brand contact details must be unique across brands

> Each brand must have its own contact address, email and phone; reusing them across brands is a policy violation.

- **Rule ID:** BRD-178
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.email + brand.phone + brand.street`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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, Twilio, Bandwidth
- **Applies:** Applies when the brand is NOT a sole proprietor.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-178/

## Why this rule exists

Shared contact details across many brands is the signature of a reseller registering client traffic under its own details, which is the pattern the brand-per-EIN and consent-transfer rules exist to stop. Providers treat it as a violation serious enough to trigger deactivation rather than a mere rejection.

## How to fix it

Use the client's own address, email and phone for each brand. If you are an agency, your details belong on the CSP record, never on the brand.

## Example of a compliant value

```text
Brand contact: jane.doe@acmecoffee.com — not agency@northstarmarketing.com reused across ten brands.
```

## Notes

Detectable only against other brands in the same tenant, so it is surfaced as guidance until multi-brand state exists.
