How Far Does One Opt-Out Travel?

A stop reply answers less than you think#

A prospect answers an outbound message with one word: stop. Every team knows what happens next. The contact is suppressed, the sequence halts, somebody logs it, and that part is solved.

The question that never gets asked is how wide that stop goes. Across the one line it arrived on, across every line you run, across the other brand you sell under, across the agency running the program for you.

Federal rules answer all four. One answer depends on something most senders treat as a style choice.

• The do-not-call procedures in 47 CFR 64.1200(d) attach to a person or entity, not to a phone number. The rule requires a list of people who ask not to receive calls made by or on behalf of that entity (eCFR text current through 1 September 2026, read 19 September 2026).
• Paragraph (e) is the sentence that puts those procedures on your texts. The rules in (c) and (d) apply to telemarketing calls or text messages to wireless numbers, to the extent described in the Commission order FCC 03-153.
• Neither paragraph mentions the sending number, which is why a per-line mental model of opt-outs starts in the wrong place.

Adding lines multiplies capacity, not identities#

Scaling this channel means adding lines. Every vendor in the category sells it that way, because the daily ceiling sits on the line and the arithmetic is simple.

Tuco AI prints that arithmetic on its pricing page: limits stack linearly, ten lines gives 500 new conversations a day and a hundred lines gives 5,000 (tuco.ai/pricing, read 19 September 2026).

The math is right about throughput and silent about identity. Ten lines selling one company's product are one sender under the rule, and one stop request binds all ten.

• Blue Reacher paces a line at 50 opted-in or 30 cold new conversations a day, so the same scaling question arrives here the way it arrives anywhere else.
• Suppression on Blue Reacher attaches to the contact record and applies account-wide across every line, campaign and manual send. See how opt-out handling works.
• A platform that suppresses per line rather than per account turns the eleventh line into a fresh way to text somebody who already told you to stop.
• Worth testing rather than reading. Send to a suppressed number from a different line and watch whether the send is refused.

How you name yourself sets how far the stop reaches#

Two rules that look unrelated are wired together. One governs how you identify yourself in a message. The other decides which of your companies a stop request covers.

The identification rule at 64.1200(d)(4) asks for three things: the individual caller's name, the name of the entity on whose behalf the call is made, and a number or address that reaches that entity.

The scope rule at 64.1200(d)(5) then reads that identification back. A stop applies to the entity making the call and not to affiliated entities, unless the consumer reasonably would expect them included.

• The test is the consumer's reasonable expectation, given the identification of the caller and, for telemarketing calls, the product being advertised (47 CFR 64.1200(d)(5), read 19 September 2026).
• Sign as the parent company and a reader reasonably expects the stop to cover everything the parent sells.
• Sign as one named brand, on every message that contact ever gets, and the expectation narrows to that brand. The signature is doing legal work, not branding work.
• The coupling cuts both ways, so decide it once and deliberately, then write the decision down beside your message templates rather than leaving it to whoever drafts the next campaign.

The FCC is being asked to write that test down#

The agency opened this exact question ten days ago. Its draft Report and Order and Further Notice, FCC-CIRC 2609-05, carries a section headed Affiliates and Separate Lines of Businesses or Divisions.

Paragraphs 36 and 37 ask whether the existing standard should be modified, whether more specific guidance would help, and whether the rule should reach all robocalls rather than only exempted and telemarketing ones.

Financial and consumer groups have proposed actual rule text, and their proposal is stricter than the habit most senders have.

• The proposed 64.1200(a)(13), quoted in footnote 80: where an affiliate, line of business or division obtains a separate consent and holds itself out as that brand throughout all calls and texts, it would be deemed a separate sender.
• Read the two conditions together. Separate consent is the easy half. Holding yourself out as that one brand throughout every message is the half that fails in practice.
• One survey email under the parent name breaks the throughout, and the separation it was protecting goes with it.
• Status matters and gets reported loosely. This is a draft circulated 9 September 2026 for the Commission's 30 September open meeting, not a rule in force (FCC fact sheet DOC-424844A1, read 19 September 2026).

Your agency holds the list and you hold the failure#

Plenty of outbound programs run through somebody else. An agency owns the sending account, a platform owns the suppression table, a contractor owns the CRM the flags live in.

The rule assigns that risk in one sentence. Where requests are recorded or maintained by a party other than the entity on whose behalf the call is made, that entity is liable for any failure to honor them.

Outsourcing the list is fine. Outsourcing the consequence is not. Ask for the export in writing before the first send rather than after the first complaint.

• 64.1200(d)(3) also requires the request be recorded and the number placed on the list at the time the request is made, rather than whenever the next batch job runs.
• Sharing a stop request outside your own entity or an affiliated entity needs the consumer's prior express permission, which rules out handing a suppression file to a partner because it seemed helpful.
• Agencies running one line per client sub-account meet this from both sides at once: each client is the entity, and the agency is the party holding the record.
• Retries in automation tools make the gap wider, because a replayed send does not re-ask whether a suppression landed between the attempts.

Two clocks run on every stop request#

The deadline and the memory are different numbers, and most teams can quote only one of them.

64.1200(d)(3) says a do-not-call request must be honored within a reasonable time from the date it is made, and that period may not exceed ten business days.

64.1200(d)(6) says the request must be honored for five years from the time it is made, and that a record of the request is kept.

• Ten business days is a ceiling rather than a target. Blue Reacher suppresses in seconds, and treating the ceiling as the plan is what produces the message that goes out on day six.
• Five years outlives most CRM migrations, most agency contracts and most platform changes. A suppression list that does not survive a migration has failed the rule quietly.
• TCPA claims run four years under 28 U.S.C. 1658, so the retention duty outlasts the window in which somebody can bring one.
• Keep the record of the request, not only the flag on the row. A flag says the state changed and a record says when, how and by whom.

What this means for a B2B outbound list#

One scope caveat, stated plainly. The procedures in (d) are written around telemarketing calls to a residential telephone subscriber, and (e) extends (c) and (d) to wireless numbers.

B2B lists are full of personal mobile numbers, and whether a given number counts as residential turns on how it is used rather than on the label your CRM put on it.

Treat the procedures as the floor for any list you cannot cleanly show is all business lines, and take the edge cases to counsel rather than to a vendor page.

• This page is a reading of published rule text rather than legal advice, and every citation is given so you can check the sentence yourself.
• State law adds a layer, with its own registries and its own scope. See whether iMessage marketing is legal for the state picture.
• None of this depends on the channel. A stop is a stop whether it arrived on a blue bubble, a green one, or a voicemail.
• The narrower question of designating one method to revoke sits in the FCC draft order on exclusive opt-out methods.

Five checks to run this week#

The whole thing reduces to five questions you can answer in an afternoon, and most teams fail two of them.

Run them in order, because the first answer changes what the rest mean.

• Does a stop received on one line suppress that contact on every other line you run? Test it with a real number instead of reading a feature page.
• How do your messages identify the sender, and is that the same name on every message a given contact will ever receive from you?
• If you sell under more than one brand, which one does a stop cover today, and is that the answer you intended?
• Who physically holds the do-not-call record, and can you export it yourself this afternoon without asking anyone?
• Can you produce the request itself, with a date on it, for a contact who opted out three years ago?

Frequently asked questions