Consent is a starting condition, not a checkbox
Text messaging rules and norms in most places start from the same basic principle: a business needs a real basis to text someone before doing it, and that basis looks different depending on whether the lead reached out first or the business is initiating contact. A lead who texted your number, filled out a form asking to be contacted, or otherwise clearly opted in has given consent for that kind of follow-up. Reaching out cold to a purchased or scraped list has not.
This is not a technicality to route around, it is the actual foundation of why texting leads works as a channel in the first place. People respond to texts because texting still feels personal and consensual in a way that gets abused quickly once businesses start treating it like email spam. Respecting the boundary is what keeps the channel useful for everyone using it honestly.
STOP has to work every time, not most of the time
The word STOP, and close variants like UNSUBSCRIBE or CANCEL, has become the near-universal way a recipient signals they want outreach to end. The expectation, reasonably, is that sending it works immediately and permanently. A lead who texts STOP and then receives another message a week later because the sequence was managed in a spreadsheet or a separate tool has every right to be frustrated, and the business has created real exposure for itself.
This is why STOP handling should live at the data layer, not in the logic of any one campaign or sequence. If opt-out status is checked and enforced centrally, every future message, from every campaign, respects it automatically. If it is only checked by whichever tool sent the last message, it is only a matter of time before a different tool or a different list misses it.
What good STOP handling actually looks like
A contact's opt-out status should be a single source of truth that every outbound path checks before sending anything, automated or manual. It should not be possible to accidentally message someone who has opted out just because they were added to a new list or a different campaign later. The system should refuse the send, not rely on whoever is running that campaign to remember to check.
- Opt-out status enforced centrally, not per campaign or per tool
- STOP recognized immediately, without requiring an exact keyword match
- Opt-out applies across every future campaign, not just the current one
- A clear HELP response available alongside STOP
This is not legal advice, and rules vary
Texting regulations and best practices differ by country, and sometimes by state or industry, and they change over time. Nothing here should be read as a legal opinion on what any specific business is required to do. Any business texting leads at meaningful volume, especially with outbound campaigns to purchased or aggregated lists, should get real legal guidance specific to its situation rather than relying on general guidance from a vendor's blog post.
Inbound and outbound carry different obligations
It is worth separating two situations that get talked about as if they were the same thing. Replying to a lead who texted your number first, filled out your form, or otherwise reached out directly is responding to an inbound message, and the consent question there is simpler: they contacted you. Initiating a new conversation from a lead list a business already has, outbound texting, is a different act, and it is where consent needs to be established and documented before the first message goes out, not assumed because the number was on a list somewhere.
Conflating the two is a common source of real problems. A business that treats every number in its CRM as fair game for outbound texting, because some of those contacts originally reached out through some other channel months or years ago, is making an assumption about consent that may not hold up, and it is worth being conservative rather than generous when that assumption is in doubt.
Documentation matters as much as the mechanism
Having a working STOP mechanism is necessary but not sufficient. Being able to show, after the fact, when and how a contact consented to be texted, and confirming that opt-out requests were honored immediately when they happened, matters for a business's own protection as much as for the lead's experience. A system that enforces opt-outs but keeps no record of consent or opt-out events is harder to defend if a dispute ever comes up.
HELP deserves the same seriousness as STOP
STOP gets most of the attention, but a working HELP response matters too. A recipient who is confused about why they received a message, or who wants to know who is texting them and why, should get a clear, honest answer, not silence or a generic canned reply that does not actually address what they asked.
Why this belongs in the platform, not the playbook
The businesses that get this wrong are rarely acting in bad faith. They are usually running consent and opt-out tracking manually, across spreadsheets and separate tools, and something falls through the cracks under normal operational pressure. Building consent and STOP enforcement into the system that actually sends the messages removes that failure mode instead of hoping every person managing a campaign remembers to check a list by hand.