> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Call consent and recording

> Prepare a calling review that separates contact permission, artificial-voice requirements, recording decisions, and requests to stop contact.

Decide who may be contacted and for what purpose before preparing a calling workflow. Review permission to place a call separately from permission to record, transcribe, or reuse information from it.

<Note>
  This is a review procedure, not authorization to call. Outbound calling remains unavailable in the [documented execution paths](/agents-platform/overview#current-availability). Do not treat a saved phone configuration or consent field as a working enforcement control.
</Note>

## 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](https://docs.fcc.gov/public/attachments/FCC-24-17A1_Rcd.pdf).

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](https://www.ftc.gov/news-events/news/press-releases/2024/03/ftc-implements-new-protections-businesses-against-telemarketing-fraud-affirms-protections-against-ai).

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

| Review item | Record before release |
| - | - |
| Purpose and parties | The business responsible for the call, the message, and whether the purpose changes during the interaction. |
| Recipients | The intended audience, relevant locations, and the source of the contact details. |
| Contact permission | The basis approved for this use, the scope of any consent, and where the evidence can be retrieved. |
| Identification and notices | The approved business identification, automation notice, and any required contact information. |
| Recording and transcription | Whether each is enabled, its purpose, the notice or consent approach, and what happens if a person declines. |
| Stopping contact | How a refusal or withdrawal reaches the system that determines eligibility for future calls. |
| Data handling | Who may access the evidence and conversation records, with the reviewed retention and deletion process. |

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

Use the [AI disclosure guide](/agents-platform/legal/ai-disclosure) to review identity and automation notices. Use the [Privacy Policy](https://threetone.in/privacy-policy) for Threetone's current information-handling policy.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is permission to call the same as permission to record?" id="faq-call-recording-permission">
    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.
  </Accordion>

  <Accordion title="Does an AI notice make a call permissible?" id="faq-call-ai-notice">
    A notice does not resolve whether the call may be placed. Review contact permission, applicable calling requirements, and the message itself before release.
  </Accordion>

  <Accordion title="Can the prompt manage requests to stop calling?" id="faq-call-stop-enforcement">
    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.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.