Marketing Agency TCPA Liability: Who Initiates a Client’s Texts?

A marketing agency and its client can both face a Telephone Consumer Protection Act suit over the same text campaign. The agency that writes and schedules the messages can be treated as the party that “initiates” them, and the client whose products they promote can be held vicariously liable. Neither side’s exposure is automatic. Control of the campaign and the paperwork between agency and client usually decide it, which leaves a sued agency or client more room to defend than the complaint suggests.

Is the agency or the client the one that “initiates” the text?

Either party can be the initiator under the Telephone Consumer Protection Act, and sometimes both are. The statute makes it unlawful “to make any call (other than a call made for emergency purposes or made with the prior express consent of the called party) using any automatic telephone dialing system or an artificial or prerecorded voice” to a cell phone, under 47 U.S.C. § 227(b)(1)(A). The Supreme Court called it “undisputed” that a text to a cell phone qualifies as a call under that provision, in Campbell-Ewald Co. v. Gomez. An autodialer is equipment that generates numbers randomly or in sequence, which most list-based texting tools don’t do under Facebook v. Duguid, and a prerecorded call plays a recorded or artificial voice instead of a live person. The FCC’s rule for marketing messages reaches anyone who will “Initiate, or cause to be initiated, any telephone call that includes or introduces an advertisement or constitutes telemarketing,” under 47 C.F.R. § 64.1200(a)(2).

The FCC filled the gap left by the undefined words “make” and “initiate” in its 2015 omnibus order, explaining that “Congress therefore put the responsibility for compliance with the law directly on the party” that makes or initiates automated and prerecorded calls, according to FCC 15-72. The same order said a party can be liable without dialing if it is “so involved in the placing of a specific telephone call” as to be deemed to have initiated it.

An agency that picks the audience and sets the send window for a client looks a lot like that party under FCC 15-72. The FCC’s 2013 Dish Network ruling also leaves room for the client to become the initiator. It described a seller that could be “so involved in the placing of a specific telephone call as to be directly liable for initiating it,” for example “by giving the third party specific and comprehensive instructions as to timing and the manner of the call,” according to FCC 13-54. A client that dictates the exact list and send time is closer to that line than one that approves a campaign brief.

Texting software raises a separate question, covered in how the make-or-initiate test applies to platforms. An agency sits between the platform and the client, which is exactly why it gets named.

The 2015 order also lists “the extent to which a person willfully enables fraudulent spoofing of telephone numbers” as a factor in deciding liability, per FCC 15-72. Agencies that pick caller numbers for clients should read up on caller ID risk from local presence numbers before a campaign rotates numbers it doesn’t control.

Can an agency be liable when a vendor hits send?

Yes, and the leading case, Campbell-Ewald Co. v. Gomez, involved an advertising agency that never sent a text itself. The Supreme Court described the defendant as “a nationwide advertising and marketing communications agency” hired by the Navy for a recruiting campaign, according to the Court’s opinion. The Navy approved texts to opted-in recipients only, and a subcontractor built the list and sent the message to more than 100,000 people.

In the 2014 appeal, Campbell-Ewald argued that it couldn’t be held liable because it outsourced the sending, according to the Ninth Circuit’s opinion in Gomez v. Campbell-Ewald Co.. The court rejected that argument, holding “that a defendant may be held vicariously liable for TCPA violations where the plaintiff establishes an agency relationship, as defined by federal common law, between the defendant and a third-party caller.” The panel also wrote that “it is unclear why a third-party marketing consultant shouldn’t be subject to that same liability” that a merchant faces for outsourced telemarketing.

The Supreme Court affirmed in January 2016. It wrote, “We do not overlook that subcontractor Mindmatics, not Campbell, dispatched the Navy’s recruiting message to unconsenting recipients,” and said it had “no cause to question” the FCC’s vicarious-liability ruling, according to the opinion.

