# CON-HELP-BACKED — Declared HELP support must have a help message behind it

> A campaign declaring HELP keywords must supply the help reply that will be sent.

- **Rule ID:** CON-HELP-BACKED
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `campaign.help_keywords + campaign.help_message`
- **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:** TCR, CTIA, Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-help-backed/

## Why this rule exists

Declaring HELP support without configuring a reply produces the worst possible outcome: a consumer asks who is texting them and gets silence or an error. CTIA requires HELP to always produce a response, whether or not the requester is even subscribed.

## How to fix it

Write the HELP auto-reply, naming the brand and giving a real support contact a person can actually reach.

## Example of a compliant value

```text
Acme Coffee: for help, email support@acmecoffee.com or call 415-555-0134. Msg & data rates may apply. Reply STOP to unsubscribe.
```