TwinEthos homeAPI access

Law

FCC Declaratory Ruling FCC 24-17 (AI voices under the TCPA; 47 U.S.C. 227, 47 CFR 64.1200)

Federal Communications Commission · United States (federal) (US) · 3 provisions encoded · verified against the official source as of 2026-10-04.

Informational data, not legal advice. Summaries and rules have not been reviewed by a lawyer: always verify official law text for decisions. A suggested guard is intended to address each rule; adding it is not a statement of compliance to that law.

Official text: docs.fcc.gov, www.ecfr.gov, www.govinfo.gov.

Trust and provenance 3 official sources · last verified 4 Oct 2026 · not reviewed by a lawyer · 3 of 3 provisions audit-grade · release 2026.10.05

Where this instrument's data comes from, how current it is, and what has and has not been checked. Each provision below has its own panel.

Official sources
Lanes
Binding law — in force 3
Verification
Sources last verified 4 Oct 2026; each provision states how.
Data release
Data release 2026.10.05, data as of 4 Oct 2026, schema 0.3.10.
Legal review
None of the 3 provisions has been reviewed by a lawyer; no TwinEthos rule has been legally reviewed yet. Treat each as research to check against the official text; it is not legal advice. Open questions for counsel on them: 3.
Audit standard
3 of 3 provisions audit-grade. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors
3 detectors, all experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify. Each provision lists its detectors' known limits.
Changes
  • 2026.10.05 (5 Oct 2026): 3 provisions added

Each data release records which provisions changed; the full list is on Changes.

Binding law — in force

State the responsible business's registered name at the start of every AI-voice call and give a callback number (47 CFR 64.1200(b)(1)-(2); FCC 24-17)

47 CFR 64.1200(b)(1) · official text · In force: applies since 8 Feb 2024 · United States (federal) (US)

All artificial or prerecorded voice telephone messages, which FCC 24-17 confirms include AI-generated voices (para. 9), must at the beginning state clearly the identity of the business, individual or other entity responsible for initiating the call, using the name under which a business is registered with the State Corporation Commission or comparable authority, and during or after the message state clearly a telephone number for it, not the autodialer's or a premium-rate number; for telemarketing that number must take do-not-call requests during business hours (47 CFR 64.1200(b)(1)-(2); 47 U.S.C. 227(d)(3)(A)). Detect outbound AI-voice call code with no configured caller identity or callback number.

Trust and provenance not reviewed by a lawyer · audit-grade · source verified 4 Oct 2026 · release 2026.10.05
Lane
Binding law — in force In force: applies since 8 Feb 2024
Official source
47 CFR 64.1200(b)(1) · captured 4 Oct 2026 · anchor hash (SHA-256) ea284453dbaa… · 5 more anchors in the data release
Verification
Quoted text found word for word in the captured official document (4 Oct 2026). Source last verified 4 Oct 2026: checked against the captured official document; not in the weekly watcher's list; checked against the captured document.
Data release
Data release 2026.10.05, data as of 4 Oct 2026, schema 0.3.10.
Legal review
Not reviewed by a lawyer. TwinEthos derived this rule from the official text it cites: treat it as research to check against that text; it is not legal advice. No TwinEthos rule has been legally reviewed yet. Open questions for counsel on this rule: 1.
Audit standard
Audit-grade: meets all 10 checks of the TwinEthos audit standard that apply to it. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors

1 detector (code pattern), experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify.

Known limits:

  • Opening line configured in the voice platform UI
  • Identity spoken by a TwiML document served from another service
  • The agent's first message may be set in the voice platform's dashboard or a prompt file outside the scanned code; check the configured opening. A company name constant used elsewhere suppresses the finding, so confirm i…

Who it applies to

  • Duty falls on: any person
  • Any person or entity whose telephone calls deliver an artificial or prerecorded voice message, including AI-generated or cloned voices and AI voice agents, to a called party in the United States, whether or not the call needed consent: every such message states the responsible entity's identity at its beginning and a callback telephone number during or after it. FCC 24-17 applies the rule to AI voices from 2024-02-08.
  • Whether it applies depends on facts outside the code; a person has to decide.

The guard to add

Open every AI voice call with the registered business name and give a callback number during or after the message.

