TCPA Class Action Filed Against FSB in Ninth Circuit

Some lawsuits arrive quietly. Others show up wearing tap shoes and a spotlight. The new TCPA class action filed against The Federal Savings Bank, or FSB, in the Ninth Circuit lands somewhere in the middle: serious enough to matter, specific enough to teach, and familiar enough to make every marketing, mortgage, and compliance team sit up a little straighter.

At the center of the case is a simple allegation with expensive potential: unwanted text messages. That is the kind of claim that sounds small until someone multiplies it across a class, adds statutory damages, and asks a federal judge to let the whole thing move forward together. Suddenly, what looked like a few annoying messages starts behaving like a line item from a legal horror movie.

This article explains what the filing against FSB appears to involve, why the Ninth Circuit matters, how the Telephone Consumer Protection Act works in the real world, and what this lawsuit says about the modern risk map for banks, lenders, lead generators, and any business that still thinks “we got the number from somewhere” is a compliance strategy.

What Was Filed Against FSB in the Ninth Circuit?

A new federal case, Almond v. The Federal Savings Bank, was filed in the U.S. District Court for the Eastern District of California, which sits within the Ninth Circuit. Public docket information identifies the suit as a Telephone Consumer Protection Act case brought by plaintiff James Almond against The Federal Savings Bank, with a jury demand. In plain English, that means this is not just a customer-service complaint with a legal accent. It is a federal consumer-protection lawsuit built around the rules governing calls and texts.

Public reporting on the complaint says the plaintiff alleges FSB sent SMS messages without consent and kept going despite requests that the messages stop. One publicly described complaint excerpt references a text identifying the sender as someone “over at The Federal Savings Bank,” which gives the dispute a very modern flavor: a consumer, a phone, a financial-services pitch, and a paper trail living in message history rather than a voicemail box from 2008.

Just as important, the case is still early. A filing is an allegation, not a finding. No public merits ruling has established liability. That distinction matters. Good legal writing should never treat a complaint like a final exam already graded in red ink. Still, even at the pleading stage, the filing matters because it highlights the kind of TCPA theory that continues to attract class-action attention: alleged marketing texts sent without valid consent, plus alleged failures to honor opt-out requests.

Why This Case Matters More Than One Inbox Full of Texts

The FSB lawsuit is not landing in a vacuum. In another federal case from 2025, an Illinois court certified a nationwide TCPA do-not-call class and a transfer subclass against The Federal Savings Bank and related defendants in litigation over telemarketing calls. That earlier ruling did not decide every merits issue, but it showed something important: plaintiffs’ lawyers and courts are willing to examine bank marketing systems, vendor relationships, and consent evidence at scale when the underlying outreach looks standardized.

That broader context is what gives the new Ninth Circuit filing extra heat. When one institution is already tied to a large TCPA fight involving telemarketing practices, a fresh lawsuit over text messages does not read like an isolated clerical mishap. It reads like a reminder that communication compliance is not a side quest. It is part of the main plot.

And the plot can get expensive fast. The TCPA famously allows private actions with statutory damages that can start at $500 per violation and rise to $1,500 per violation for willful or knowing misconduct. Multiply that by repeated contacts or a certified class, and even a seemingly ordinary messaging campaign can become a boardroom problem before the coffee cools.

TCPA Basics, Explained Without the Usual Legal Fog Machine

Texts Count as Calls

In the Ninth Circuit, this point is not new: text messages can qualify as “calls” for TCPA purposes. That matters because businesses sometimes talk about texting like it is the law’s quirky little cousin, somehow different from calling. Courts have not been especially charmed by that idea. If a marketing text hits a consumer’s phone, TCPA analysis is often in the room already, pulling up a chair.

Consent Is Specific, Not Magical

Businesses love the word “consent.” Courts love details. Those are not always the same thing. Under Ninth Circuit case law, consent depends heavily on context. If a consumer gives a number in connection with one transaction or request, that does not automatically create permission for every future call or text about every imaginable product under the sun. Consent has scope. Scope has boundaries. Boundaries create lawsuits.

That is why so many TCPA disputes revolve around how the number was obtained, what the consumer was told at the time, whether the disclosure named the actual seller or texter, whether the message matched the reason the number was provided, and whether the records are clean enough to prove all that months or years later.

Revocation Is Where the Fight Gets Personal

Even where initial consent arguably existed, the next question is often whether the consumer revoked it. The Ninth Circuit has recognized that consumers can revoke prior express consent, and the FCC has strengthened the consumer side of that equation by clarifying that revocation may be made in any reasonable manner and must be honored within a reasonable time, not to exceed 10 business days. In normal human language: when someone says stop, smart companies should stop acting surprised.

