# MSG-056 — A no-reply route must disclose that replies are not received

> Where the sending route cannot receive inbound texts, every message must clearly disclose that replies are not monitored.

- **Rule ID:** MSG-056
- **Layer:** Message content (`MESSAGE_CONTENT`)
- **Checks:** `campaign.sample[] + 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:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** CTIA, FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/message-content/msg-056/

## Why this rule exists

Telling a consumer to "reply STOP" on a route that discards inbound messages is worse than saying nothing: they believe they have opted out and keep receiving messages. If replies genuinely cannot be received, the opt-out route must be stated some other way.

## How to fix it

Use a route that receives replies. If you genuinely cannot, disclose it in every message and give a working alternative opt-out route.

## Example of a compliant value

```text
Acme Coffee: your order is ready. This number does not receive replies — manage texts at https://acmecoffee.com/sms-preferences
```