This is a review procedure, not authorization to call. Outbound calling remains unavailable in the documented execution paths. Do not treat a saved phone configuration or consent field as a working enforcement control.
Identify the applicable requirements
For a proposed U.S. deployment, the FCC’s AI voice ruling treats AI-generated human voices as artificial or prerecorded voices under the Telephone Consumer Protection Act. Its consent requirements and exceptions require a review of the actual call. Do not assume that interactive speech falls outside these rules. See FCC Declaratory Ruling 24-17. Telemarketing may also require a separate review under the FTC’s Telemarketing Sales Rule. The FTC has addressed AI-enabled calls and recordkeeping in its telemarketing rule update. Have a qualified reviewer determine the rules that apply to the intended recipients, purpose, and locations. This guide does not classify a campaign, select an exemption, or determine the recording rules for a jurisdiction.Assemble the calling review
Do not assume a purchased contact list, an existing account, or permission for another channel covers the proposed call. Give the reviewer the actual collection wording and evidence rather than a generic consent label.
Verify the intended controls
1
Review eligibility before calling
Design the calling integration to check the approved contact criteria before initiation. Prompt instructions are not a substitute for a check in the system that places the call.
2
Check notices and refusal paths
Review the opening, recording decision, request to stop, and request for another contact method. Use synthetic scenarios first. Verify the actual integration when its runtime path is released.
3
Trace a withdrawal through the workflow
Confirm which system records the request and prevents further contact within its reviewed scope. Include queued work and connected systems in the review; do not assume a conversation note updates them.
4
Keep retrievable evidence
Keep the approved wording and version, relevant permission evidence, control checks, and release decision under appropriate access controls. Have the reviewer set the retention requirements for this evidence.
Frequently asked questions
Is permission to call the same as permission to record?
Is permission to call the same as permission to record?
Review them separately. The intended use, applicable rules, and the person’s choices may differ. Do not make one consent field stand in for every decision.
Does an AI notice make a call permissible?
Does an AI notice make a call permissible?
A notice does not resolve whether the call may be placed. Review contact permission, applicable calling requirements, and the message itself before release.
Can the prompt manage requests to stop calling?
Can the prompt manage requests to stop calling?
The prompt can describe the intended response. A reliable workflow also needs a verified mechanism to record the request and apply it to future contact. This guide does not claim that such a mechanism is currently supplied by Threetone.