Keep the caller identity as configuration (REGISTERED_BUSINESS_NAME, CALLBACK_NUMBER) and build the voice agent's first message from it, so the agent's first utterance states who is responsible for the call; put the callback number (not the dialer's number, never a premium-rate number) in the script or closing, and for telemarketing make it a line that takes do-not-call requests during business hours. Prompt instructions alone are not enough: set the first message explicitly (Retell begin_message, Vapi firstMessage, ElevenLabs first_message, Twilio <Say> before the agent connects) so the model cannot skip it.

Where it goes: 1 application source code, 3 config and feature flags, 7 prompt construction, 14 user-facing text.

What this provision adds:

  • Use the name the business is registered under with the State Corporation Commission or comparable authority, at the beginning of the message, and a callback number that is not the dialer's or a premium-rate number.

Example (Python + Retell AI), before:

agent = retell.agent.create(response_engine=ENGINE, voice_id=VOICE, begin_message='Hi! Do you have a minute?')

After:

BUSINESS_NAME = 'Acme Dental Group LLC'
CALLBACK_NUMBER = '+1-555-0100'
agent = retell.agent.create(response_engine=ENGINE, voice_id=VOICE,
    begin_message=f'Hello, this is an automated assistant calling on behalf of {BUSINESS_NAME}. You can reach us at {CALLBACK_NUMBER}.')

Control: An AI or artificial-voice call does not state, at its start, who is responsible for the call, and does not give a callback telephone number. The same guard addresses 1 item with binding law in 1 jurisdiction. Engineering guidance, not legal advice.

Rule id us-fcc-tcpa-ai-voice.ai-voice-call-identifies-caller-and-callback-number · review status: primary source derived

Binding law — in force

Give AI-voice telemarketing calls an automated opt-out that records the do-not-call request and ends the call (47 CFR 64.1200(b)(3), (a)(10))

47 CFR 64.1200(b)(3) · official text · In force: applies since 8 Feb 2024 · United States (federal) (US)

Where an artificial or prerecorded voice message, including an AI-generated voice (FCC 24-17 para. 9), includes or introduces an advertisement or is telemarketing, or is made under a residential exemption, and reaches a residential or wireless line, it must provide within two seconds of the identification an automated, interactive voice- and/or key press-activated opt-out with brief instructions; using it must automatically record the number to the caller's do-not-call list and immediately end the call, and a voicemail message must give a toll-free number reaching the same mechanism (47 CFR 64.1200(b)(3)). A called party may revoke consent by any reasonable method, including that opt-out mechanism, and revocations must be honoured within ten business days (64.1200(a)(10)). Detect AI-voice marketing call code with no opt-out handling.

Trust and provenance not reviewed by a lawyer · audit-grade · source verified 4 Oct 2026 · release 2026.10.05
Lane
Binding law — in force In force: applies since 8 Feb 2024
Official source
47 CFR 64.1200(b)(3) · captured 4 Oct 2026 · anchor hash (SHA-256) eeb5fa5e7aff… · 4 more anchors in the data release
Verification
Quoted text found word for word in the captured official document (4 Oct 2026). Source last verified 4 Oct 2026: checked against the captured official document; not in the weekly watcher's list; checked against the captured document.
Data release
Data release 2026.10.05, data as of 4 Oct 2026, schema 0.3.10.
Legal review
Not reviewed by a lawyer. TwinEthos derived this rule from the official text it cites: treat it as research to check against that text; it is not legal advice. No TwinEthos rule has been legally reviewed yet. Open questions for counsel on this rule: 1.
Audit standard
Audit-grade: meets all 10 checks of the TwinEthos audit standard that apply to it. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors

1 detector (code pattern), experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify.

Known limits:

  • Opt-out configured as a platform tool in a dashboard
  • Do-not-call list maintained by a separate dialer
  • Opt-out tools may be configured on the voice platform rather than in code; check the agent's tools and end-call behaviour. Informational calls outside (a)(3)(ii)-(v) still need opt-out only where the rule says so.

Who it applies to

  • Duty falls on: any person
  • Any person or entity delivering an artificial or prerecorded voice message, including an AI-generated voice or AI voice agent, that includes or introduces an advertisement or constitutes telemarketing, or is made under an exemption of 64.1200(a)(3)(ii)-(v), to a residential line or a wireless or other number listed in 64.1200(a)(1)(i)-(iii), in the United States; and every caller relying on prior express consent, for revocations (64.1200(a)(10)). FCC 24-17 applies the rule to AI voices from 2024-02-08.
  • Whether it applies depends on facts outside the code; a person has to decide.

The guard to add

Give every AI telemarketing call an automated opt-out that records the number to the do-not-call list and hangs up.

Right after the identification line, the agent says how to opt out ('Say stop or press 9 to be added to our do-not-call list'); a DTMF gather or a tool the model must call on an opt-out intent (end_call_and_add_to_dnc) writes the number to the do-not-call list and ends the call, without asking the person to confirm. Voicemail drops include a toll-free number that connects to the same mechanism. Any reasonable revocation heard by the agent marks the consent revoked, and the dialer honours it within ten business days at most (immediately is simplest).

Where it goes: 1 application source code, 6 API calls and integrations, 9 AI output handling, 15 agent action surface.

What this provision adds:

  • Offer the opt-out within two seconds of the identification, with brief instructions; record the number to the do-not-call list automatically and end the call immediately; voicemail drops give a toll-free number reaching the same mechanism.
  • Treat any reasonable revocation (a spoken 'stop', a key press, a reply) as definitive and honour it within ten business days at most; do not designate an exclusive revocation method.

Example (Python + Vapi), before:

client.calls.create(assistant_id=SALES_ASSISTANT, phone_number_id=PN, customer={'number': lead.phone})

After:

assistant = with_opt_out(SALES_ASSISTANT, script='Say stop or press 9 to opt out of future calls.',
                       on_opt_out=lambda number: (dnc.add(number), consents.revoke(number)))
if not dnc.contains(lead.phone):
    client.calls.create(assistant_id=assistant.id, phone_number_id=PN, customer={'number': lead.phone})

Control: An AI or artificial-voice telemarketing call offers no automated opt-out that records a do-not-call request and ends the call. The same guard addresses 1 item with binding law in 1 jurisdiction. Engineering guidance, not legal advice.

Rule id us-fcc-tcpa-ai-voice.ai-voice-telemarketing-automated-opt-out · review status: primary source derived

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.