That is one reason allegations about ignored stop requests are so important. A case framed around post-revocation messages can be more dangerous than a case built only on a messy consent form, because jurors and judges alike tend to understand the phrase “please stop texting me” without needing a telecommunications glossary.

Do-Not-Call Rules Still Pack a Punch

The TCPA is not just about autodialers. Its do-not-call framework remains a major source of exposure, especially for telemarketing campaigns. The regulatory landscape has also evolved to make clear that National Do Not Call protections apply to text messages. On top of that, FTC guidance continues to emphasize company-specific do-not-call requests, meaning a consumer can tell a particular business not to call even if other exceptions might otherwise exist. Translation: “but they inquired once” is not a forever pass.

The Ninth Circuit Framework FSB Is Walking Into

The Ninth Circuit has built a meaningful body of TCPA law, and that matters because forum shapes leverage. Several decisions help explain why a text-message case against a bank can become more than a nuisance filing.

First, Satterfield v. Simon & Schuster established long ago that text messages count as calls under the TCPA. That alone keeps texting campaigns from ducking behind semantic tricks. Second, Van Patten v. Vertical Fitness Group emphasized that prior express consent depends on the transactional context and that revocation must clearly express a desire not to be contacted. Third, Fober v. Management and Technology Consultants reinforced that consent analysis turns on the actual scope of what the consumer agreed to, not on corporate optimism.

Then there is Moskowitz v. American Savings Bank, a useful reminder that not all texts are treated the same way. There, the Ninth Circuit held that messages sent by the plaintiff’s phone to a bank’s short code supplied consent for responsive texts. That case is important because it shows that courts will sometimes credit genuine consumer-initiated interaction. But it also highlights the flip side: when the consumer did not initiate the exchange, or allegedly revoked permission, the bank’s position gets shakier.

Another major point is agency and vendor liability. In Henderson v. United Student Aid Funds, the Ninth Circuit held that a reasonable jury could find vicarious liability for TCPA violations committed by debt collectors hired through intermediaries. For banks and lenders, that is the part that should make every vendor-management slide deck sweat a little. You do not always escape TCPA risk by outsourcing the click-happy part.

And N.L. v. Credit One Bank showed that courts in the circuit can take a practical view of harm and consent when the wrong number gets called repeatedly. The intended-recipient defense is not a magic eraser. If the wrong person gets the messages or calls, that can still produce liability.

Why Financial Institutions Keep Seeing TCPA Trouble

Banks and mortgage lenders live on phone numbers. They collect them through applications, rate inquiries, lead forms, website funnels, transferred calls, customer-service interactions, and partner channels. That creates opportunity, but it also creates a recordkeeping headache with a legal bill attached.

Here is the recurring pattern. A consumer visits a website, checks a box, enters a number, or clicks something while trying to compare offers. Weeks later, a different company, or a company working through a vendor, starts calling or texting. Somewhere in the stack, the business believes it has consent. Somewhere else, the consumer insists they never agreed to hear from that sender, on that topic, in that volume, or after saying stop. By the time lawyers arrive, everyone is holding screenshots and speaking in italics.

The FCC’s recent moves make this environment even tougher for sloppy lead-generation practices. The agency closed the so-called lead generator loophole by making clear that telemarketing robocalls and robotexts requiring prior express written consent cannot rely on one broad consent covering a parade of sellers. Each caller or texter generally needs the appropriate consent for itself. That is a direct warning to businesses that built marketing systems on vague disclosures and crowded comparison-shopping pages.

So why does this matter for the FSB case? Because the allegations described publicly fit a pattern courts and regulators already know well: consumer contact through texts, disputed consent, alleged failures to honor stop requests, and a lender sitting close enough to the communications stream that agency and compliance questions immediately follow.

What the Parties Are Likely to Fight About

If this case develops in a typical TCPA direction, expect the early battles to center on a few familiar questions.

Was there valid consent? FSB will likely want to show the plaintiff provided a phone number in a way that authorized the texts, or that the messages were tied to a prior inquiry or business interaction. The plaintiff will likely argue the opposite: no meaningful consent, no valid written permission if required, or consent too narrow to cover the messages actually sent.

Were the texts telemarketing? Content matters. A message pitching mortgage products, refinancing opportunities, or related services is more likely to trigger telemarketing analysis than a truly informational text. Courts often care less about the label a company assigns and more about the commercial reality of the message.

Was consent revoked? If the plaintiff can prove stop requests and continued texts afterward, that can become the emotional core of the case. TCPA disputes often become more concrete and more sympathetic once the timeline reads: message, stop request, more messages, lawsuit.

Who sent the messages, really? If a third party, platform, or marketing partner was involved, vicarious liability becomes central. Companies sometimes discover that “not us” is weaker than it sounds when the messages were allegedly sent on their behalf, with their branding, or in pursuit of their products.

