HELP must be supported even on one-time programmes
The requirementstatement
HELP keyword support is required regardless of whether the programme sends recurring messages.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.help_keywords
- Where it liveslayer
- OperationalOPERATIONAL
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- What the fix involvesfailureClass
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- CTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Declare HELP support and configure a reply, even for a single-message programme. The reply must name the brand and give a support route.
A compliant exampleexample
Help keywords: HELP, INFO
Rules you will hit next
One other rule reads campaign.help_keywords. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
OPS-HELP-ONE-TIME is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.