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
Every message an AI voice agent or text-to-speech system delivers on a call states clearly, at the beginning, the identity (registered business name) of the entity responsible for initiating the call, and states during or after the message a telephone number for that entity.
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.
Reach
Law in force in United States (federal) (US).
Trust and provenance
How far the rules this guard addresses have been checked. Each rule links to its provision, with its citation, official text and its own panel.
- This control
- Audit-grade: meets all 3 checks of the TwinEthos audit standard that apply to it.
- Lanes
- Binding law — in force 1
- 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 1 rule 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: 1.
- Audit standard
- 1 of 1 rule 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
- 1 detector, 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.
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 reviewers look for: a fixed first message or pre-agent <Say> that names the registered business, generated from configuration; a callback number in the script; no outbound voice agent whose opening is left to the model.
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}.')Engineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.
Every rule this guard addresses
Binding law — in force (1)
- United States (federal) (US)
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.