Peer-to-peer texting platforms exist for one reason. A person clicks send on each message, so the platform isn’t an autodialer, and the TCPA’s consent rule for autodialed texts doesn’t apply. A 2020 FCC ruling accepted that logic, and the Supreme Court’s 2021 autodialer decision made it stronger. But it answers only one kind of claim. A company that treats P2P texting as a TCPA exemption still has Do Not Call and state-law exposure on every message.
What does a peer-to-peer texting platform do differently?
A person sends each message. In the 2020 ruling on the P2P Alliance petition, DA 20-670, the FCC’s Consumer and Governmental Affairs Bureau recounted the petitioner’s description of these platforms as ones that “enable two-way text communication” and require a person to send each message manually, one at a time, with discretion over its content.
That design answers the TCPA’s autodialer provision. Under 47 U.S.C. § 227(a)(1), an automatic telephone dialing system is equipment with the capacity “to store or produce telephone numbers to be called, using a random or sequential number generator” and “to dial such numbers.” Campaign volume doesn’t change the analysis. The Bureau said “the fact that a calling platform or other equipment is used to make calls or send texts to a large volume of telephone numbers is not probative of whether that equipment constitutes an autodialer under the TCPA.”
What did the FCC actually rule?
A conditional answer. The Bureau held that “if a calling platform is not capable of originating a call or sending a text without a person actively and affirmatively manually dialing each one, that platform is not an autodialer and calls or texts made using it are not subject to the TCPA’s restrictions on calls and texts to wireless phones.”
It didn’t bless any product. The ruling says “We do not rule on whether any particular P2P text platform is an autodialer because the record lacks a sufficient factual basis for us to confirm (or for commenters to assess) whether any particular P2P text platform actually works as claimed in the P2P Alliance Petition.” The protection belongs to platforms that really work the way the petition described, which means the defense depends on proof of how your platform worked when your messages went out.
Two more limits matter. This is a Bureau-level declaratory ruling, not a rule adopted by the full Commission. And after McLaughlin Chiropractic Associates v. McKesson Corp. (2025), district courts in private suits decide what the TCPA means for themselves, so a court will weigh the ruling’s reasoning instead of deferring to it.
Did Facebook v. Duguid make the P2P argument stronger?
Yes. In Facebook, Inc. v. Duguid, 592 U.S. 395 (2021), the Supreme Court held that to qualify as an autodialer, a device “must have the capacity either to store a telephone number using a random or sequential generator or to produce a telephone number using a random or sequential number generator.” Most texting platforms, P2P or not, send to lists of numbers customers provided. They don’t generate numbers.
So after Duguid, the P2P design becomes a second line of defense. A company can argue both that its platform lacks a random or sequential number generator and that a human sent each message. Plaintiffs’ lawyers have shifted accordingly, toward Do Not Call and state-law theories that don’t depend on the equipment at all. The earlier post on autodialer defenses after Duguid covers the equipment argument in detail.
Which claims does P2P texting not answer?
Every claim that doesn’t depend on an autodialer. That’s the part companies miss, and it’s where the exposure now sits.
The Do Not Call rules apply to telephone solicitations regardless of how they’re dialed. The national Registry rule in 47 C.F.R. § 64.1200(c)(2) bars any “telephone solicitation” to a registered residential subscriber, and the FCC applies the Do Not Call rules to “telephone solicitations or telemarketing calls or text messages to wireless telephone numbers,” under § 64.1200(e). A volunteer clicking send on a sales text to a registered number is still sending a telephone solicitation.
Quiet hours work the same way. Section 64.1200(c)(1) bars solicitations “before the hour of 8 a.m. or after 9 p.m. (local time at the called party’s location).” A P2P team in one time zone, working through a list after dinner, can hit that line without anyone noticing.
The internal do-not-call list applies too. Under § 64.1200(d), a company making calls for telemarketing purposes needs a written policy, trained personnel, and a working suppression list. A P2P platform with many senders and shared inboxes is exactly the setting where a reply like “please stop” gets read by one person and never reaches the list.
State laws are the last piece. Several state statutes define regulated dialing equipment more broadly than the federal statute does, and some don’t turn on equipment at all. The earlier post on state mini-TCPA laws and texting covers which states to check.
| Claim | Does the P2P design help? | What actually answers it |
|---|---|---|
| Autodialed text to a cell phone without consent, § 227(b) | Yes, if a person sends each message | Platform documentation and the Duguid argument |
| National Do Not Call Registry, § 227(c)(5) | No | Registry scrub, established business relationship, written procedures |
| Internal do-not-call list | No | Opt-out capture across every sender and inbox |
| Quiet hours under § 64.1200(c)(1) | No | Send-time controls tied to the recipient’s location |
| State statutes with broader equipment definitions | Sometimes | The specific state’s text and the platform’s design |
Damages under either federal provision run up to $500 per violation, and a court may increase that to up to three times the amount if it finds the violation was willful or knowing. Those numbers apply to a Do Not Call claim even when the autodialer claim fails.
What records prove a platform is really peer-to-peer?
Evidence of how the platform worked on the dates in question, not a vendor’s marketing page. The FCC’s ruling turned on whether a platform “lacks the capacity to transmit more than one message without a human manually dialing each recipient’s number.” A plaintiff will look for any feature that sends without a click: scheduled sends, auto-replies, drip sequences, or a bulk-send mode a manager can switch on.
That’s why the vendor contract and the platform’s configuration history matter as much as the messages themselves. A company should be able to show which features were enabled, who sent each message, and when. Session logs that tie each send to a named user account are the best evidence there is. They’re also the evidence most often lost when a company changes vendors or closes a campaign.
If a demand letter arrives over P2P texts, the steps follow the claims, not the platform:
- Put a litigation hold on the platform’s send logs, the user and session logs showing who sent each message, the consent records, and the configuration history for the account.
- Export every opt-out and stop reply, from every sender’s inbox, with dates and times.
- Pull the Registry scrub records for the campaign and the date of the Registry data used.
- Gather the vendor contract, the platform’s technical documentation, and the message scripts.
- Have a lawyer review the file before responding to the demand, texting the claimant, or offering money.
Businesses using P2P platforms for sales outreach should line up TCPA defense lawyers before the campaign, because the evidence that wins the autodialer argument is created during the campaign, not after the lawsuit.
Questions about peer-to-peer texting
Do we still need consent to send P2P marketing texts?
Not for the federal autodialer rule, if the platform in fact requires a person to send each message. Consent still matters for state laws with broader definitions, and it matters for Do Not Call claims, where prior express invitation or permission is one way a call stops being a telephone solicitation. Collecting written consent is the safer course for marketing texts on any platform.
Does using templates make a P2P platform an autodialer?
The FCC’s description of P2P platforms assumes senders can work from prepared scripts, so a template alone shouldn’t change the analysis. The question is dialing and sending, not drafting. A feature that sends a template to many numbers with one click is a different matter, and that’s the kind of feature plaintiffs ask about in discovery.
Are political and nonprofit P2P texts treated differently?
Under the federal Do Not Call rules, texts from tax-exempt nonprofits and many political messages aren’t telephone solicitations. Commercial texts are. The P2P Alliance’s members included nonprofits and political groups, and businesses copying their playbook should remember that the Do Not Call rules treat a sales message differently.
Can a company be liable for texts its volunteers or reps send through P2P?
Yes, if the texts were sent on its behalf. The Do Not Call private right of action covers calls made “by or on behalf of the same entity.” A brand ambassador or independent rep using a company-provided P2P account will usually be treated as sending for the company.
Defending claims over P2P text campaigns
If your company is accused of sending marketing texts through a peer-to-peer platform, the platform’s send logs and the opt-out records across every sender usually decide which claims survive. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving texts sent through manual texting platforms. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act, 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200, as published in the eCFR on July 1, 2026. The FCC Consumer and Governmental Affairs Bureau’s ruling is the P2P Alliance Declaratory Ruling, DA 20-670 (June 25, 2020).
The court decision is Facebook, Inc. v. Duguid, 592 U.S. 395 (2021).
This post is general information about the Telephone Consumer Protection Act and related laws as of July 4, 2026. 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.