Is Missed Call Text Back TCPA Compliant? The Plain-English Guide

The short answer

Texting back a customer who just called you is generally fine. Their inbound call is treated as consent to a reasonable, non-marketing response about why they called. The legal risk in business texting almost never comes from the text-back itself — it comes from what businesses do next: promotional follow-ups without written consent, ignored STOP replies, and messages sent at the wrong hours.

That distinction matters because the penalties are per message. TCPA statutory damages are $500 per violation, up to $1,500 when willful — multiplied across every text in a campaign, which is why settlements routinely reach six and seven figures. Compliance is not a nice-to-have in this category; it is the category.

The two consent tiers, and where a missed call sits

The TCPA (47 U.S.C. § 227) and the FCC's rules around it draw one line that explains almost everything:

• Transactional / informational texts — responding to a customer's call, confirming their appointment, answering their question. These need prior express consent, and a customer voluntarily calling your business and leaving their number is the textbook example of giving it.
• Marketing texts — offers, promotions, campaigns, anything that advertises. These need prior express written consent: a signature or checkbox, tied to disclosure language naming your business, that the customer can refuse without being denied service. A phone call is never written consent.

So the automatic "Sorry we missed your call — how can we help?" is on the safe side of the line, and so is the AI conversation that follows about pricing, hours, and booking, because the customer is asking and you are answering. A "20% off this week only!" blast to that same number three weeks later is on the other side of the line — different message, different consent requirement.

Quiet hours

Federal rules prohibit texting before 8 a.m. or after 9 p.m. in the recipient's local time. An instant text-back to a live call effectively self-complies — the caller is holding their phone — but two cases need real enforcement in software:

• Scheduled follow-ups and reminders, which must be windowed to local time.
• Stricter state windows — Florida, for example, ends the texting day at 8 p.m. and caps how many times you can contact someone about the same matter in 24 hours.

Opt-outs: the part that generates lawsuits

Every recipient has the right to revoke consent, and revocation does not have to use the magic word — courts and the FCC treat any reasonable expression ("stop", "unsubscribe", "don't text me") as valid. Recent FCC rules require honoring revocations promptly, and the safe engineering answer is immediately and automatically:

• STOP, UNSUBSCRIBE, and variants suppress the number without a human in the loop.
• HELP returns your business name and contact info.
• The opt-out is recorded with a timestamp, because in a dispute the record is the defense.

The carrier layer: A2P 10DLC

Separate from the law, US carriers require businesses texting from regular 10-digit numbers to register their brand and use case (A2P 10DLC). Unregistered traffic gets filtered — your texts simply stop arriving — and carriers enforce their own content rules on top. This is why "just use a personal cell" is not a real alternative for business texting at any volume, and why a platform should handle registration for you. One number, one registered use — a number recycled across businesses or campaigns is a deliverability and compliance liability.

State mini-TCPAs

Florida's FTSA, Oklahoma, Washington, and a growing list of states layer their own rules on top of the federal ones — tighter hours, frequency caps, and private rights of action of their own. The practical takeaway for a local business is not to memorize fifty statutes; it is to keep your texting to the transactional side of the line, honor opt-outs instantly, and let your platform enforce the windows.

If an AI is doing the texting, say so

Where the conversation is held by AI — as it is with CompleteLine — the first message should say so plainly, and it should note when conversations are recorded or stored. Several states are legislating in exactly this direction, and disclosure costs nothing: customers do not abandon conversations because an assistant is honest about being one. CompleteLine builds the disclosure into the message pipeline itself rather than offering it as a setting, so it cannot be turned off per client.

The compliance checklist

1. Text back only numbers that contacted you first — inbound call or text, never purchased lists or scraped numbers.
2. Keep automatic texts transactional — respond, answer, book. No promotions without prior express written consent collected separately.
3. Honor STOP instantly and automatically, keep timestamped opt-out records, and support HELP.
4. Respect quiet hours on anything scheduled — 8 a.m.–9 p.m. local federally, tighter where states say so.
5. Register your number (A2P 10DLC) and never reuse a number across businesses or campaigns.
6. Disclose AI in the first message when an AI holds the conversation.
7. Keep records — consent, conversations, opt-outs. The paper trail is the protection.

Frequently asked questions