Agencies sometimes hope McLaughlin Chiropractic Associates v. McKesson Corp. changes this. That 2025 decision held that “District courts are not bound by the agency’s interpretation,” so FCC rulings like Dish Network now get respect instead of binding weight, according to the Supreme Court’s opinion. It’s a weak argument here. The Ninth Circuit’s vicarious-liability holding starts from ordinary agency law, not only from deference to the FCC. In Gomez, the panel wrote, “We therefore assume that Congress intended to incorporate” ordinary tort rules of vicarious liability. An agency shouldn’t build its defense on McLaughlin.

When does the client answer for the agency’s texts?

The client answers for the agency’s texts if the agency acted as its agent, with actual or apparent authority, or if the client ratified the campaign by accepting its benefits. The Dish Network ruling says a seller “does not generally” initiate calls made through a third-party telemarketer, but “it nonetheless may be held vicariously liable under federal common law principles of agency,” according to FCC 13-54.

The FCC’s rules in 47 C.F.R. § 64.1200(f) use two labels that fit client and agency. A “seller” is “the person or entity on whose behalf a telephone call or message is initiated” to promote goods or services, and a “telemarketer” is “the person or entity that initiates a telephone call or message” for that purpose, under 47 C.F.R. § 64.1200(f). The client is almost always the seller. The agency is often the telemarketer.

The Commission’s Dish Network ruling lists facts that help a plaintiff prove apparent authority, and they’re the ordinary facts of an agency engagement. Those facts include access to “the seller’s customer information,” use of the seller’s trade name, and evidence “that the seller approved, wrote or reviewed the outside entity’s telemarketing scripts,” per FCC 13-54. Most clients approve every message their agency sends. That approval is good brand practice and bad TCPA evidence.

Do Not Call claims under 47 U.S.C. § 227(c)(5) give plaintiffs a second route to the client. These claims cover the National Do Not Call Registry, the federal list of numbers whose owners opted out of telemarketing, and each company’s internal opt-out list. The private claim belongs to someone who received “more than one telephone call within any 12-month period by or on behalf of the same entity” in violation of the rules, under 47 U.S.C. § 227(c)(5). For opt-outs, the rule says “If such requests are recorded or maintained by a party other than the person or entity on whose behalf the call is made, the person or entity on whose behalf the call is made will be liable for any failures to honor the do-not-call request,” under § 64.1200(d)(3). If the agency’s platform eats a STOP reply, the client owns that failure.

Consent under 47 C.F.R. § 64.1200(f)(9) also runs to the client. Prior express written consent, the signed agreement the rules require for autodialed or prerecorded marketing, must authorize “the seller to deliver or cause to be delivered” the messages, under § 64.1200(f)(9). An agency can’t borrow consent that a consumer gave to a different client. Keeping keyword opt-in and double opt-in records in the client’s name avoids that fight.

Exposure for agencies and clients at a glance

Who is sued Theory Source Exposure per text Defenses that answer it
Agency that ran the campaign Direct liability as the party that made or initiated the message 47 U.S.C. § 227(b)(1)(A), (b)(3); FCC 15-72 $500, up to $1,500 if willful or knowing Client or vendor made the key choices, prior express consent, no autodialer or prerecorded voice
Agency that hired a sending vendor Vicarious liability for the vendor’s messages Gomez v. Campbell-Ewald Co. (9th Cir. 2014) $500, up to $1,500 if willful or knowing No agency relationship, vendor acted outside its instructions, consent
Client whose products were promoted Vicarious liability as the seller FCC 13-54; 47 U.S.C. § 227(c)(5) Up to $500, up to $1,500 if willful or knowing No actual or apparent authority, no ratification, consent, fewer than two texts in 12 months
Client that kept or shared the opt-out list Failure to honor a stop request 47 C.F.R. § 64.1200(d)(3) Up to $500, up to $1,500 if willful or knowing Request honored within ten business days, request never received

How should agency contracts split the TCPA risk?

By assigning each job to the party that actually controls it, in writing. An indemnity clause is only as good as the balance sheet and insurance behind it. Clients should check the agency’s coverage for TCPA exclusions before relying on its promise to pay. The usual terms on indemnity and consent warranties in vendor contracts apply with one twist: the agency often supplies the list, the copy, and the platform, so its warranties have to cover all of them.

