- 1Capture prior express written consent
Determine whether the call requires prior express written consent or another consent standard. If written consent applies, confirm the approved authorization and store the supporting record with the campaign context.
- 2Disclose the AI and the recording up front
Use approved notice language for the call type and applicable policy. A sample AI or recording notice is not a universal script and does not itself establish consent.
- 3Honor opt-outs and the Do-Not-Call list
Identify which opt-out and suppression requirements apply to the call and campaign. Confirm the caller-facing mechanism, processing workflow, applicable timing, and evidence of suppression checks with the policy owner.
- 4Respect calling-time windows
Check the applicable federal, state, and campaign time restrictions, including how the called party's location is determined. Record the control and how exceptions are handled.
- 5Keep an auditable record of every call
Identify which consent, disclosure, opt-out, and call records your process must retain. Keep each source of evidence in the system responsible for capturing it; Trace call analysis does not create consent or dialing-system records.
The checklist (print this)
- What consent standard applies to each call type, and where is the supporting record kept?
- Which AI, recording, or caller-identification notices apply, and when must they be given?
- Which opt-out and suppression rules apply, and how are requests processed and recorded?
- What calling-time restrictions apply to the audience and jurisdictions in scope?
- Which systems capture consent, dialing, call, and review evidence?
- Who reviews exceptions, missing records, and policy changes?
Call review can help inspect what happened in submitted conversations. Trace can surface configured speech and sensitive-data findings with supporting evidence. It cannot establish caller consent, verify a suppression list, or determine whether a call met the TCPA. Those facts require other records and legal review. Trace can be used with PyAI Omni agents or on your existing stack.
Frequently asked questions
What should our review checklist include?+
Define the call population and purpose, identify the consent and opt-out requirements that apply, check the relevant notices and calling controls, and decide which records support each conclusion. Review the requirements with counsel.
Do I need written consent or is a verbal okay?+
Marketing/telemarketing calls with an artificial or prerecorded (AI) voice generally need prior express written consent. Verbal 'prior express consent' is generally only sufficient for non-marketing informational calls.
How can call analysis support a TCPA review?+
Call analysis can help reviewers examine what was spoken in submitted interactions. Consent evidence, dialing-system behavior, suppression-list checks, and the legal conclusion require other records and qualified review.
Primary sources
We cite primary law. Statutes, rulings, and state laws change, confirm currency before relying on them.
- 47 U.S.C. § 227 (TCPA)
The federal statute governing autodialed and prerecorded/artificial-voice calls.
- 47 CFR § 64.1200 (FCC rules)
The FCC's implementing rules, including the prior-express-written-consent requirement.
- FCC Declaratory Ruling (Feb 8, 2024)
AI-generated and voice-cloned calls are an 'artificial or prerecorded voice' under the TCPA.