Can this become a class case? Class certification is where the temperature changes. Plaintiffs will try to show common proof about campaign design, message templates, consent records, and vendor systems. Defendants will try to show individualized issues, especially around consent and revocation. That tug-of-war often determines whether a TCPA case stays annoying or becomes existential.

Post-2025: The Supreme Court Just Made TCPA Litigation Even More Interesting

As if the statute needed more personality, the Supreme Court added a fresh wrinkle in 2025. In McLaughlin Chiropractic Associates v. McKesson, the Court held that district courts are not bound by the FCC’s legal interpretations of the TCPA in private enforcement suits under the Hobbs Act. That does not erase FCC guidance, but it does mean district courts can interpret the statute independently while giving the agency’s view appropriate respect.

Why does that matter here? Because it introduces a new layer of uncertainty into already difficult cases. Plaintiffs and defendants alike now have more room to argue about the meaning of statutory terms and the weight of prior FCC rulings. In one sense, that may benefit defendants challenging aggressive regulatory interpretations. In another, it removes the comfort of a stable playbook. For everyone involved, TCPA litigation now comes with an extra side of unpredictability.

That uncertainty sits alongside the Supreme Court’s earlier decision in Facebook v. Duguid, which narrowed the definition of an automatic telephone dialing system. After Duguid, plaintiffs have often leaned harder on do-not-call claims, prerecorded-voice claims, consent disputes, and revocation theories instead of assuming every automated text platform automatically qualifies as an ATDS. The result is not the death of TCPA litigation. It is more like a strategic relocation.

Real-World Experiences Around Cases Like This

If you want to understand why a TCPA class action filed against FSB in the Ninth Circuit feels important, do not just read the statute. Think about the lived experience on both sides of the phone.

For consumers, the story is often boring before it becomes infuriating. A person gets a text about a mortgage rate, a refi offer, or a “quick question” from someone sounding helpful. They ignore it. Another one comes. Then another. At some point, the person replies with a variation of the most universally understood phrase in mobile history: stop. If the texts keep coming, the experience changes from minor annoyance to a weird, everyday form of trespass. The phone stops feeling like a tool and starts feeling like a doorbell connected to a marketer’s treadmill.

For customer-service teams inside financial institutions, the experience is different but equally messy. The front-line employee answering complaints usually did not design the campaign, pick the vendor, approve the consent language, or decide how quickly opt-outs would process. But they are the one hearing from irritated consumers who insist they never signed up, do not know why the bank has their number, and definitely do not want to hear the phrase “we appreciate your interest” one more time before lunch. In many organizations, the complaint reaches compliance only after the customer has already lost patience and started taking screenshots.

For compliance officers and in-house lawyers, these cases often feel less like a single lawsuit and more like a forced audit with teeth. They have to reconstruct how the number was captured, where the lead came from, what the disclosure said at the exact moment of collection, whether the seller was specifically identified, whether the campaign content was telemarketing, how opt-outs were logged, whether any vendor altered the workflow, and whether the message platform suppressed opted-out numbers fast enough. It is not glamorous work. It is digital archaeology with sanctions risk.

Then there are the vendors and lead generators, the eternal supporting cast in modern TCPA drama. Their systems may be fast, scalable, and excellent at generating dashboards with cheerful arrows pointing up. What they are not always excellent at is preserving clean evidence that consent was valid, specific, and traceable to the exact outreach at issue. In litigation, “the consumer came from a partner source” is not proof. It is the beginning of a document request.

And finally, there is the management perspective. Executives often first hear about a TCPA problem through a number that does not seem real: possible exposure per text, per call, per class member. That is when the problem stops sounding like customer irritation and starts sounding like risk management. One campaign, one weak disclosure, one sloppy transfer process, or one ignored stop request can suddenly create a file that pulls in marketing, legal, operations, vendor management, IT, and public relations all at once.

That is the real-world significance of a case like this. It is not just about whether one plaintiff got a few texts. It is about whether the institution behind the texts can prove a lawful communication system from top to bottom, with receipts.

Bottom Line

The TCPA class action filed against FSB in the Ninth Circuit matters because it sits at the intersection of three trends that are defining modern communications litigation: aggressive scrutiny of text-based marketing, growing skepticism of vague consent practices, and rising willingness to test class theories against banks and their marketing ecosystems.

For readers following the case as legal news, the key point is straightforward: the claims are still allegations, and the court has not decided liability. For businesses, the lesson is less comforting. Consent must be specific. Revocations must be honored. Vendor conduct is not magically someone else’s problem. And in the post-McLaughlin era, the TCPA remains one of those statutes that can look settled on Monday and suddenly argumentative by Thursday.

In other words, if your marketing texts are clean, documented, limited, and respectful of opt-outs, wonderful. Keep going. If not, the Ninth Circuit may be serving the industry a reminder with very expensive punctuation.

SEO Tags