TCPA and Missed-Call Callbacks: What Businesses Can Do

The Telephone Consumer Protection Act restricts calls made with an automatic telephone dialing system or a prerecorded/artificial voice, and requires prior express consent for those specific call types, but a single manually placed callback to someone who just called your business is generally treated differently than a mass autodialed or prerecorded campaign (FCC, telemarketing and robocall rules, retrieved 2026-09-26). This guide explains what the FCC's rules actually distinguish between, and where businesses still need to be careful. It is not legal advice; confirm your specific setup with your own counsel.

This guide is for small business owners and office managers who want to return a missed call without a TCPA compliance headache. It covers what an autodialer is under current law, what consent means for automated versus manual calls, and a practical checklist for returning missed calls safely.

Key Takeaways

• The TCPA restricts calls made with an automatic telephone dialing system (ATDS) or prerecorded/artificial voice messages, and generally requires prior express consent for those (FCC, telemarketing and robocall rules, retrieved 2026-09-26).
• In Facebook, Inc. v. Duguid (2021), the Supreme Court narrowed the definition of an ATDS to a device that uses a random or sequential number generator to store or produce numbers, which excludes most systems that simply dial a specific, known number (Facebook, Inc. v. Duguid, 592 U.S. ___ (2021), Justia, retrieved 2026-09-26).
• Calling back the specific number that just called your business, manually and without a prerecorded message, is a materially different fact pattern than an autodialed telemarketing campaign, but the analysis depends on the equipment used and the content of the call.
• Consent can be revoked at any time, in any reasonable way, including a caller asking not to be called again (FCC, telemarketing and robocall rules, retrieved 2026-09-26).
• State rules on call recording and consumer calling can add requirements on top of the TCPA; check your state alongside the federal rules.
• Nothing here is legal advice. TCPA case law is still developing after Duguid, and businesses should confirm their calling technology and scripts with their own counsel.

On this page: What the TCPA actually restricts · What counts as an autodialer after Duguid · Manual callbacks vs automated campaigns · Consent, revocation and recordkeeping · A practical checklist before you call back · Where this fits into missed-call recovery · How This Guide Was Sourced · Frequently Asked Questions

What The TCPA Actually Restricts

The TCPA restricts calls made using an automatic telephone dialing system, and separately restricts calls that use a prerecorded or artificial voice message, whether or not an autodialer is involved (FCC, telemarketing and robocall rules, retrieved 2026-09-26). For calls that fall into either category, the caller generally needs the called party's prior express consent, and written consent specifically for prerecorded or autodialed telemarketing calls to a cell phone.

The law is federal and applies nationwide, but it operates alongside state-level rules on things like call recording consent and consumer protection, which can be stricter. It does not ban businesses from calling customers back; it restricts the technology and message type used to do it without consent.

What Counts As An Autodialer After Duguid

For years, courts disagreed on how broadly "automatic telephone dialing system" should be read, with some circuits treating almost any system that could dial stored numbers automatically as an autodialer. That changed in 2021.

In Facebook, Inc. v. Duguid, the Supreme Court held that a device only qualifies as an ATDS under the TCPA if it has the capacity to store or produce telephone numbers using a random or sequential number generator (Facebook, Inc. v. Duguid, 592 U.S. ___ (2021), Justia, retrieved 2026-09-26). A system that simply pulls a specific, known phone number, like the number that just called your business, from a call log and dials it does not fit that definition, because it isn't generating or selecting the number randomly or sequentially.

This narrowed the reach of the ATDS rules considerably, though it did not touch the separate restriction on prerecorded or artificial voice messages, which applies regardless of how the number was dialed.

Manual Callbacks Vs Automated Campaigns

There's a meaningful difference between two scenarios that businesses sometimes conflate:

The safest posture for any business returning a missed call is a live, manually initiated call (or an AI receptionist answering and calling back in real time as part of the same live interaction) rather than a batch, prerecorded, or algorithmically dialed follow-up to a list. This is a general description of the legal distinction, not a guarantee that any specific setup is compliant.

Consent, Revocation And Recordkeeping

