A federal court in New Jersey recently refused to throw out a putative class action against Staples that alleges the company kept sending marketing texts after a customer replied "Stop." The October 26, 2026 ruling is a useful reminder for anyone thinking about TCPA proof of consent text messages: if you are challenged, your records are what you will have to work with. This post covers what the ruling did and did not decide, and which consent records high-volume senders should keep.
Key takeaways
- In Rubin v. Staples, Inc., the court rejected a motion to dismiss for lack of standing. It treated consent as an affirmative defense and a factual dispute for discovery, not a reason to end the case early.
- The ruling is not a finding that Staples' consent was invalid. The coverage we reviewed does not describe Staples' consent records at all.
- Federal rules let people revoke consent by any reasonable method, and replying "stop" counts automatically. Opt-out history is part of your consent story.
- Keeping organized records of where consent came from, when, what the person saw, and what happened afterward puts you in a better position if you are ever challenged.
- Whether any particular set of records is "sufficient" is a legal question. Ask counsel.
What happened in Rubin v. Staples
In Rubin v. Staples, Inc., 2026 WL 3205681 (D.N.J. Oct. 26, 2026), the plaintiff alleges Staples sent him numerous unwanted texts even though he repeatedly asked it to stop. The case is a putative class action, and these are allegations, not findings.
Staples moved to dismiss for lack of standing, arguing the plaintiff had consented to the texts. According to TCPAWorld's coverage (opens in a new tab), the court rejected that argument. It said that because Staples allegedly sent the texts, the plaintiff's consent, which he purports to have revoked, did not sever the causal link to his injuries. The court also described consent as an affirmative defense: even if consent ultimately shields Staples from liability, the plaintiff would not lose standing. Disputes over whether the "Stop" texts were sent can be explored in normal discovery.
The article's author, TCPA defense lawyer Eric J. Troutman, calls Staples' standing argument meritless and says consent is a merits issue, not a standing issue. That is his opinion, not the court's holding.
What the ruling does not say
The headline on the coverage (also published by The National Law Review (opens in a new tab)) is more dramatic than the decision. This was a standing ruling. It was not a decision that Staples' consent was invalid or poorly documented, and the reporting we reviewed does not say what consent records Staples relied on or whether the court looked at them. The alleged problem is what happened after consent: repeated "Stop" replies.
The takeaway is practical, not doctrinal. A consent defense is something you prove with evidence, usually later in a case rather than at the start. Senders who cannot produce clear records may find that harder.
What counts as consent under FCC rules
Under the FCC's rules, "prior express written consent" is defined, in the text of 47 CFR 64.1200(f)(9) (opens in a new tab), as a signed written agreement that:
- clearly authorizes the seller to deliver advertisements or telemarketing messages,
- identifies the phone number to be used, and
- includes a clear and conspicuous disclosure, including that signing is not a condition of purchase.
Electronic signatures count if they are valid under federal law or state contract law. Note that the definition is written around autodialed or prerecorded messages, and we reviewed it through a third-party copy of the regulation, so confirm the current text against the official eCFR.
Even this definition does not say which records a sender must keep, or how long. We found no FCC or court source that lists required consent record fields. Anything beyond the definition above is general practice, not a stated requirement.
Revocation is part of the record
Consent is not a one-time event. Under 47 CFR 64.1200(a)(10) (opens in a new tab), a person can revoke consent, including written consent, by any reasonable method that clearly expresses a desire to stop. Replying "stop," "quit," "end," "revoke," "opt out," "cancel," or "unsubscribe" is a reasonable method per se. Senders cannot designate an exclusive way to revoke, and requests must be honored within a reasonable time not exceeding ten business days.
A few related details from the rule text:
- A one-time confirmation text sent within five minutes of a revocation request is presumed to fall within the consumer's prior consent. A longer delay requires the sender to show it was reasonable.
- A revocation made by another means, such as a voicemail or email, creates a rebuttable presumption of revocation once the called party produces evidence of the request.
The "revoke-all" delay
The FCC's Consumer and Governmental Affairs Bureau extended a waiver of section 64.1200(a)(10) (opens in a new tab) until January 31, 2027. According to law-firm coverage (opens in a new tab), the delay is narrow: it covers only the "revoke-all" portion, under which one revocation would apply to all future calls and texts from the caller, including on unrelated topics. That coverage says other TCPA rules and prior FCC revocation guidance are unchanged. The waiver runs until January 31, 2027 unless it is extended or changed by the pending rulemaking.
Opt-out messages can be the evidence
A separate case shows how opt-out records can matter. In a Central District of California case (opens in a new tab) over alleged "opt-out evaders," the defendant attached a declaration showing the plaintiff replied "Don't text me anymore" instead of the invited keyword "STOP." The court denied dismissal because it could not take judicial notice of the plaintiff's actual opt-out message at the pleadings stage. Records of what a person actually sent, and what you did in response, can become central.
What this means for high-volume SMS senders
At high volume, you will not remember individual opt-ins. You will have your records, and only your records. Based on the rule text and the cases above, these are sensible categories to keep for each phone number. They reflect general operational practice, not a legal checklist:
- Source of consent. The form, keyword, checkbox, or channel where the person opted in, and the campaign or list it belongs to.
- Timestamp. The date and time of the opt-in. Consent dates can matter to a defense. The rule's limited reassigned-number safe harbor, for example, turns partly on the date prior express consent was obtained.
- Disclosure language. The exact wording the person saw when they agreed, saved as the version in use at that time, not just today's version.
- Number and signature details. The phone number provided and how agreement was captured, such as an electronic signature.
- Opt-out history. Every inbound opt-out message in full, when it arrived, when you processed it, and when you last sent anything to that number.
- Message logs. What you sent and when, so you can show the sequence of consent, messages, and opt-out.
Two cautions. First, the rules in this area have been in flux. The Eleventh Circuit vacated the FCC's "One-to-One Consent" rule in January 2025, one business day before it was to take effect, so do not assume that rule applies. Second, the litigation landscape varies by court. In July 2026, the Seventh Circuit held in Steidinger v. Blackstone Medical Services that marketing texts are not "telephone calls" under one TCPA private-right-of-action provision, according to a Barnes & Thornburg alert (opens in a new tab). The same alert cautions that the ruling does not give senders free rein. How that holding plays out elsewhere, and under other TCPA provisions or state laws, is an open question. Reporting suggests the New Jersey court in Rubin did not treat texts as outside the statute, but we have not read that opinion.
What to do now
- Audit your records. Pick a sample of recent opt-ins and see whether you can pull the source, timestamp, and disclosure wording for each within minutes.
- Version your consent language. Keep a dated archive of every opt-in form, keyword prompt, and disclosure you have used.
- Store opt-outs as evidence. Log the full text of each opt-out reply, not just a "suppressed" flag.
- Test your stop handling. Reply with "stop," "unsubscribe," and plain-language requests, and confirm each is honored well inside ten business days.
- Watch the January 31, 2027 date. The "revoke-all" waiver is currently set to end then unless it is extended or changed.
- Ask counsel what to keep and for how long. No source we reviewed sets a retention period.
Frequently asked questions
What is TCPA proof of consent for text messages?
It is the evidence a sender can produce to show a recipient agreed to receive texts. For marketing texts, the FCC's rule text describes written consent as a signed agreement, which can be electronic, that authorizes the messages, identifies the number, and includes a clear disclosure. What records a sender should keep to prove that is a question for counsel.
Does the Staples ruling mean consent records don't work?
No. The court ruled on standing, not on whether Staples' consent was valid, and it called consent an affirmative defense to be sorted out in discovery. The reporting does not say what records Staples had. The lesson is that consent is something you may need to prove with evidence, not that records are useless.
Can someone revoke consent by replying with something other than "STOP"?
Yes. The FCC rule says revocation can be made by any reasonable method that clearly expresses a desire to stop, and senders cannot designate an exclusive method. Replies like "stop," "quit," "cancel," and "unsubscribe" are reasonable per se. Plain-language requests, such as "don't text me anymore," are the kind of message that has shown up in litigation.
Keeping your program defensible
Consent records are only useful if they are captured automatically and consistently. Flowtext handles STOP/opt-out processing automatically (see Features) and builds in list scrubbing and TCPA compliance, with 10DLC registration. You can read more on our Compliance page.
This post is general information, not legal advice. Consult counsel about your own text messaging program and consent practices.
Tags
- TCPA
- SMS compliance
- consent management
- opt-in records
- opt-outs