Platform Liability Under the TCPA: AI-Voice Claims Proceed
When a business hires one vendor to send its marketing texts and another to supply an artificial voice for its calls, which of them can be sued under the Telephone Consumer Protection Act? A federal court in Virginia recently said both can. Vendors that power automated calling, not just the business whose product is sold, can face TCPA claims for calls that run through their platforms. The same ruling narrows which claims survive, which matters to platform operators and the businesses that use them.
What the Virginia Court Decided in Lowrey v. Twilio
A federal judge allowed several TCPA claims to proceed against a texting and calling platform and an AI-voice provider, while dismissing others. The case is Lowrey v. Twilio, Inc., No. 6:25-cv-00116 (W.D. Va.), and Senior Judge Norman K. Moon issued the memorandum opinion and order on October 1, 2026. The plaintiff alleged that a company marketing probate services paid Twilio to place calls and texts and paid OpenAI to generate the messages and the artificial voice that answered when he called back.
Both companies asked the court to dismiss the claims against them. According to the opinion, Twilio argued it “did not make or initiate the calls because it had no control over the content of the messages or when and to whom messages were sent,” and OpenAI argued it “did not make or initiate the calls because its artificial voice technology did not engage until after the call was answered.” The idea was that because the two companies split the usual jobs of a telemarketer between them, neither one had “made” a call.
The court disagreed. In the ruling, it held that the complaint alleged enough to find that Twilio and OpenAI, “working in concert,” “made” and “initiated” calls “within the meaning of the TCPA.” The opinion reasoned that a provider “facilitate[s] the first actions, steps, or stages of” a call by supplying the artificial voice and answering the consumer who picks up. A ruling on a motion to dismiss assumes the allegations are true and decides only whether the claims may go forward. No court has found Twilio, OpenAI, or any defendant liable.
Who “Makes” a Call Under the TCPA?
Direct liability under the TCPA has long turned on who actually places the call. The statute makes it unlawful under 47 U.S.C. § 227(b)(1)(A)(iii) “to make any call” to a cell phone “using any automatic telephone dialing system or an artificial or prerecorded voice” without the called party’s consent, and under § 227(b)(1)(B) “to initiate any telephone call to any residential telephone line using an artificial or prerecorded voice to deliver a message without the prior express consent of the called party.” An automatic telephone dialing system, or autodialer, is equipment that stores or produces numbers with a random or sequential number generator and dials them. An artificial or prerecorded voice is a recorded or synthetic voice, now including an AI-generated one, in place of a live person.
Courts had generally read “make” and “initiate” to reach the party that physically places the call. The company whose product is being sold, often called the seller, was usually on the hook only through agency law, not directly. The opinion restates that background rule: direct liability “generally does not extend to sellers who do not personally make the phone calls at issue but only includes the telemarketers acting on behalf of those sellers.” What was new here was applying that rule to two vendors who each performed only part of a telemarketer’s job.
What the Ruling Changes for Platforms, and What It Doesn’t
The practical lesson for platform operators is blunt. A contract that assigns the dialing to one company and the voice to another will not, by itself, keep either out of a TCPA case. The court treated the two providers as modern telemarketers and found a plausible basis to hold each of them directly liable for the calls. Operators should expect plaintiffs to name the calling platform and the AI vendor alongside the advertiser, because this ruling hands them a theory that each one “made” the call.
The decision also narrowed the case, and those limits cut in the defense’s favor. In the ruling, the court held that the TCPA’s “do not call” protections in § 227(c) reach only home phone lines, concluding that “§ 227(c) only applies to residential landlines,” not cell phones. The court also followed the Seventh Circuit in holding that a text message is not a “telephone call” for the private Do Not Call action in § 227(c)(5), so claims built on texts to that subsection were dismissed. (The reach of that split is covered in this post on whether texts count as calls for Do Not Call suits.) The national Do Not Call Registry is the federal list consumers join to stop most telemarketing.
Two more limits matter to platforms. The court held, in its opinion, that two FCC identification and opt-out regulations, 47 C.F.R. § 64.1200(b)(1) and (b)(3), “do not provide private causes of action,” so a consumer cannot sue a vendor directly for breaking them. And the court declined to resolve the providers’ argument that their terms of service amount to the “reasonable practices and procedures” affirmative defense, ruling only that it was “premature to consider them at the motion to dismiss stage.” That defense is still available later in the case.
One strategic point is easy to miss. The court decided these questions for itself instead of deferring to the agency, noting that a court “is required to independently interpret the meaning of a statute and has no obligation to defer to an alternative construction by an executive agency.” For platform operators, that means older guidance written to favor industry is persuasive at best. The statute’s text, and how a given judge reads it, now drives the outcome. What survived in this case were the artificial-voice claims to cell phones under § 227(b)(1)(A)(iii), which is where the exposure for AI-voice calling sits.
What Platform Operators Should Preserve and Do Now
A company that operates a texting or voice platform, or that uses one to reach customers, protects itself by keeping the records that decide a TCPA case. When a demand letter or complaint arrives, move quickly on the following.
- Put a litigation hold on your call and text logs, your dialer and platform records, and the consent records for each number you called or texted.
- Pull the opt-out and internal do-not-call logs, with the date each request was received and honored.
- Pull the National Do Not Call Registry scrub records and the version dates used for each campaign.
- Gather the vendor and platform contracts, the integration or API configuration, the call scripts, and any artificial-voice or recorded audio files.
- Talk to a lawyer before responding to a demand letter, contacting the claimant, or offering to settle.
Where the call and text records are incomplete, that gap usually shapes the defense more than any legal argument. The firm’s TCPA defense attorneys in California page explains how these claims move through federal and state court.
If Your Platform or Your Company Is Named in a TCPA Case
If your company sends marketing calls or texts through a platform, or supplies the dialing or the voice that others use, a TCPA claim will depend on the call and consent records tied to each number. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving automated calls and AI-generated voices. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The ruling is Lowrey v. Twilio, Inc., No. 6:25-cv-00116, Memorandum Opinion and Order (W.D. Va. Oct. 1, 2026), available as the docket and document on CourtListener. The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227, and the FCC’s telemarketing rules are at 47 C.F.R. § 64.1200.
This post is general information about the Telephone Consumer Protection Act and related laws as of November 6, 2026. Allegations described in this post have not been proven. 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.