A customer texted STOP: what just happened, and what to do next

You sent a customer a perfectly normal message, maybe a reminder about tomorrow's appointment, and the reply came back as one word: STOP. Now the conversation looks locked in your texting app, there's a warning banner you've never seen before, and you're not sure whether you just lost a customer or broke a law.

One STOP is not a lawsuit, and most of the time it isn't even anger. But what you do in the next few minutes matters, because the fastest way to turn a routine opt-out into genuine legal exposure is to try to work around it.

What technically happens the moment someone texts STOP

STOP is a reserved keyword in business texting. When a customer sends it to a business number, a well-built platform flags that number as opted out and blocks future outbound texts to it. Most platforms also send one final automated confirmation, something like "You have been unsubscribed. No more messages will be sent." That confirmation is standard practice: as of mid-2026, a single immediate confirmation with no marketing in it is treated as part of the opt-out, not a new message.

This happens at the system level, not in your app's settings. You didn't do it, and on most platforms you can't undo it yourself, which is by design. The block is the system protecting you from accidentally texting someone who just revoked consent.

Why so strict? In the US, texting someone after they've opted out is exactly where TCPA statutory damages live: $500 to $1,500 per violating text, and every text after the STOP is potentially its own violation. Since the FCC's 2025 rule changes, consumers can revoke consent by any reasonable method and revocations must be honored within 10 business days. STOP is the clearest possible revocation, so platforms built for business texting treat it as immediate.

The mistakes that turn one STOP into a lawsuit

A single STOP costs you nothing. The damage comes from what people do next, usually with good intentions. These are the moves to avoid:

• Texting them from another number. Your personal cell, a second business line, a teammate's phone. Treat the opt-out as covering your business, not just the number they texted. "Sorry to bother you, just confirming Thursday" from your personal phone is still a business text to someone who said stop.
• Manually adding them back. If your platform lets you clear the block yourself, don't. Opting back in has to come from them.
• Sending one last message to apologize or explain. The confirmation the system already sent is the last message. Yours would be a new one, after revocation.
• Calling repeatedly to ask why or to talk them back into texts. One polite call about an existing job is normal business. A pressure campaign to undo an opt-out looks terrible and defeats the point of honoring it.

The pattern behind all four: treating STOP as an obstacle to route around instead of an instruction to follow. Texts after a documented opt-out make an easy case, because the revocation is timestamped and the violation is on paper.

Was it even meant for you?

Here's the scenario that trips up service businesses: the customer texted STOP, but they still want the appointment. Maybe they were clearing out reminder texts from every business at once. Maybe a kid had the phone. Maybe they thought STOP only killed the marketing messages, not the conversation with you.

It doesn't matter. STOP applies to the number, not to what they meant. Keep the job on the schedule, show up as planned, and honor the block in the meantime. Don't cancel work because of an opt-out, and don't text to double-check the appointment either. If you genuinely need to confirm something, call once, or email if you have an address.

If they mention it when you see them ("why did your reminders stop?"), that's your opening. Tell them what happened and how to turn texts back on.

How opting back in actually works

Only the customer should lift the block, and they do it by texting a keyword, usually START (some systems also accept UNSTOP or YES), to the same number they opted out from. That single text tells the platform they've re-consented, and normal messaging resumes.

The whole value of the keyword system is that consent and revocation are recorded actions taken by the customer, with timestamps, not notes in your CRM that say "Dave said it was fine."

So when a customer says in person or on the phone that they want texts again, tell them: "No problem. Text START to this number and it'll switch back on." If they'd rather you do it for them, the block should stay until their START arrives. Once it does, you're back to normal.

Handling it operationally so nobody on the crew texts them again

In a one-person shop, STOP is easy: you saw it, you'll remember. In a three-person crew it's a landmine. The office honored the opt-out, but a tech who has the customer's number saved texts "on my way" from his personal cell the next morning. Now you have a post-revocation text and no record of why it seemed fine.

The fix is structural, not a memo. All customer texting goes through one business number and one system, so the block is enforced by software instead of memory. When a STOP comes in, close the conversation with a short internal note ("opted out 7/10, keep Thursday appointment, call if needed") so the next person who opens it knows the situation in five seconds.

If your crew is still texting customers from a mix of personal phones, this is the strongest single argument for stopping: opt-outs simply cannot be honored reliably across four separate phones.

US vs Canada, briefly

In the US, the TCPA is the hammer: $500 to $1,500 in statutory damages per violating text. STOP is the cleanest version, honored immediately in practice.

In Canada, CASL governs commercial messages. It requires an unsubscribe mechanism, and consent can be implied for limited windows (roughly two years after a purchase, six months after an inquiry). Both regimes treat conversational one-to-one replies to a customer who texted you differently from marketing blasts, but neither tolerates messaging someone who has clearly said stop.

Operationally, run one policy on both sides of the border: STOP means no more outbound texts until they text START.

What your platform should do automatically

You should not be maintaining a do-not-text list in a spreadsheet. A platform built for business texting should block the number the instant STOP arrives, keep it blocked for everyone on the team, accept START without you touching anything, and keep a record of consent so you can show when and how a conversation started.

Loonext covers the core of that out of the box: STOP is honored instantly, future sends to that number are blocked, and consent (name and date) is recorded when you start a conversation. Details are on the compliance page. Whatever tool you use, verify it accepts START automatically and does the rest before you trust it with customer texting.

STOP is not an emergency, it's an instruction. Honor it, note it, keep the job, and let START come from them.

This article is general information, not legal advice. If you are unsure how the rules apply to your business, talk to a lawyer.