Does One Do Not Call Request Bind Your Affiliates and Sister Brands?
Not automatically, but don’t count on the gap. The FCC’s rule says a stop request applies to the company that made the call and doesn’t reach affiliates “unless the consumer reasonably would expect them to be included.” That qualifier is where multi-brand companies get hurt. If a customer would see two brands as the same business, a text from the second brand after a stop request to the first looks like a violation to a plaintiff, and the company has to argue about customer expectations.
What does the rule say about affiliates?
The text is in the internal do-not-call provisions of 47 C.F.R. § 64.1200(d)(5): “In the absence of a specific request by the subscriber to the contrary, a residential subscriber’s do-not-call request shall apply to the particular entity making the call (or on whose behalf a call is made), and will not apply to affiliated entities unless the consumer reasonably would expect them to be included given the identification of the caller and (for telemarketing calls) the product being advertised.”
The sentence does its work in several places. The default is narrow: the request applies to the entity that made the call or on whose behalf it was made. The exception depends on the consumer’s expectation, not on the company’s corporate chart. And the test looks at two facts, how the caller identified itself and what product it advertised.
The FCC explained the reasoning when it adopted the rule in 2003. In its Report and Order, FCC 03-153, it described the principle this way: affiliates fall within the established business relationship exemption “only if the consumer would reasonably expect them to be included given the nature and type of goods or services offered and the identity of the affiliate.” It added that the approach “offers flexibility to companies whose subsidiaries or affiliates also make telephone solicitations, but it is based on consumers’ reasonable expectations of which companies will call them.”
Is the established business relationship the same question?
It is closely related, and the rule treats them in parallel. The definition of an established business relationship in 47 C.F.R. § 64.1200(f)(5) says that a “subscriber’s established business relationship with a particular business entity does not extend to affiliated entities unless the subscriber would reasonably expect them to be included given the nature and type of goods or services offered by the affiliate and the identity of the affiliate.”
So the same expectation test controls two questions. Can the second brand rely on the customer’s relationship with the first, so that the Registry doesn’t bar the call? And does a stop request to the first brand bind the second? If the answer to the first question is yes because customers would expect the brands to be connected, the answer to the second is probably yes as well. A company can’t comfortably argue that customers see two brands as one for purposes of calling and as two for purposes of stopping.
I think that’s the most useful single point for a compliance team. Pick one answer about how your customers see your brands, and use it in both places.
What if we share a stop request with another company?
The same rule limits sharing. A company making telemarketing calls “must obtain a consumer’s prior express permission to share or forward the consumer’s request not to be called to a party other than the person or entity on whose behalf a call is made or an affiliated entity,” under § 64.1200(d)(3). In practice, that means you can pass a request along to an affiliate without separate permission, but a third-party marketing partner needs the consumer’s consent. If a vendor keeps your list, the same section makes you responsible for its mistakes.
How should a multi-brand company handle suppression?
I’d start from a conservative position, because the legal test is a fact question and the cost of a wrong answer is a statutory claim. Under 47 U.S.C. § 227(c)(5), a person who received “more than one telephone call within any 12-month period by or on behalf of the same entity” in violation of the regulations may recover “up to $500 in damages for each such violation,” and a court “may, in its discretion, increase the amount of the award to an amount equal to not more than 3 times” that amount for willful or knowing violations.
A few practices reduce the risk:
| Practice | What it does | What to document |
|---|---|---|
| One suppression list for brands that share a name, logo, app, or loyalty program | Treats a stop to any brand as a stop to all | The brand map and the reason each brand is in the group |
| Brand-level lists for brands customers wouldn’t connect | Respects the narrow default in the rule | The facts showing separate identity: names, ownership disclosures, marketing |
| A documented decision for each brand pair | Shows the company considered the expectation test | The decision-maker and date, and the facts relied on |
Brand identity is a fact question, so keep evidence. Screenshots of how each brand’s texts identify the sender help show what the consumer would expect, and so does the legal name in the footer. Whether a customer logs in to a shared account is also worth recording.
What does a sister-brand problem look like in practice?
Take a hypothetical company that runs a hotel brand and a separate spa brand under one rewards program. A guest texts STOP to the hotel’s promotional number. Two weeks later the spa brand, which draws its list from the rewards database, sends an offer from a different number. The spa’s message carries its own name, but the offer is addressed to rewards members and comes through the same app. A plaintiff will argue that a guest who joined one program would expect both brands to honor the request. The company will argue that the spa is a separate business. Neither side can win that argument from the corporate charts alone.
The facts that matter are the ones the FCC’s own wording points to: how the caller identified itself and what product it was advertising. If the spa’s message is branded as part of the rewards program, the company has made the plaintiff’s argument for it. If it’s branded as the spa and sent to people who joined the spa’s own list, the company’s position is much stronger. This is why I’d review sender identification, not only the suppression logic, whenever two brands share customers.
What about the new revocation rule?
A separate rule is delayed. The FCC’s revocation rules, adopted in 2024, include a provision that a revocation made in response to one kind of message applies to all future robocalls and robotexts from that caller on unrelated matters. The Consumer and Governmental Affairs Bureau first delayed it to April 11, 2026, in DA 25-312, and then in DA 26-12 found “good cause exists to extend the effective date for this requirement until January 31, 2027.” That provision concerns one caller’s messages across subject matters, not affiliates, but it points the same direction. Systems that can’t apply one customer’s stop request across the company’s own brands and message types are going to have a harder time on both fronts.
What to gather if a sister-brand claim arrives
- Pull the stop request to the first brand, with the date it arrived, the channel, and the words the customer used.
- Pull the first message from the second brand after that date, and the sender identification it carried.
- Collect the brand map, including the legal entities and any shared accounts or marketing platforms.
- Find the written do-not-call policy in force for each brand and the training records.
- Wait to answer a demand letter or contact the person until a lawyer has reviewed the file.
The firm’s TCPA litigation defense page describes how these claims move through court. For related reading, see the earlier post on internal do-not-call policy claims and on franchisor liability for franchisee texts.
Questions multi-brand companies ask about stop requests
If a customer stops texts from one brand, can another brand text them?
Only if the customer wouldn’t reasonably expect the brands to be connected. The test is the customer’s expectation, based on how the second brand identified itself and what it was selling. When in doubt, treat the request as covering both.
Does a parent company’s stop list cover its subsidiaries?
The rule treats affiliates as covered only when a consumer would reasonably expect it. A subsidiary with its own name and a different product line may stand apart. A subsidiary that markets under the parent’s name probably doesn’t.
Can we share our do-not-call list with a marketing partner?
Not without the consumer’s prior express permission, unless the partner is the entity on whose behalf you called or an affiliate. A separate marketing partner is the case the rule is aimed at.
What if the customer only stopped one type of message from one brand?
The affiliate rule and the new revocation rule address different problems, and I’d read them together. A customer who tells a brand to stop promotional texts may still expect billing notices from it. The internal list should record what was stopped, from which brand, and in which channel, so the company can apply the request as broadly as the customer’s words and the rules require.
Does the Registry work the same way across affiliates?
The Registry is national and federal. The question for affiliates is whether the established business relationship extends to them, and the definition uses the same expectation test.
Defending claims across related brands
If your company has been sued or received a demand letter claiming that one brand texted a customer who had asked another brand to stop, the brand map and the sender identification will decide much of the case. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving do-not-call requests across affiliated brands. Contact Rosenberger + Kawabata online for a free and confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200, as published in the eCFR on March 15, 2026. The FCC orders are Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, Report and Order, FCC 03-153 (July 3, 2003), DA 25-312 (Apr. 7, 2025), and DA 26-12 (Jan. 6, 2026).
This post is general information about the Telephone Consumer Protection Act and related laws as of March 15, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.