The HELP Keyword: What SMS Programs Must Reply With
The short answer: when a subscriber texts HELP to your number, your program must reply automatically with, at minimum, the name of the program or organization and a way to get support, such as a customer care phone number, email address, or website. That expectation comes from the CTIA Messaging Principles and Best Practices, the industry framework US wireless carriers enforce on application-to-person (A2P) messaging, and it is baked into 10DLC campaign registration: reviewers check that HELP is configured and that your opt-in disclosures tell subscribers it exists. HELP is the service-desk companion to STOP; where STOP ends the relationship, HELP answers "who is texting me and how do I reach a human?"
Where the HELP Requirement Comes From
Unlike the STOP opt-out, which connects directly to consent revocation under the TCPA (47 U.S.C. 227) and the FCC's rules (47 CFR 64.1200), the HELP keyword is primarily a carrier-governance requirement. The CTIA Messaging Principles and Best Practices direct message senders to support standard keywords, HELP among them, and to make sure the response identifies the program and provides contact information. Carriers and the 10DLC registry apply these principles as conditions of sending: campaigns are vetted for HELP handling at registration, and programs that ignore standard keywords risk filtering, suspension, or campaign revocation.
There is a legal undertone as well. A subscriber who cannot find out who is texting them or how to make it stop is exactly the situation consumer-protection frameworks are designed to prevent, and confused recipients file complaints, which is the metric carriers watch most closely. A clear HELP response reduces complaints, keeps your sending reputation clean, and often deflects a STOP from someone who just had a question.
Required and Recommended Elements of a HELP Response
| Element | Status | Example |
|---|---|---|
| Program or organization name | Required (CTIA best practice) | "Riverdale Food Bank Alerts" |
| Support contact: phone, email, or URL | Required (CTIA best practice) | "Call 555-0100 or email support@example.org" |
| Opt-out reminder ("Reply STOP to cancel") | Strongly recommended | "Reply STOP to unsubscribe" |
| "Msg and data rates may apply" | Recommended | Standard disclosure line |
| Message frequency | Recommended for recurring programs | "Msg frequency varies" |
| Link to terms or FAQ page | Optional | "Info: example.org/sms-terms" |
A complete response that fits comfortably in one SMS segment might read:
- "[Program Name]: For help, call 555-0100 or visit example.org/support. Msg and data rates may apply. Reply STOP to cancel."
- "[Organization] Alerts: Questions? Email support@example.org. Msg frequency varies. Reply STOP to opt out."
Keep it to one message, lead with the program name (the subscriber may have forgotten who you are, which is often why they texted HELP), and make the contact method one your team actually monitors.
Configuration Requirements That Trip Programs Up
- HELP must work at every stage. The keyword should return the response whether the sender is an active subscriber, someone mid-way through a double opt-in confirmation, or a person who already texted STOP. An opted-out user texting HELP should still learn who you are; do not treat their HELP as a re-subscription.
- Match variants and case. Handle "help", "HELP", "Help", and common adjacent phrasings ("info" is a frequently supported companion keyword). Standard keyword matching should ignore case and surrounding whitespace.
- Every number needs it. If you send from multiple long codes or a toll-free number plus a 10DLC number, each sending number must return a correct, program-specific HELP response. A shared generic reply that names the wrong program is a vetting red flag.
- Advertise it at opt-in. The CTIA framework expects "Reply HELP for help" (with STOP language) in your opt-in disclosures and welcome message, not just silent back-end support. Your consent form and confirmation messages should both mention it.
- Keep the contact info current. A HELP response pointing to a disconnected number or an unmonitored inbox fails the purpose of the requirement. Review the response text whenever your support channels change.
- Do not let HELP dead-end. If a subscriber replies again after the auto-response with an actual question, someone (or something) should answer. Two-way programs handle this natively; broadcast-only programs should route replies to a monitored queue.
HELP and STOP: Companion Keywords, Different Jobs
HELP and STOP are the two standard keywords every A2P program must support, and they are designed to work as a pair. STOP executes consent revocation: under the FCC's rules, opt-out requests must be honored, and the confirmation flow has its own tight requirements, covered in our guide to SMS unsubscribe message examples. HELP, by contrast, keeps the subscriber informed without changing their status: it identifies the program, supplies a support channel, and reminds them that STOP exists.
Programs that get HELP right often see it absorb interactions that would otherwise become opt-outs or carrier complaints. A subscriber who wonders "why am I getting these?" and receives a clear answer with a human contact frequently stays subscribed; the same subscriber met with silence texts STOP, or worse, reports the message as spam. In that sense HELP is not just a compliance checkbox but a retention and deliverability tool.
Both keywords sit inside the larger CTIA framework covering consent, disclosure, content, and number use; for the full picture of what carriers expect from a messaging program, see our overview of the CTIA Messaging Guidelines.
Special Considerations for Nonprofits, Healthcare, Schools, and Government
Mission-driven and public-sector programs should treat the HELP response as a front door, not a formality. Healthcare programs operating under HIPAA (45 CFR Parts 160 and 164) should keep the HELP response free of any protected health information and route clinical questions to a secure channel; the auto-reply should name the program generically ("[Clinic] Appointment Reminders") and point to the office line. Government programs carry effective-communication and language-access obligations (ADA Title II at 28 CFR 35.160, Title VI at 42 U.S.C. 2000d, and Executive Order 13166), so consider returning HELP responses in the languages your program advertises in and ensuring the listed contact channel is accessible, for example a phone line that supports relay services under the FCC's TRS rules (47 CFR Part 64, Subpart F). Schools and universities should point HELP to an office that families actually recognize, not a vendor's generic support desk.
Testing and Maintaining Your HELP Flow
HELP handling breaks quietly: a platform migration resets the auto-reply to a default template, a new sending number launches without keywords configured, or the support line in the response text changes owners. Build a simple maintenance routine around three checks. First, test from a real handset, not just the platform's simulator, and do it for every sending number you operate; text HELP as an active subscriber, as an opted-out number, and as a number that has never interacted with the program, confirming the response is correct in all three states. Second, verify the content: does the response still name the current program, and does the listed phone, email, or URL still reach a monitored destination? Third, review the logs: a sudden spike in HELP traffic usually means a recent message confused people, which is worth knowing for reasons beyond compliance.
Schedule the full check quarterly and after any change to numbers, vendors, or support channels. Keep the HELP response text under version control alongside your opt-in disclosure language, since 10DLC campaign records describe your keyword handling and material drift between what you registered and what you actually send is the kind of inconsistency carrier audits notice.
This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your own obligations with qualified counsel or the relevant regulator.
Frequently Asked Questions
What is the HELP keyword in SMS?
HELP is a standard reserved keyword that any subscriber can text to an A2P messaging program to find out who is sending the messages and how to get support. Under the CTIA Messaging Principles and Best Practices, programs must respond automatically with the program name and contact information, and most responses also restate the STOP opt-out instruction.
What must a HELP response include?
At minimum, the program or organization name and a support contact such as a phone number, email address, or website. Best practice adds "Reply STOP to cancel," "msg and data rates may apply," and message frequency, all within a single message.
Is the HELP keyword legally required?
It is an industry requirement rather than a statutory command. The TCPA and FCC rules focus on consent and opt-out, while HELP support comes from the CTIA Messaging Principles and Best Practices, which carriers enforce through 10DLC campaign vetting and ongoing filtering. Practically, a program that does not support HELP will have trouble getting and staying approved to send.
Should HELP work for people who already opted out?
Yes. An opted-out recipient who texts HELP should still receive the identification and contact response, and their opted-out status should not change. This lets someone who forgot why they are in your database learn who you are without being re-subscribed.
Does texting HELP cost the subscriber anything?
The subscriber's ordinary message and data rates may apply, which is exactly why the standard disclosure line appears in opt-in language and in the HELP response itself. The program does not charge the subscriber for the keyword interaction.
Standard Keywords Handled Out of the Box
FRANSiS configures HELP and STOP handling automatically on every number, with program-specific responses you control, and its AI Powered Helper picks up the conversation when subscribers reply with real questions, so subscribers who ask for help get a response. Contact us to see how it works.
