# CON-124 — The sending entities must be named before consent is captured

> The authorised sending entities must be disclosed before the consumer acts, not on the confirmation screen or in the first message.

- **Rule ID:** CON-124
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `disclosure ordering on the opt-in surface`
- **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 crawled website or policy page
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** AT&T
- **Applies:** Applies to every 10DLC registration.
- **Depends on:** CON-123
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-124/

## Why this rule exists

Consent is given at the moment of the act, so a name disclosed afterwards was not part of what was agreed to. Brands get this wrong in a specific and understandable way: the confirmation page is where they put the full legal detail, because that is the page nobody has to be persuaded by.

## How to fix it

Move the entity names above the consent control, inside the sentence the consumer is agreeing to. Keep them on the confirmation as well if you like — the requirement is that they appear before the act, not that they appear only there. Done when the names are on screen at the moment the box is ticked.

## Example of a compliant value

```text
☐ Text me offers from Acme Coffee and my local Acme Coffee franchise location.

[Join] — the names appear above this button, not on the page it leads to.
```

## Notes

Depends on CON-123: where no entity is named at all, that is CON-123's finding and this rule has no ordering to judge.