The short answer
The TCPA is the statute that governs whether an automated call may lawfully be placed at all. It matters acutely for voice AI because an AI-generated voice is an artificial voice under the Act, which places these calls in a category requiring consent — and it carries a private right of action with statutory damages per call.
In detail
The core restrictions cover automated dialling and artificial or prerecorded voice messages to mobile numbers, calls outside permitted local hours, disregard of do-not-call requests, and failure to identify the caller. The FCC has confirmed that AI-generated voices fall within the artificial-voice provisions, which removes any argument that a conversational agent is outside the Act because it is not playing a recording.
Consent requirements differ by call purpose, and the distinction is the one most often collapsed. Marketing calls to a mobile number generally require prior express written consent, which means a signed or electronically signed agreement that discloses the automated nature of the calls and is not conditioned on a purchase. Purely informational calls to an existing customer sit under a lower standard. Calling a number under a consent record that does not cover the actual purpose is a violation.
Enforcement is what gives the statute its weight. Statutory damages are assessed per call, trebled for wilful violations, and the private right of action makes class actions economically attractive to plaintiffs’ firms. Because the exposure scales with volume, an automated dialler that misapplies a rule produces liability in proportion to how well it works.
This entry is general information about a widely cited statute, not legal advice. Requirements change through FCC rulemaking and litigation, and obligations depend on the specific facts of a calling programme. Anyone running outbound campaigns should have the programme reviewed by qualified counsel.
How Rexa handles it
Rexa enforces several TCPA-adjacent controls in the dispatch path rather than leaving them to campaign configuration: recipient-local calling windows, a do-not-call gate that runs before dispatch, per-destination daily caps defaulting to three attempts with a platform ceiling of five, and mid-call opt-out detection. These are platform behaviours, not a legal opinion on any specific campaign.
Compliance overviewRelated terms
Do Not Call
Do Not Call refers to the registries and internal lists of numbers that must be suppressed from telemarketing contact.
Calling window
A calling window is the range of local hours during which it is permissible to place a call to a recipient, with the hours outside it known as quiet hours.
Consent capture
Consent capture is the process of obtaining, recording and retaining evidence that a person agreed to be contacted.
Opt-out keyword
An opt-out keyword is a word or phrase that, when spoken or sent by a recipient, is treated as a request to stop being contacted.