# WEB-059 — The site referenced in the message flow must be the registered brand site

> The website referenced inside the message flow must belong to the same business as the registered brand website.

- **Rule ID:** WEB-059
- **Layer:** Website (`WEBSITE`)
- **Checks:** `campaign.message_flow + brand.website`
- **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
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-059/

## Why this rule exists

A message flow pointing at a different domain usually means consent is collected on a partner or platform property, which raises the consent-transfer question directly. Where it is legitimate, it needs explaining rather than leaving for a reviewer to infer.

## How to fix it

Reference the brand's own domain in the message flow. Where consent is collected on a third-party platform, say so explicitly and explain the relationship.

## Example of a compliant value

```text
Brand website acmecoffee.com; message flow references acmecoffee.com/signup.
```