A verification code text that a user asked for is one of the safest messages a business sends. The Supreme Court threw out a TCPA suit over Facebook’s login notification texts in 2021, holding that the system wasn’t an autodialer. The FCC has also said a one-time reply to a consumer’s own request doesn’t violate its rules. Risk starts when a code text carries marketing, reaches the wrong person, or arrives as an automated voice call. Each of those has a defense.
Does the TCPA cover one-time passcode texts at all?
47 U.S.C. section 227(b)(1)(A) bars calls to cell phones made “using any automatic telephone dialing system or an artificial or prerecorded voice” without prior express consent. The FCC’s 2015 order says text messages get “the same consumer protections under the TCPA as voice calls.” A passcode text is covered only if the sending platform is an autodialer, or if an artificial voice delivers the code.
Facebook, Inc. v. Duguid narrowed the autodialer definition, and the case was about security texts. Facebook sent login notification texts to Noah Duguid, who had never had a Facebook account. The Supreme Court held that “a necessary feature of an autodialer under §227(a)(1)(A) is the capacity to use a random or sequential number generator to either store or produce phone numbers to be called.” A system that texts numbers tied to user accounts doesn’t do that.
Most passcode platforms send codes to a number the user typed in, one message at a time. That design is far from the random or sequential dialing Duguid describes. A plaintiff suing over an OTP text usually has to plead facts showing the platform generated numbers, and most can’t.
Does a user who requests a code give consent to receive it?
The FCC’s 2015 answer, for the code itself, is yes. Its 2015 Declaratory Ruling and Order repeats the 1992 rule that “persons who knowingly release their phone numbers have in effect given their invitation or permission to be called at the number which they have given, absent instructions to the contrary.” A user who enters a number and taps “send code” has done exactly that.
The same 2015 order addressed one-time replies to consumer requests. The FCC found that “a one-time text sent in response to a consumer’s request for information does not violate the TCPA or the Commission’s rules” if it meets three conditions. The consumer must request it, the business must send it once and immediately, and the text must contain only the information requested, with no other marketing.
McLaughlin Chiropractic Associates v. McKesson Corp. changed how much weight those FCC statements carry. The Supreme Court held in 2025 that a district court “is not bound by the FCC’s interpretation of the TCPA” and must apply ordinary statutory interpretation while giving the agency appropriate respect. The consent reasoning still matters, but a court now decides it for itself.
The strongest OTP defense rarely depends on the FCC’s 2015 order anyway. Duguid supplies a statutory answer to the autodialer element, and the user’s own request supplies a factual answer to consent. A business with both doesn’t need to win an argument about agency deference.
What turns a verification text into a marketing text?
Adding an offer is the fastest way to lose the protection the FCC gave on-demand texts in 2015. The FCC’s third condition requires a reply with “no other marketing or advertising information.” A passcode text that also offers 20 percent off the next order is no longer a one-time informational reply.
47 C.F.R. section 64.1200 requires prior express written consent for autodialed or prerecorded telemarketing to a cell phone. A signup screen that collects a number for login security rarely has the written disclosures that consent requires. Marketing tacked onto a security text can therefore turn a low-risk message into a claim that needs the full consent record to defend.
Do Not Call exposure follows the same line. Section 227(a)(4) defines a “telephone solicitation” by its purpose of encouraging a purchase, and the Do Not Call rules reach telephone solicitations. A pure passcode isn’t one. The firm’s post on texts and the Seventh Circuit’s Steidinger decision covers a separate question: whether a text is a “call” under the Do Not Call private right of action at all.
What about codes sent to the wrong number or by voice?
Wrong numbers drive most real OTP claims, and Facebook, Inc. v. Duguid itself began when Facebook texted a man who never gave it his number. A user who mistypes a number, or a fraudster who enters someone else’s, can send codes to a person who never consented. Duguid’s autodialer holding still protects a system that doesn’t generate numbers.
Voice codes delivered by an automated call raise a different problem under section 227(b), and businesses often miss it. Many platforms let a user choose an automated call that reads the code aloud. That call uses an artificial voice, so section 227(b)(1)(A) applies without any autodialer showing, and Duguid offers no help. The called party’s consent becomes the whole defense.
Section 64.1200(a)(3) gives residential landlines a narrower rule. A noncommercial artificial voice call to a home line needs no consent if the caller makes three calls or fewer in 30 days. The caller must also honor opt-outs. A commercial call without an advertisement gets a similar exemption. The firm’s post on wrong-number TCPA claims covers reassigned numbers in more detail.
| Claim theory | Statute or rule | Exposure per violation | Defenses that answer it |
|---|---|---|---|
| Autodialed OTP text without consent | 47 U.S.C. 227(b)(1)(A) | $500, up to $1,500 if willful or knowing | No random or sequential number generator under Duguid, and the user’s own request |
| OTP text with marketing added | 47 C.F.R. 64.1200(a)(2) | $500, up to $1,500 if willful or knowing | No autodialer, or prior express written consent on record |
| Artificial voice code call | 47 U.S.C. 227(b)(1)(A) | $500, up to $1,500 if willful or knowing | Prior express consent from the called party |
| Do Not Call claim over a code text | 47 U.S.C. 227(c)(5) | Up to $500, up to $1,500 if willful or knowing | A pure code isn’t a telephone solicitation, and in some circuits a text isn’t a call |
What should a business preserve and do after an OTP text claim?
A demand letter or complaint over verification texts calls for these steps, in this order:
- Put a litigation hold on the platform’s send logs, request logs, IP and device data, and the consent records for each number involved.
- Pull any opt-out or STOP records and internal do-not-call entries for the number, with dates.
- Pull the Do Not Call Registry scrub records and version dates if any marketing went to the number.
- Collect the SMS vendor contract, the message templates in use on each date, and any voice-code audio or text-to-speech scripts.
- Talk to a lawyer before responding to a demand letter, contacting the claimant, or offering anything to settle.
Businesses comparing their options can see how California TCPA defense lawyers evaluate these claims before the first response.
Questions businesses ask about verification code texts
Can a business be sued over passcode texts triggered by bots?
A bot that enters random numbers can make a platform text people who never asked for a code, and 47 U.S.C. 227(b) still reaches those texts. Those recipients never consented, so the claim shifts to the autodialer element. Under Duguid, a system that sends one code to whatever number was typed in doesn’t generate numbers itself. Rate limits and fraud filters also help, because they show the business stopped the traffic once it appeared.
Do verification code texts need STOP language?
The on-demand ruling doesn’t make opt-out language a condition, and many carriers set their own rules for code messages. Honoring a STOP reply is still the safer course. A user who opts out and keeps getting codes has a better revocation argument, and a business that ignores revocations has a harder time showing good faith on willfulness.
Is a password reset text an advertisement under the TCPA?
A password reset text that only gives a link or a 6-digit code is informational. It doesn’t encourage a purchase, so it isn’t a telephone solicitation or telemarketing. The answer changes if the message adds a promotion, a product pitch, or a link to a sales page. Keep security messages and marketing messages in separate templates.
Does consent to receive codes also cover marketing texts?
Consent given for a login code covers that code, and 47 C.F.R. 64.1200(a)(2) sets a higher bar for marketing. Autodialed or prerecorded marketing texts to a cell phone need prior express written consent, and a login screen rarely collects it. A separate marketing opt-in with the required disclosures is the cleaner route, even if it costs some signups.
If your company has been sued over verification texts
If your company faces a demand or lawsuit over passcode or login texts, the send logs and the consent record for each number usually decide the case. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving verification code and login notification texts. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
47 U.S.C. section 227 (autodialer and artificial voice restrictions, telephone solicitation definition, private rights of action).
47 C.F.R. section 64.1200 (prior express written consent for telemarketing and the residential line exemptions).
Facebook, Inc. v. Duguid (2021) 592 U.S. 395 (autodialer must use a random or sequential number generator, in a case over login notification texts).
FCC Declaratory Ruling and Order, FCC 15-72 (2015) (consent by providing a number, and one-time on-demand texts).
McLaughlin Chiropractic Associates, Inc. v. McKesson Corp. (2025) 606 U.S. 146 (district courts not bound by FCC interpretations of the TCPA).
This post is general information about the Telephone Consumer Protection Act and related laws as of November 14, 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.