# WEB-058 — Website, description, flow and samples must identify one sender

> The website, campaign description, message flow and sample messages must all identify the same sending business.

- **Rule ID:** WEB-058
- **Layer:** Website (`WEBSITE`)
- **Checks:** `brand website + campaign fields + samples`
- **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:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR, Twilio, Bandwidth, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-058/

## Why this rule exists

Each artifact is written separately, so a single inconsistent name is common and innocent — but a reviewer cannot distinguish that from a registration assembled out of several businesses. Consistency across all four is what makes the sender verifiable.

## How to fix it

Use one customer-facing name everywhere, and make it the registered brand display name or DBA.

## Example of a compliant value

```text
Website header, description, message flow and every sample all say "Acme Coffee".
```