An agency agreement should say whose consent records support each list and who keeps them. It should also name the party that processes opt-out replies, and require transfer of each request on a set schedule, since the rule says the period to honor a request “may not exceed ten (10) business days from the receipt of such request,” under § 64.1200(d)(3). Every message should identify the client, because the same rule requires “the name of the person or entity on whose behalf the call is being made.” And subcontracting to a sending vendor should need the client’s written approval.

Agency and client interests split the day a TCPA complaint arrives, because each side’s best argument is often that the other one controlled the campaign. Agencies and clients that trade blame by email hand the plaintiff the agency evidence the case needs. A common-interest agreement and an early decision on tender and defense costs keep that from happening.

For outbound calls in a mixed campaign, the FTC’s Telemarketing Sales Rule adds an assisting-and-facilitating rule that bars “substantial assistance or support to any seller or telemarketer when that person knows or consciously avoids knowing” of a violation, under 16 C.F.R. § 310.3(b). It doesn’t carry the TCPA’s per-text statutory damages, but agencies should know where the federal telemarketing rules overlap and differ.

If a demand letter names the agency, the client, or both

  1. Freeze the campaign data under a litigation hold: the platform’s send logs, message templates, list files, and the consent record behind each number, wherever they sit.
  2. Export the opt-out history with dates, including STOP replies, the date each number was suppressed, and any transfers of requests between agency and client.
  3. Collect the Do Not Call Registry scrub results and the registry version dates used for each send.
  4. Gather the agency agreement, any subcontract with a sending vendor, insurance policies, campaign briefs, and the approval emails for each message.
  5. Talk to a lawyer before replying to the letter, contacting the person who received the texts, or tendering the claim to the other party.

The firm’s page on defending TCPA class actions in California covers how these claims move through state and federal court.

Questions agencies and clients ask about campaign texts

Is an agency liable if it only wrote the copy?

Direct liability under § 227(b) is unlikely for an agency that only wrote the copy, because writing a message is a step removed from placing the call. The harder question is vicarious liability for whoever sent the text. If the agency hired that vendor or controlled the list, a plaintiff will argue agency, as in Gomez. If the client chose the list and send time, that argument weakens.

Can a client avoid liability by saying the agency picked the list?

Blaming the agency’s list choices helps the client, but it isn’t a complete answer. The client is the seller, and an agency hired to market its products usually has actual authority to do so. Stronger defenses ask whether the agency acted outside its instructions and whether consent existed. Contract terms requiring opt-in lists support the first.

Does consent a customer gave our agency cover a client’s texts?

Usually not for marketing texts that need written consent, because § 64.1200(f)(9) ties that consent to the seller, meaning the client whose products are promoted. A consumer who agreed to hear from one brand hasn’t agreed to texts about another brand, even if the same agency sends both.

Who has to honor a STOP reply sent to an agency’s number?

Both should honor it, but 47 C.F.R. § 64.1200(d)(3) puts the risk on the client. The FCC’s rule makes the seller liable when someone else keeps the opt-out list and fails to honor a request. Agency contracts should require the agency to suppress the number and pass the request to the client quickly, so both lists match within the ten-business-day window.

Sued over a client’s text campaign?

If your agency or company is defending claims over a campaign that someone else wrote or sent, the contracts and approval records between you usually decide who carries the exposure. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving agency-run text campaigns and vicarious liability for vendor messages. Contact Rosenberger + Kawabata online for a 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, and the Telemarketing Sales Rule provision is 16 C.F.R. § 310.3. The FCC rulings are the Dish Network Declaratory Ruling, FCC 13-54 (released May 9, 2013), and the 2015 Declaratory Ruling and Order, FCC 15-72 (released July 10, 2015).

The court decisions are Campbell-Ewald Co. v. Gomez, 577 U.S. 153 (2016); Gomez v. Campbell-Ewald Co., 768 F.3d 871 (9th Cir. 2014), aff’d, 577 U.S. 153 (2016); McLaughlin Chiropractic Associates v. McKesson Corp., 606 U.S. 146 (2025); and Facebook, Inc. v. Duguid, 592 U.S. 395 (2021).

This post is general information about the Telephone Consumer Protection Act and related laws as of January 21, 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.

← Back to Blog

Let’s Talk.