> ## 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.

# AI identity and disclosure

> Review how an agent identifies the business, explains its use of AI, describes its abilities, and responds when someone requests human help.

Make it clear who the agent represents and how it participates in the interaction. Review the full experience, including the displayed name, voice, greeting, generated responses, links, and actions.

The FTC's government and business impersonation rule addresses materially false identity and affiliation claims. An agent's name, voice, and wording should not create a misleading impression about the organization behind it. See the [FTC's explanation of the impersonation rule](https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-highlights-actions-protect-consumers-impersonation-scams).

<Note>
  The checks below are design recommendations for a deployment review. They do not provide a universal disclosure script or determine the legal requirements for every location or channel. Review applicable requirements with qualified advisers and check [runtime availability](/agents-platform/overview#current-availability).
</Note>

## Review the opening

<Steps>
  <Step title="Identify the responsible business">
    Use the approved business name and describe the purpose of the interaction. Check that the voice, display name, and contact information represent that business accurately.
  </Step>

  <Step title="Explain the use of AI">
    Prepare a short, understandable explanation that the person is interacting with an AI assistant. Review its placement, language, and audibility before the person is asked to act or provide information.
  </Step>

  <Step title="Describe the actual scope">
    State what the assistant can help with. Avoid claims of human identity, professional authority, guaranteed results, or completed actions that the integration cannot support.
  </Step>

  <Step title="Offer a real alternative">
    Identify the supported route for human assistance or another contact method. If live transfer is unavailable, provide the verified alternative without claiming that a transfer has started.
  </Step>
</Steps>

Review recording and transcription notices separately with the [call consent checklist](/agents-platform/legal/call-consent). An AI notice should not be used as a substitute for those decisions.

## Test the experience

Prepare an approved response for each scenario, then verify it in the released integration. Saving a first message or prompt only prepares the configuration.

| Scenario | Check |
| - | - |
| The person interrupts the greeting | The business identity and AI explanation remain understandable. |
| The person asks whether the agent is human | The answer acknowledges the use of AI directly. |
| The conversation changes language | The explanation remains accurate and comprehensible in the selected language. |
| The person asks for a person | The response describes the assistance route that actually exists. |
| A tool fails or has no result | The agent does not claim success, confirmation, or an action that did not occur. |
| The voice resembles a real person | The reviewer checks the authority to use it and whether the presentation could mislead the listener. |

Keep the reviewed wording with the agent version and the intended channel. Recheck it when the voice, first message, language policy, connected actions, or assistance route changes. See [prompting](/agents-platform/configure/agent-behavior/prompting) and [versioning](/agents-platform/deploy/versioning) for configuration review.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is a notice hidden in the privacy policy enough?" id="faq-ai-notice-placement">
    Do not assume a policy link resolves the interaction's disclosure requirements. Have the reviewer determine what must be communicated, where, and when. This guide recommends making the use of AI clear in the interaction itself.
  </Accordion>

  <Accordion title="Can an agent use a friendly name?" id="faq-ai-agent-name">
    Review the name together with the voice and greeting. The presentation should not imply that a specific person is speaking or that the assistant has an affiliation or authority it does not have.
  </Accordion>

  <Accordion title="Does identifying the agent as AI approve the rest of the workflow?" id="faq-ai-disclosure-scope">
    No. Review calling permission, recording, data use, action authorization, and any sector-specific requirements separately. Clear identity is one part of the deployment review.
  </Accordion>
</AccordionGroup>


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