Skip to content

STOP, HELP, and the texts you are required to answer

The keywords US carriers expect every business texting program to handle, what your replies should say, and the mistake that leaves people opted out on one channel and reachable on another.

Sohail Safdar · · 6 min read

If you text customers in the US, a few words carry obligations. Handle them properly and nobody notices. Handle them badly and you get carrier filtering, complaints, and eventually a number that no longer delivers.

The words that matter

STOP, and the variants carriers treat the same way: STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. Any of them means stop texting this person. It takes effect immediately and lasts until they opt back in.

HELP, and INFO. Means "who is this and how do I reach you". You must answer, and this is the one message you deliberately send to somebody even after they have opted out, because the requirement is that asking for help gets help.

START, and UNSTOP, YES. Means they want messages again, and it lifts a previous STOP.

Carriers handle some of this at the network level, but you cannot rely on that and you should not: your own records are what you will be asked for.

What your replies should actually say

For STOP, confirm once and then genuinely stop:

Bright Smile Dental: You're unsubscribed and won't receive further messages. Reply START to resubscribe.

One confirmation. Not a "sorry to see you go, here's a discount". A retention attempt after STOP is the message most likely to turn an opt-out into a complaint.

For HELP, identify yourself and give a real contact route:

Bright Smile Dental: Appointment reminders and replies. Call (555) 123-4567 or visit brightsmile.example.com. Msg&data rates may apply. Reply STOP to opt out.

That is the carrier-expected shape: who you are, what the program is, how to reach a human, the rates disclosure, and how to stop.

The mistake almost everybody makes

Recording the opt-out against the conversation instead of against the person.

It is the natural thing to build. Someone texts STOP in a thread, you mark that thread opted out, and it looks correct, because the thread goes quiet.

Then one of these happens:

In each case somebody who told you to stop gets texted again. From their side there is no distinction between "our software modelled this at the wrong level" and "they ignored me".

The obligation attaches to the person, identified by the address you reach them at. Record it there, and every thread (existing or future, on any channel) inherits it.

Normalising the number, which sounds pedantic and is not

An opt-out stored as (555) 123-0000 against inbound traffic that arrives as +15551230000 is an opt-out that does nothing. It sits in your database looking recorded and matches no message you ever send.

Normalise to E.164 before you store it and before you look it up. If a staff member is typing a number into an opt-out form by hand, validate it rather than merely tidying it. A number typed without a country code should be rejected, not silently turned into something that looks like E.164 and is not.

Keep the evidence, not the conclusion

"We think they opted out" is not a record. What you want, per person:

That third one matters because a staff member should be able to record "they told me on the phone to stop texting" without needing a manager. The receptionist who was just told that is usually the most junior person in the room, and making her find somebody senior is how the instruction gets lost.

Lifting an opt-out is the opposite: that is a claim about somebody else's wishes, and it should need authority.

Frequency is the obligation nobody writes down

No rule caps you at a specific number of messages per day. But a program that texts three times a day gets STOPs, complaints, and carrier scrutiny, and that is a practical cap whether or not anyone wrote it.

Two things worth doing:

And separate purposes. A practice answering a customer's own question should not burn the allowance its appointment reminder needs.

Quiet hours

The commonly cited window is 8am to 9pm in the recipient's local time. Some states are stricter.

The part that gets missed: the recipient's local time, not yours. A single-location practice can ignore the distinction. The moment you have two locations in different timezones, "9pm" stops being one moment.

And a deferred message is better than a dropped one. A reminder that would land at 3am should be held until morning, not silently discarded, because the appointment is still tomorrow.

What you need in place before sending

Not legal advice. TCPA and state rules carry real penalties and change. Have counsel review your program.

How Frontiva handles it

Keyword handling is automatic and the AI is kept out of all three: STOP, START and HELP are answered by fixed code, not by a model deciding what to say to somebody who just asked to be left alone. HELP returns the carrier-required disclosure with your practice's own name and number, because a template with a placeholder in it is not what any customer saw.

Opt-outs are recorded against the address, so one STOP covers every thread you have with that number, on any channel, including ones opened later. Numbers are validated rather than merely normalised, and a staff member can record an opt-out with ordinary contact permissions while lifting one requires more.

Every outbound message (AI reply, reminder, automation, or a person typing) passes through a single check that reads purpose, consent, opt-out state, quiet hours and the frequency cap. A refusal names the rule that produced it, so you can tell a customer why rather than guessing.

You can see all of it on one screen: the wording your customers agreed to, the words the product acts on, who has asked you to stop, and why reminders were not sent.

A thread for somebody who has opted out shows as blocked in the unified inbox, so a staff member about to type a message sees it before they type rather than after the send is refused. Consent revocation covers the four other ways an opt-out arrives, none of which involves a keyword.

Frequently asked questions

Which keywords must a business texting program handle?

STOP, and the variants carriers treat identically: STOPALL, UNSUBSCRIBE, CANCEL, END and QUIT. HELP and INFO, meaning who is this and how do I reach you, which you must answer even to somebody who has already opted out, because the point of the requirement is that asking for help gets help. And START, UNSTOP or YES, which lifts a previous opt-out. Carriers handle some of this at the network level and you should not rely on that, because your own records are what you will be asked for.

Should an opt-out be recorded against the conversation or the person?

The person, identified by the address you reach them at. Recording it against the conversation is the natural thing to build and it looks correct, because the thread goes quiet, but the same number messaging you on another channel, a staff member starting a fresh thread next month, or a contact merge that drops the flag all produce a text to somebody who told you to stop. From their side there is no difference between modelling it at the wrong level and ignoring them.

Why does phone number formatting matter for opt-outs?

Because an opt-out stored in one format against traffic that arrives in another is an opt-out that matches nothing. Stored as (555) 123-0000 while your messages address +15551230000, it sits in the database looking recorded and does nothing at all. Normalise to E.164 before storing and before looking up, and validate rather than tidy: a number typed without a country code should be rejected, not quietly turned into something that resembles E.164 and is not.

What should a HELP reply say?

Who you are, what the program is, how to reach a human, the rates disclosure, and how to stop. For example: Bright Smile Dental, appointment reminders and replies, call 555 123 4567, msg and data rates may apply, reply STOP to opt out. It has to carry your own name and number rather than a template placeholder, because a placeholder is not what any customer saw.

Is there a legal limit on how many texts a business may send per day?

No fixed federal number, and there is a practical cap whether or not anyone wrote it down: a program texting three times a day collects opt-outs, complaints and carrier scrutiny. Cap automated messages per person over a rolling 24 hours rather than resetting at midnight, which would make 11pm and 12:01am two different days and double the cap, count per person rather than per conversation, and keep conversational replies out of the count entirely.

Get the next one by email

Email me when Frontiva publishes a new guide or post. At most one a week, nothing else, and an unsubscribe link in every one.

To keep spam out, we record your IP address, approximate location and browser with your message. Privacy Policy

Start free. Be live this week.

Built for dental, med spa, home services, and the businesses that live on the phone.