Push Notifications, Social DMs, and In-App Chat: Where the TCPA Stops
App push notifications and social-media direct messages usually sit outside the Telephone Consumer Protection Act. Its consent rule for automated calls covers calls “to any telephone number assigned to a paging service, cellular telephone service,” under 47 U.S.C. § 227(b)(1)(A)(iii). An app alert lands in an installed app, not on a number. Exposure comes back when a message falls back to SMS, so a company that keeps app messages inside the app starts with strong defenses.
Is a push notification a “call” under the TCPA?
A push notification falls outside § 227(b)(1)(A)(iii) on the statute’s words, because that rule reaches calls to a telephone number and a push notification never uses one.
Texts came under the TCPA because they land on a cell number. In Campbell-Ewald Co. v. Gomez, the Supreme Court described a text message to a cellular telephone as a call under § 227(b)(1)(A)(iii), writing “A text message to a cellular telephone, it is undisputed” before reaching that conclusion. The FCC took the same view in its 2015 omnibus order: “Glide raises the issue of whether SMS text messages are subject to the same consumer protections under the TCPA as voice calls. We reiterate that they are.”
A push notification moves from the app’s server through the phone’s operating system to the app the customer installed. Nobody dials a number. The customer can switch alerts off in the phone’s settings or delete the app, and the carrier’s text network plays no part.
Congress drew this same line in § 227(e)(8)(C), the caller-ID provisions. They define a text message as one “transmitted to or from a device that is identified as the receiving or transmitting device by means of a 10-digit telephone number or N11 service code,” and they exclude “a message sent over an IP-enabled messaging service to another user of the same messaging service, except a message described in clause (ii).” That definition governs only subsection (e). It’s still the clearest statement of how Congress separates carrier texts from app-to-app messages, and a defense brief should use it.
Nunes v. Twitter, Inc., 194 F. Supp. 3d 959 (N.D. Cal. 2016), shows a federal judge in San Francisco drawing the same distinction. According to the opinion, tweets were delivered as texts to recycled cell numbers. The court wrote that “it’s unclear why the desire to send alerts by text message (rather than email, or push notification through an app) should prevail over the TCPA’s goal of protecting people with recycled numbers from receiving unwanted texts sent by companies using autodialers.” The decision came before the Supreme Court narrowed the autodialer definition, but its practical point holds. The judge saw the push notification as the alternative to a text, not as another kind of text.
Do the Do Not Call rules reach social-media DMs or in-app chat?
Do Not Call claims rarely reach DMs or in-app chat, because 47 C.F.R. § 64.1200(c)(2) protects registered telephone numbers and the private claim requires telephone calls.
The National Do Not Call Registry is the federal list where people enter their phone numbers to stop sales calls. The FCC’s rule bars telephone solicitations to a subscriber “who has registered his or her telephone number on the national do-not-call registry,” and paragraph (e) extends it to “telephone solicitations or telemarketing calls or text messages to wireless telephone numbers,” under § 64.1200. The private claim belongs to a person who received “more than one telephone call within any 12-month period by or on behalf of the same entity,” per § 227(c)(5). A DM sent to a username doesn’t touch a registered number.
Section 227(a)(4) has one word plaintiffs will press. It defines a telephone solicitation as “the initiation of a telephone call or message” made to encourage a purchase, rental, or investment, per the statute. Expect a plaintiff to argue that “or message” covers app messages. The better reading keeps that word inside the telephone setting of the whole subsection, and the private claim in § 227(c)(5) still says “telephone call.”
In-app chat is the easiest case, since the customer opens the window and types first. The risk shows up when an agent asks for a phone number and then texts or calls the customer, because that’s a new channel and the consent question starts over from the beginning. The post on how far a single consent stretches covers that problem.
When does an app message turn back into a TCPA text?
An app message comes back under § 227(b)(1)(A)(iii) when it reaches the customer as an SMS or MMS message, or travels over a channel that uses the phone number as the address.
SMS fallback is the first trap, and Campbell-Ewald v. Gomez applies to it in full. Many notification vendors offer a setting that sends a text when a push notification fails or when the customer has notifications turned off. That fallback message is a text to a cell number. Fallback settings are the easiest place for an app-first company to pick up TCPA exposure without knowing it, because marketing teams rarely read the vendor’s delivery defaults.
The Commission’s 2015 order also reached email-to-text gateways. In FCC 15-72, the FCC found that messages sent as email to a carrier’s gateway and converted into texts on the phone need the recipient’s consent. That ruling’s autodialer reasoning came before the Supreme Court’s 2021 decision, but the message still arrives as a text on a cell number.
Phone-number chat apps and RCS business messages sit closer to the line than push alerts do. Some messaging apps use the phone number as the account ID, and RCS messages appear in the phone’s built-in texting app. Neither fits cleanly on one side. A company should handle consent for both as if they were texts until a court says otherwise.
Pro sports teams that sell tickets through an app show how the split plays out. The app can push a seat upgrade offer with little TCPA risk, but the follow-up call or text from a sales rep is a different matter, and the rules for ticket sales calls by sports teams and venues apply to that part.
Facebook, Inc. v. Duguid keeps the autodialer claim narrow even for real texts. An autodialer, under the statute, is equipment that generates phone numbers randomly or sequentially. In that case, about login-alert texts, the Supreme Court held: “That definition excludes equipment like Facebook’s login notification system, which does not use such technology.” The post on what still qualifies as an autodialer after Duguid walks through that defense.
McLaughlin Chiropractic Associates v. McKesson Corp., decided in June 2025, also lowered the weight of FCC readings in court. The Supreme Court held that “District courts are not bound by the agency’s interpretation” and must read the statute for themselves.
Do state texting laws go further than the TCPA?
Some state statutes, including Washington’s RCW 19.190.010, use broader words, so the line between app messages and texts is less certain at the state level.
Florida’s statute defines a telephonic sales call as “a telephone call, text message, or voicemail transmission to a consumer” in Fla. Stat. § 501.059(1)(j). That list names texts, not app alerts, and the details of Florida’s mini-TCPA rules for marketing texts matter for any company messaging Florida numbers.
RCW 19.190.010 uses looser wording. It defines an electronic text message as “a text message sent to a cellular telephone or pager equipped with short message service or any similar capability.” A plaintiff would press “any similar capability” against app messages, so a Washington campaign isn’t safe just because it runs through an app.
Exposure by channel
| Channel | TCPA provision a plaintiff would cite | Exposure per message | Defenses that answer it |
|---|---|---|---|
| Push notification to an installed app | None on the statute’s words | Low under the TCPA | No telephone number, and the customer controls alerts in device settings |
| Social-media DM or in-app chat | None unless sent to a phone number | Low under the TCPA | No telephone number, and the customer started the chat |
| SMS fallback or email-to-text | 47 U.S.C. § 227(b)(1)(A)(iii), (c)(5); 47 C.F.R. § 64.1200(c), (e) | Up to $500, or up to $1,500 if willful or knowing | Consent, Duguid, established business relationship |
| Phone-number chat apps and RCS | Unsettled; plaintiffs would cite § 227(b)(1)(A)(iii) | Plan as if it were a text | App-to-app definition in § 227(e)(8)(C), plus the text defenses |
If a demand letter claims your app messages were texts
- Put a litigation hold on push logs, SMS logs, and the delivery records that show which channel carried each message to the number in question, along with the consent record for that number.
- Pull the opt-out history for the number, including any STOP replies and the dates the number was suppressed.
- Pull the Do Not Call Registry scrub records and the version dates used for any text or call campaigns that reached the number.
- Collect the notification and texting vendor contracts, the fallback settings in effect on each send date, and the message templates.
- Talk to a lawyer before replying to the letter, messaging the claimant, or offering a credit to close it out.
Vendor delivery records don’t last forever, and the cost of losing call and text logs once a claim arrives can exceed the claim itself. The firm’s California TCPA defense lawyers page covers the defense of text and call claims in state and federal court.
Questions businesses ask about app and social messages
Do we need TCPA consent before sending push notifications?
Push notifications don’t need TCPA consent under § 227(b)(1)(A)(iii), because they aren’t sent to a telephone number. The phone’s operating system usually asks the customer to allow notifications, and the customer can turn them off at any time. App store rules and privacy laws still apply. The TCPA question comes back only if the vendor converts an undelivered push into a text.
Can a customer bring a TCPA claim over a social-media DM?
A DM sent to a username doesn’t reach a telephone number, which is what both § 227(b) and the Do Not Call rules protect. A claim built on DMs alone faces that problem from the first page. The picture changes if the business moved the conversation to texts or calls after the DM, so the follow-up messages are where to look.
Does turning on SMS fallback change our risk?
SMS fallback changes the risk a lot, because a fallback message is an ordinary text to a cell number under 47 C.F.R. § 64.1200. It carries the same consent and Do Not Call questions as any marketing text. Companies that want fallback should limit it to transactional messages or to numbers with documented consent for marketing texts, and keep records showing which channel delivered each message.
Are messages on phone-number chat apps texts under the TCPA?
Messages on phone-number chat apps are an open question under § 227(b)(1)(A)(iii). These apps use the phone number to find the account, but the message travels over the internet between users of the same app. The caller-ID definition in § 227(e)(8)(C) excludes that kind of message, though only for the caller-ID rules. The cautious course is to collect the same consent you’d collect for texts.
When a messaging claim lands on your desk
If your company is accused of texting customers who signed up only for app alerts, the delivery-channel records usually decide the first round. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving marketing texts and app-to-SMS fallback messages. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200. The FCC’s 2015 order is FCC 15-72, released July 10, 2015. The state statutes are Fla. Stat. § 501.059 and RCW 19.190.010.
The court decisions are Campbell-Ewald Co. v. Gomez, 577 U.S. 153 (2016); Facebook, Inc. v. Duguid, 592 U.S. 395 (2021); McLaughlin Chiropractic Associates v. McKesson Corp., 606 U.S. 146 (2025); and Nunes v. Twitter, Inc., 194 F. Supp. 3d 959 (N.D. Cal. 2016).
This post is general information about the Telephone Consumer Protection Act and related laws as of February 6, 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.