# XBC-011 — Opt-in description must carry the registered brand name

> The CTA / message-flow field must name the brand, matching the registered Brand or DBA.

- **Rule ID:** XBC-011
- **Layer:** Brand ↔ campaign (`CROSS`)
- **Checks:** `brand.display_name + campaign.message_flow`
- **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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Bandwidth, Telnyx, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/cross/xbc-011/

## Why this rule exists

The reviewer reads the message flow to confirm the consent a consumer gave was consent to hear from THIS brand. A flow describing an anonymous opt-in cannot establish that, and it is also the exact pattern a reseller registering someone else’s traffic would produce.

## How to fix it

Name the brand explicitly in the opt-in description, and quote the consent wording the consumer agrees to — that wording should name the brand too.

## Example of a compliant value

```text
Customers opt in at acmecoffee.com/signup by ticking an unchecked box agreeing to receive recurring automated marketing texts from Acme Coffee.
```