# WEB-062 — An undeclared additional use case must be surfaced

> Where the website or description implies a message category the campaign has not declared, it must be flagged.

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

## Why this rule exists

Live traffic must match the registered use case, and an undeclared category is a violation waiting to happen the first time that content is sent. Catching it at registration is the difference between adding a use case and being filtered later.

## How to fix it

Declare every category you will send, or remove the undeclared one from your plans. MIXED covers promotional plus transactional.

## Example of a compliant value

```text
Site shows cart-abandonment flows → declare MARKETING (or MIXED), not ACCOUNT_NOTIFICATION alone.
```