Is Missed-Call Text-Back Legal in 2026? What the "Texts Aren't Calls" Rulings Change (and What They Don't)

Short answer: A missed-call text-back is legal in most cases when it's a fast, purely informational reply to someone who just called you, it names your business, and it honors STOP. The wave of 2026 rulings saying "texts aren't calls" only kills one kind of lawsuit, the federal do-not-call claim, and mostly outside California. It doesn't touch the TCPA's autodialer and artificial-voice rules, Florida's own telemarketing law, or the carrier registration that decides whether your text arrives at all. Keep the first text boring, and put the promo somewhere else.

At Wrk Less, missed-call capture is one of the systems we build most, and the text-back is the piece owners ask about most. Here's what changed this fall and how we wire it so it holds up.

What did the "texts aren't calls" rulings actually decide?

The TCPA's do-not-call private right of action, 47 U.S.C. § 227(c)(5), lets someone sue if they "received more than one telephone call within any 12-month period" from the same entity in violation of the do-not-call rules. The fight is over whether a text is a "telephone call."

On July 14, 2026, the Seventh Circuit said no in Steidinger v. Blackstone Medical Services, which Holland & Knight notes binds Illinois, Indiana and Wisconsin. District courts have been piling on since:

• Lowrey v. Twilio, Inc. (W.D. Va. Oct. 1, 2026) held texts aren't "telephone calls" under § 227(c)(5) and that cell phones aren't "residential lines," per TCPAWorld's write-up. The plaintiff alleged the calls used an AI voice that read an OpenAI quota error out loud mid-call, which is why Twilio and OpenAI were named.
• Radvansky v. 1st Class Medical (D. Colo. Sept. 23, 2026) became, by Troutman Amin's count, the 17th district court to adopt the rule.
• Closer to home for us in Orlando, James v. Smarter Contact, Inc. (M.D. Fla. Mar. 31, 2026) reached the same result.

The holdout is California. In Combs (C.D. Cal. Oct. 2, 2026), a federal court held SMS are calls for do-not-call purposes, and TCPAWorld expects other courts in the Ninth Circuit to follow.

Does that make missed-call text-back risk-free?

No, and this is where we see owners overcorrect. Here's what the rulings move and what they leave alone:

Risk	Changed by the 2026 rulings?	What still applies
Federal do-not-call suits over texts, § 227(c)(5)	Mostly yes, outside the Ninth Circuit	California courts still allow them; no Supreme Court ruling yet
Autodialer and artificial-voice claims, § 227(b)	No	$500 per violation, up to triple if willful
AI-voice callbacks instead of texts	No	An AI voice is an artificial voice, so prior express consent applies
Florida Telephone Solicitation Act	No	Covers text messages by name; $500 per violation, up to triple
Revoking consent (STOP and similar)	No	Honor within 10 business days now; FCC 26-67 changes how it works once effective
A2P 10DLC carrier registration	No	Unregistered traffic gets filtered or blocked

Two rows matter most. Section 227(b) is the autodialer and prerecorded or artificial voice rule, with $500 statutory damages per violation, and none of these do-not-call cases touch it. And the FCC ruled in 2024 that AI-generated voices count as "artificial" under the TCPA. So the shops that "upgrade" from a text-back to an automatic AI voice callback move themselves into the stricter bucket, not out of it.

Why does a missed-call text usually count as informational?

Because the content decides the consent tier, not the technology. Marketing texts need prior express written consent under 47 CFR 64.1200. A text that only answers the caller's own inquiry ("Sorry we missed you, this is Lakeside Auto. What can we help with?") reads as informational. Add "and ask about this week's brake special" and you've written a telemarketing message.

Carriers draw a similar line. CTIA's Messaging Principles and Best Practices lists "initiating the text message exchange in which the Message Sender replies to the Consumer only with responsive information" as one form of opt-in. Read it carefully: that's the consumer starting a text exchange. A missed phone call isn't a text, so we don't lean on that line as cover. We lean on keeping the content responsive.

What does Florida's law add?

If your callers are in Florida, the Florida Telephone Solicitation Act, § 501.059, is the bigger threat. It defines a "telephonic sales call" as "a telephone call, text message, or voicemail transmission" made to solicit a sale, so the federal argument about the word "call" doesn't help you here. A call "in response to an express request of the person called" falls outside "unsolicited," which is why a narrow reply to the caller's inquiry is your friend.

The statute also gives you a cure window for texts. Before suing over text solicitations, the person must reply "STOP," and you have 15 days to stop. Damages are actual damages or $500, whichever is greater, up to triple if willful. That cure window only protects you if your system actually catches STOP. It's the first thing we test.

How do we build a missed-call text-back that holds up?

Our standard build looks like this. The phone system or Retell voice agent flags a missed or abandoned call. A webhook hands it to an n8n workflow (we covered why that logic belongs there in Retell Workflows vs. n8n and Zapier). The workflow checks the CRM for an opt-out on that number, sends one templated text through a registered Twilio Messaging Service, and logs the send, the template version and the delivery status against the contact.

The rules we bake in:

• One informational template. Business name, a one-line "how can we help," an option to reply or book. No offers, no coupons, no review requests.
• Separate marketing consent. If a caller wants promos, we capture written consent in a separate step, a checkbox on the booking form, and store it with a timestamp.
• Every opt-out word, everywhere. The inbound handler matches STOP and the other standard keywords and suppresses the number across every workflow, not just the text-back. Our FCC opt-out breakdown covers what FCC 26-67 changes. As of October 11 it still hadn't been published in the Federal Register, so it isn't in effect yet, and the current 10-business-day rule stands.
• No surprise AI calls. If the client wants an outbound AI callback, it only fires when the caller asked for one during the call, and the agent says it's AI, which we cover in our AI disclosure guide.
• Quiet hours. We don't text back at 2 a.m. just because the call came in then. Overnight calls go to the after-hours AI line or get queued for morning.

Why would a compliant text-back still fail?

Because of carrier registration. A2P 10DLC isn't a law. It's a carrier requirement run through The Campaign Registry, and per TCR's own 2026 overview, TCR doesn't approve campaigns. Your provider and its upstream partners do, and review can take 1 to 4 weeks. Unregistered texts fail quietly: your dashboard says "sent," and the caller gets nothing.

Two current changes matter for this build. Twilio rolled out more specific rejection codes on September 15, so a rejected campaign now tells you what to fix. And on October 1, Verizon raised its outbound A2P SMS surcharge from $0.0045 to $0.005 per message, according to Tychron's carrier fee notices. That's tiny per text, but it's a reminder that delivery costs move under you.

We register the text-back as a customer-care style campaign whose sample messages match the live template word for word, and we alert on delivery-failure webhooks so a filtered number gets caught in hours, not months.

What should you check before turning on missed-call text-back?

• The first text is informational only: business name, "how can we help," no promo
• Marketing consent is captured separately, in writing, with a timestamp
• STOP and every other opt-out keyword suppress the number across all workflows
• Florida numbers get honored well inside the 15-day window (we do it in seconds)
• The number is on an approved 10DLC campaign whose samples match the live text
• Delivery failures trigger an alert, not just a log line
• Outbound AI voice callbacks only fire when the caller asked for one
• Texts don't go out during quiet hours

If you want your missed calls turned into booked jobs without walking into any of this, see how our missed-call capture works, or book an AI systems assessment and we'll audit your current text-back, consent records and 10DLC registration on the call.

This is how we build and audit these systems, not legal advice. Have counsel review your message wording, especially if you text California or Florida numbers.