# WEB-057 — Website content must be consistent with the declared use case

> What the website shows the business doing must be consistent with the campaign use case.

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

## Why this rule exists

The use case determines the consent standard and throughput a campaign receives, so reviewers verify it against the business rather than accepting the selection. A site that is plainly an e-commerce store behind a 2FA-only registration reads as an attempt to obtain transactional treatment for marketing traffic.

## How to fix it

Choose the use case that matches what the site shows the business doing. Where you genuinely send several categories, use MIXED and collect promotional-grade consent.

## Example of a compliant value

```text
A retail site sending promotions and order updates → MIXED, not ACCOUNT_NOTIFICATION.
```