Even where consent applies, it isn't permanent or automatic. The FCC's guidance states that a called party can revoke consent at any time, in any reasonable manner, including replying "stop" to a text or telling a caller directly not to call again (FCC, telemarketing and robocall rules, retrieved 2026-09-26). Once revoked, continuing to call or text can create exposure regardless of how the original consent was obtained.

Good recordkeeping practice, regardless of legal requirement, includes:

1. Log the date, time and number of every inbound call you intend to call back, so you can show the callback was tied to an actual inbound call, not a purchased list.
2. Note whether the callback was placed manually or through automated dialing equipment, since that distinction matters under Duguid.
3. Record any request not to be called again and suppress that number going forward.
4. Keep scripts free of prerecorded or artificial voice content unless you have documented prior express written consent for that specific call type.
5. Review your calling platform's technical description (does it use a random or sequential number generator, or does it simply redial a known number) with whoever built or sold it to you.

A Practical Checklist Before You Call Back

Before your team or your AI receptionist calls a missed caller back, confirm:

1. The number being called is the one that placed the inbound call, not a purchased or scraped list.
2. The callback is a live conversation, not a prerecorded or artificial voice message, unless you have documented consent for that.
3. The calling method does not generate or select numbers randomly or sequentially.
4. No prior "do not call" or revocation request exists for that number.
5. Your state's own call recording and consumer-calling rules are satisfied alongside the federal TCPA rules.

Where This Fits Into Missed-Call Recovery

Most of the TCPA exposure discussed above applies to outbound callback campaigns, not to a business answering its own live inbound calls. An AI receptionist that picks up every call on the first ring, the approach behind Voksha's missed call recovery page and its AI receptionist for small business, sidesteps most of this analysis entirely, because there is no outbound callback to place. Voksha's own security practices, including SOC 2 Type II compliance, cover how call data is handled once a call is answered. For the data on why fast callbacks matter when a call is missed anyway, see speed to lead: how fast should you return a missed call and missed call recovery: how to win back customers within 90 seconds.

How This Guide Was Sourced

This guide is based on the FCC's own consumer-facing telemarketing and robocall guidance and the U.S. Supreme Court's 2021 opinion in Facebook, Inc. v. Duguid, both retrieved 2026-09-26. No Voksha call data is used in this guide. This is general information, not legal advice, and TCPA interpretation continues to evolve in the courts after Duguid; confirm your specific calling setup and scripts with your own counsel before relying on any distinction described here. Written by the Voksha team. Voksha builds AI receptionists for small businesses; Voksha does not send SMS or text messages to callers.

Frequently Asked Questions

Does the TCPA stop a business from calling back a missed caller?

No. The TCPA restricts calls made with an automatic telephone dialing system or a prerecorded/artificial voice message without consent; it does not ban returning a call. A live, manually placed callback to the specific number that just called you carries different exposure than an automated campaign. Confirm your setup with counsel.

What changed with the Facebook v. Duguid Supreme Court case?

The Court narrowed what counts as an "automatic telephone dialing system" under the TCPA to devices that use a random or sequential number generator, which excludes systems that simply redial a specific known number (Justia, retrieved 2026-09-26). It did not change the separate rules on prerecorded or artificial voice messages.

Can an AI receptionist legally call a missed caller back?

An AI receptionist that answers an inbound call live, or places a live return call to the specific number that just called, is a different fact pattern than a mass autodialed or prerecorded campaign. The specific platform and call flow still need to be reviewed against TCPA rules and your state's requirements with your own counsel.

Do TCPA rules vary by state?

The TCPA is federal, but states can add their own consumer-calling and call-recording consent rules on top of it. Requirements vary and change, so check your specific state alongside the federal rules and confirm with your own counsel.

Conclusion

The TCPA targets automated, non-consensual outreach, not the basic act of returning a call to someone who just called you, but the technology and message type you use still matter and the law keeps evolving after Duguid. Confirm your specific calling setup with your own counsel before relying on any distinction in this guide. For a system that answers every inbound call live instead of relying on callbacks at all, see Voksha's pricing.