Note: This article is for general informational and editorial purposes only. It is not legal advice.
Introduction: When “Wrong Number” Becomes a Very Expensive Phrase
In the world of consumer finance, a wrong-number phone call may sound like a small mistake. Someone picks up, says, “You have the wrong person,” and life moves on. In TCPA litigation, however, that tiny moment can become a legal snowball rolling downhill with a calculator, a subpoena, and a very serious facial expression.
American Express has found itself under renewed pressure in a high-stakes Telephone Consumer Protection Act discovery fight involving alleged prerecorded calls to wrong-party or “never call” numbers. The case, Duke v. American Express Company, has become a sharp reminder that TCPA lawsuits are not only about whether calls were made. They are also about whether a company can produce the data needed to prove who was called, when, why, how, and with what kind of technology.
The latest discovery dispute matters because it reaches the heart of modern TCPA class action litigation: call logs, consent records, wrong-number notations, vendor systems, prerecorded voice technology, and the data architecture behind high-volume outbound calling. In simple terms, the court signaled that if a major caller wants to oppose class certification, it cannot also keep the most relevant call data out of reach.
What Is the TCPA, and Why Does It Create So Much Risk?
The Telephone Consumer Protection Act, commonly called the TCPA, is a federal law designed to protect consumers from certain unwanted robocalls, robotexts, prerecorded voice messages, and automated dialing practices. For financial institutions, lenders, insurers, healthcare companies, retailers, lead generators, and debt collectors, it is one of the most important consumer-contact laws in the United States.
The law generally restricts certain calls made using an automatic telephone dialing system or an artificial or prerecorded voice without the required consent. For calls to cell phones, consent is often the key issue. The problem for companies is that consent is not always clean, simple, or permanent. Phone numbers get reassigned. Customers mistype information. Families share plans. Old numbers become new numbers. Databases age faster than an avocado on a warm kitchen counter.
The TCPA also carries serious financial consequences. Private plaintiffs may seek statutory damages of $500 per violation, and courts may increase damages for willful or knowing violations. In class action litigation, that math can become enormous very quickly. One call may be annoying. Ten thousand calls may become a boardroom emergency.
The Duke v. American Express Discovery Fight: What Happened?
The dispute centers on a putative TCPA class action in the District of Arizona. The plaintiff sought discovery related to phone numbers that American Express or vendors allegedly called using artificial or prerecorded voice technology, particularly where company records reflected wrong-party, wrong-number, or “never call” indicators.
The discovery fight did not focus only on one consumer’s experience. It focused on whether enough similar calls existed to support class certification. That distinction is crucial. In a proposed class action, the plaintiff must show that the case can properly proceed on behalf of a larger group. That means data about call volume, call patterns, wrong-number records, and common calling practices can become central evidence.
American Express resisted the requested discovery, arguing in part that the requested information was burdensome, costly, overbroad, private, and difficult to retrieve from its systems. According to the court materials, the company pointed to technical challenges involving large volumes of data, multiple databases, employee time, and significant estimated cost.
The court was not persuaded. It granted the plaintiff’s second motion to compel and ordered American Express to provide additional discovery. The court also extended the case schedule so the plaintiff would have time to analyze the data before class certification briefing.
Why the Court Focused on Call Logs
Call logs are the oxygen of TCPA litigation. Without them, a plaintiff may struggle to identify the size of the class, the number of calls, the type of technology used, and whether the alleged conduct was common across a group. With them, the case can move from “I received calls” to “Here is a pattern affecting many people.”
In this dispute, the requested records related to attempts by American Express or vendors to place prerecorded or artificial voice calls to numbers not identified as landlines, where records showed at least one wrong-party or “never call” notation. That kind of data can matter for several Rule 23 issues, including numerosity and commonality.
Numerosity asks whether the proposed class is large enough that individual lawsuits would be impractical. Commonality asks whether class members share common legal or factual questions. If call records show a consistent process, a repeated use of prerecorded voice technology, and a large universe of wrong-number calls, that data can become powerful evidence at the class certification stage.
The 3,133 Numbers Problem
One important detail in the discovery order involved the production of 3,133 phone numbers. American Express had produced data tied to those numbers, but the court found that the production did not fully match what the discovery order required.
The issue was not simply the number of phone numbers. It was the method used to identify them. The court noted that the production appeared to be limited in a way that excluded some calls that could still matter under the TCPA. In particular, the court addressed the idea that calls made before a wrong-number notation may still be relevant. That makes sense because TCPA liability does not necessarily depend on whether the caller subjectively knew at the time that it was calling the wrong person.
This is one of the most important lessons from the order. A company cannot always reduce TCPA discovery by saying, “We did not know it was the wrong person yet.” If the called party did not consent, and the call used regulated technology, the timing of the company’s internal notation may not save the day.
Why “We Cannot Easily Search That” Was Not Enough
American Express argued that producing the requested information would be highly burdensome. The court materials referenced a declaration estimating that compliance could require searching roughly 100 terabytes of data, take 16 weeks, require five employees, and cost about $100,000.
Those numbers sound dramatic, and in many business settings they would be. But in high-stakes TCPA class action discovery, courts often look beyond the sticker shock. The question is not simply whether discovery is difficult. The question is whether it is proportional to the needs of the case and whether the information is uniquely available to the defendant.
Here, the court found the data important to class certification. It also considered whether American Express had shown that the burden was truly undue. The result was not favorable to the company. The order suggests that complicated internal systems do not automatically protect a defendant from producing relevant discovery.
The Privacy Argument Also Fell Flat
Privacy is a serious issue in litigation, especially for a financial services company. Customer information, account details, payment histories, and identifying data deserve careful protection. However, courts often distinguish between sensitive account-level financial information and more limited discovery such as phone numbers, call counts, timestamps, and call-status data.
In this dispute, the court was not convinced that privacy concerns justified withholding the requested discovery. A protective order was already in place, and the plaintiff was not seeking full account details or broad financial records. The requested discovery was tied to phone numbers and call activity relevant to the TCPA claims.
That distinction matters for companies defending similar cases. A privacy objection may be stronger when a request seeks sensitive consumer financial data. It may be weaker when the request targets call records directly tied to whether a proposed class exists.
How Facebook v. Duguid Fits Into the Bigger TCPA Picture
The Supreme Court’s 2021 decision in Facebook, Inc. v. Duguid narrowed the definition of an automatic telephone dialing system under the TCPA. Many companies viewed that decision as a major defense-friendly development because it limited certain autodialer claims.
But Duguid did not eliminate TCPA risk. Claims involving artificial or prerecorded voice calls remain alive and dangerous. That is why the American Express discovery fight is so important. Even if a defendant has strong arguments about autodialer technology, prerecorded voice allegations can create a separate path for liability and discovery.
In other words, companies should not assume that one favorable Supreme Court interpretation makes TCPA compliance a sleepy back-office issue. If prerecorded messages, vendor dialers, wrong-number records, and consent gaps are involved, the litigation risk can still be very real.
Why the Case Matters for Financial Institutions
Financial institutions contact consumers for many reasons: fraud alerts, payment reminders, account servicing, collections, marketing, identity verification, and customer support. Many of those communications are useful, expected, and even welcomed. Nobody wants to miss a fraud alert because their bank decided to communicate only by carrier pigeon.
But useful communication still needs compliant infrastructure. The Duke discovery fight shows that large companies must be able to explain and document their outbound calling practices. That includes how numbers enter the system, how consent is captured, how revocation is processed, how wrong-number complaints are coded, and how vendors pass call records back to the company.
If those systems are fragmented, the company may face two problems at once. First, the compliance program may miss important warnings. Second, the legal team may struggle to produce clean discovery if litigation arises. In TCPA class actions, messy data can become almost as damaging as the calls themselves.
Vendor Management Is Now a Litigation Issue
Many large companies rely on third-party vendors to place calls, manage campaigns, service accounts, or handle collections. That does not automatically eliminate legal responsibility. In TCPA litigation, plaintiffs often look closely at whether calls were made by vendors acting on behalf of the defendant.
The American Express dispute highlights the importance of vendor-level data. If a vendor places prerecorded calls, records wrong-number complaints, flags reassigned numbers, or tracks “never call” instructions, the company may need access to that data later. A contract that says “vendor will comply with law” is helpful, but it is not enough if the actual call records are incomplete, inconsistent, or hard to retrieve.
Companies should think of vendor data as future courtroom evidence. If the vendor cannot produce reliable call logs, consent fields, campaign identifiers, and disposition codes, the company may be left arguing from memory while the plaintiff argues from gaps.
The Real Lesson: Discovery Readiness Is Compliance
For years, businesses treated TCPA compliance as a front-end issue: get consent, scrub lists, honor opt-outs, and avoid risky dialing technology. Those steps are still essential. But the Duke discovery fight adds another layer: companies must also be discovery-ready.
Discovery readiness means the company can reconstruct what happened without launching a digital archaeology expedition. It can identify calls by campaign, technology, vendor, number type, consent status, and complaint history. It can distinguish landlines from cell phones. It can track reassigned-number risk. It can show when a number was marked wrong, when calls stopped, and whether any calls slipped through afterward.
That kind of system is not just helpful for litigation. It is good business hygiene. It helps compliance teams spot problems earlier, reduces consumer frustration, improves vendor accountability, and gives defense counsel a stronger factual record if a lawsuit arrives.
Practical Examples: How a TCPA Discovery Fight Can Escalate
Imagine a bank calls a number to collect on an account. The number belonged to a customer two years ago, but it has since been reassigned. The new owner answers and says, “Wrong number.” If the bank keeps calling with a prerecorded message, the risk increases. If the bank’s vendor logs the complaint in one database but the dialing platform keeps using the number from another database, the risk increases again.
Now imagine that same issue happening across thousands of accounts. One consumer lawsuit becomes a proposed class action. The plaintiff asks for every phone number with a wrong-party notation that received prerecorded calls. The company responds, “That is hard to search.” The court asks, “But is it relevant?” The answer may be yes.
That is the danger zone. TCPA class actions often turn on whether plaintiffs can obtain the data needed to show a larger pattern. Once call logs are produced, the litigation may shift from theory to arithmetic.
What Businesses Should Do After the AmEx Discovery Ruling
1. Audit Wrong-Number Workflows
Companies should review how wrong-number complaints are captured, coded, escalated, and used to stop future calls. A “wrong party” note should not sit quietly in a customer service system while a separate dialing platform continues to call the number like nothing happened.
2. Connect Consent and Calling Data
Consent records should be connected to outbound call records. If the legal team cannot match a call to a consent source, campaign, account, or vendor, the company may struggle to defend itself later.
3. Test Vendor Data Access
Vendor contracts should require detailed call records and timely production of data. Businesses should test this before litigation, not after a motion to compel lands on counsel’s desk.
4. Preserve Call Logs Long Enough
Data retention policies should account for TCPA litigation timelines. Deleting logs too early may create major problems if the company later needs to prove compliance.
5. Treat Prerecorded Voice Calls as High Risk
After Duguid, some businesses became more relaxed about autodialer risk. But prerecorded voice calls remain a major TCPA danger. Any campaign using artificial or prerecorded voice technology deserves careful legal and compliance review.
Experience-Based Analysis: What TCPA Discovery Fights Teach in the Real World
In real-world TCPA litigation, discovery fights often reveal more than the complaint itself. A lawsuit may begin with one person saying they received unwanted calls, but the discovery process asks a much bigger question: does the company have a repeatable, measurable calling problem? That is where the pressure starts. Plaintiffs want call logs because call logs can turn a single story into a spreadsheet. Defendants resist broad discovery because a spreadsheet can become a class certification exhibit. Both sides understand the stakes.
One common experience in TCPA matters is that business teams and legal teams often speak different languages. The business team may say, “We stopped calling once the number was flagged.” The legal team then asks, “Which system shows that, and can we export it?” Suddenly, the answer becomes more complicated. The notation may live in a customer relationship platform, while call attempts live in a vendor dialer, while consent history lives in another database, while campaign logic sits in a marketing automation tool. Everyone thought the process was clear until someone had to prove it under oath.
Another practical lesson is that “burden” arguments work best when the company has a clean explanation supported by consistent testimony. Courts may listen when a request is truly massive, duplicative, or disconnected from the claims. But if a corporate witness suggests the data can be searched one way, and later declarations describe a much harder process, the inconsistency can weaken the defense. In discovery, credibility is a form of currency. Spend it carefully.
Companies also learn that wrong-number data is emotionally powerful. Consumers are not complaining about a technical footnote in a statute. They are saying, “I told you I am not that person, and you kept calling me.” Judges understand that experience. Even when the legal issues are complex, the human story is simple. Nobody wants to be chased by a robot voice for someone else’s bill, card account, or application. That simplicity can make wrong-number TCPA claims especially attractive to plaintiffs’ lawyers.
The best compliance programs treat every wrong-number report as a red alert, not a casual note. They stop calls quickly, sync suppression data across platforms, document the timeline, and verify that vendors received the update. Strong programs also run periodic tests: pick a sample of wrong-number complaints, trace what happened afterward, and confirm that no prerecorded calls continued. That kind of internal audit may feel tedious, but it is much cheaper than explaining missing data in federal court.
The broader experience is clear: TCPA discovery is not just a legal department headache. It is a systems test. It tests data governance, vendor oversight, consent architecture, complaint handling, and corporate memory. Companies that can tell a clear data story are better positioned to defend themselves. Companies that cannot may find that the discovery fight becomes the main event.
Conclusion: The Message Behind the AmEx Discovery Fight
The latest American Express TCPA discovery dispute is not merely a procedural skirmish. It is a warning to every high-volume caller. If your company uses prerecorded or artificial voice technology, if vendors place calls on your behalf, or if your systems track wrong-number complaints, you should assume that call data may become discoverable in a class action.
The court’s order reinforces a practical truth: complexity is not a shield. A large company cannot rely on scattered databases, technical burden, or partial production if the missing information is central to class certification. In TCPA litigation, the question is no longer only, “Did you have consent?” It is also, “Can you prove it, number by number, call by call?”
For American Express, the fight continues in the courtroom. For other businesses, the lesson is already available. Build cleaner calling systems. Respect wrong-number warnings. Preserve call records. Monitor vendors. And never underestimate the legal power of a phone log.
