Analysis · Litigation & decisions
Doane v. Python Leads: A Lead Company Chief Executive Who Writes the Scripts Can Be Sued Where the Calls Land
Can an overseas call center's boss be sued in Massachusetts over calls she never dialed? In Doane v. Python Leads, LLC, No. 1:24-cv-12947-JEK (D. Mass. Dec. 4, 2025), Judge Kobick said yes, at least at the pleading stage. The motions to dismiss filed by the company's founder and chief executive officer (CEO) were denied.
On this page
The Alleged Setup
According to the complaint, a Florida lead generation company ran call centers in Pakistan, generating Medicare and final expense insurance leads by live transferring consumers to buyers. The plaintiff, whose Massachusetts cell number was on the federal and state do not call lists, said he got at least 23 calls in December 2021 and January 2022. When he asked the insurance lead buyer who sent them, it named the lead company and produced a spreadsheet saying he had given written consent. He says he never did.
He sued the company and its two cofounders under the Telephone Consumer Protection Act (TCPA), the Massachusetts Telemarketing Solicitation Act, and the state consumer protection law, Chapter 93A.
Standing
The CEO argued the plaintiff lacked standing because he had filed other TCPA suits and supposedly had multiple phones. The court said she offered no evidence for the phone theory, and prior lawsuits don't erase standing when the statute gives a cause of action to anyone who receives the prohibited calls.
Personal Jurisdiction Over the CEO
The CEO said she never personally called anyone in Massachusetts. But the plaintiff brought receipts:
- A podcast where she said she oversees "everything" and talks to the Pakistan callers "all day long, almost every single day."
- An email from her cofounder calling her the call center's owner.
- State filings listing her as CEO.
- The lead contract she signed, and payments from the buyer into her personal bank account.
- Records showing 198 Massachusetts consumers were live transferred over two years.
That was enough. Writing the scripts and running the operation started the "train of events" that caused calls to land in Massachusetts, so jurisdiction fit both the state long-arm statute and due process.
Not the Caller, but Still on the Hook
Here's a neat nuance. Under the Federal Communications Commission (FCC) view, you "initiate" a call by taking the steps to physically place it. The CEO didn't, so she wasn't directly liable. However, she could be vicariously liable under agency principles. Relying in part on Golan v. FreeEats.com, Inc., 930 F.3d 950 (8th Cir. 2019), the court found her alleged writing of scripts, training callers, and signing the lead contract plausibly showed she expressly authorized the calls.
The state law claims survived as well, including a Chapter 93A claim based on the calls and the alleged fake consent record.
Other defense arguments failed. There's no duty to mitigate TCPA damages, and consent is an affirmative defense she must prove, not something the plaintiff has to disprove. Her exhibits, including a claimed earlier settlement with the lead buyer, were struck because they weren't part of the complaint.
Takeaways
Running a lead shop from abroad doesn't put the people in charge out of reach. Public statements about how hands-on you are can become exhibit A. And if your consent records can't stand up, they may become part of a deception claim rather than a defense.
Read the District of Massachusetts order in Doane v. Python Leads.
Not legal advice. TCPA.com provides general information, not legal advice, and is not a substitute for the advice of an attorney. Do not rely on it. Verify any action with your own licensed lawyer before you take it. See our Terms of Use.
