Somewhere in the first four seconds of an AI-led sales call, someone has to say the quiet part out loud: this voice is not a person. Many teams treat that sentence as a legal tax and mumble it — a mistake twice over, because badly delivered disclosure erodes trust faster than honest disclosure ever could, and in a growing list of jurisdictions the sentence is not optional. Here are the script patterns, the legal triggers behind them, and an honest look at what disclosure does to the conversation.
Why the opening line carries the legal weight
Most disclosure obligations attach to the start of the interaction, not to a line buried in a privacy policy. The FCC’s February 2024 Declaratory Ruling confirmed that AI-generated voices are “artificial” voices under the TCPA, pulling AI sales calls into the existing consent and identification regime, and the still-pending NPRM 24-84 proposes an explicit AI disclosure at the start of each call. In the EU, Article 50 of the AI Act applies from 2 August 2026 — people must be told they are dealing with an AI system unless it is already obvious. Several US states got there first. The practical question is not whether to disclose, but how to keep the person on the line while you do.
Six opening-line patterns you can adapt
These are generic templates, not measured performers — we make no claims about answer rates or conversion lift. Any vendor who quotes a precise number for “the script that works” should be asked for the study.
1. Plain disclosure
“Hi [name], this is [agent name], an AI assistant calling from [company]. Have I caught you at an okay time?”
The baseline: identity, AI status, company, permission check. It satisfies the “clear and conspicuous” language most statutes use, and it sounds like a normal call opening with one extra word in it.
2. Disclosure plus reason
“Hi [name], I’m [agent name], an AI assistant from [company]. You asked for a quote on [product] on Tuesday — I can sort that out for you now, or arrange a callback. Which suits?”
An immediate, specific reason gives the listener something to respond to other than the AI status itself. The context does the persuading; the disclosure rides along.
3. Disclosure plus opt-out
“Hi [name], this is [agent name] — I’m an AI assistant with [company]. If you’d rather deal with a person, just say ‘human’ at any point and I’ll transfer you. Otherwise, I’m calling about [reason].”
Offering the exit up front converts the disclosure from a warning into a choice. It only works if the transfer genuinely happens — see our post on AI-to-human handoff without losing context.
4. Regulated-industry variant
“Hi [name], I’m [agent name], an AI assistant — not a licensed adviser — calling on behalf of [firm]. I can answer general questions and book you in with [licensed person], but anything that needs advice stays with them.”
For finance, health, legal and similar licensed services. Utah’s amended AI Policy Act expects prominent up-front disclosure in high-risk interactions of exactly this kind, and stating the limits of the agent’s role avoids the separate problem of an AI implying professional advice.
5. Inbound and callback variant
“Thanks for calling [company] — you’re speaking with [agent name], an AI assistant. I can handle most things end to end, and you can ask for a person at any time. What can I do for you?”
Inbound callers chose to talk to you, so the disclosure lands more softly — but it is still required wherever a realistic voice could be mistaken for a human. Say it before the first question, not after.
6. Consent-anchored outbound variant (US telemarketing)
“Hi [name], this is [agent name], an AI assistant from [company]. You opted in for updates when you [signed up / requested a demo]. This call uses an AI voice — say ‘stop’ any time and we won’t call again. The reason I’m ringing is [reason].”
Where TCPA prior express written consent applies, restating the consent basis and the revocation route aligns the script with what the consent regime already demands, including the identification and callback-number rules for artificial-voice calls.
Jurisdiction table: what triggers disclosure, and what the opening must contain
| Jurisdiction | What triggers disclosure | What the opening line (or call) must contain |
|---|---|---|
| US federal | FCC Feb 2024 Declaratory Ruling: AI-generated voices are “artificial” voices under the TCPA. NPRM 24-84 (adopted Aug 2024) proposes an explicit AI disclosure duty — still a proposal, with no final rule adopted in CG Docket 23-362 as of early August 2026. | Prior express (written, for telemarketing) consent; identify the responsible entity at the start and provide a callback number under existing artificial-voice rules (47 CFR § 64.1200). Explicit “this is AI” wording is proposed, not yet mandated federally. |
| Utah | AI Policy Act (SB 149, 2024), narrowed by SB 226 and extended by SB 332 (2025, sunset now July 2027): disclosure when a person asks, and prominent up-front disclosure in “high-risk” interactions — regulated services collecting sensitive information for financial, legal, medical or mental-health decisions. | If asked “am I talking to a robot?”, a clear yes. In high-risk regulated interactions, prominent disclosure before the substance starts; clear disclosure at the outset supports the law’s safe harbour. |
| Maine | Title 10 § 1500-DD (in force since Sept 2025): using an AI chatbot in trade or commerce in a way that could mislead a reasonable consumer into thinking they are dealing with a human. | Clear and conspicuous notification that the consumer is not engaging with a human being — for a realistic voice agent, that means saying so at the outset. Violations are Maine Unfair Trade Practices Act violations. |
| California | AB 2905 (effective 1 Jan 2025) amended Public Utilities Code § 2874: calls made with automatic dialing-announcing devices must inform the called person if the prerecorded message uses an artificial voice, defined to include voices generated or significantly altered using AI. The B.O.T. Act (SB 1001) covers online bots on large platforms, not phone calls. | Tell the called person the message uses an artificial voice, alongside the long-standing identification requirements for announcing devices. |
| Colorado | The 2024 Colorado AI Act (SB 24-205) — including its general duty to tell consumers they are interacting with AI — was repealed before taking effect and replaced by SB 26-189 (signed May 2026), a narrower framework applying from 1 Jan 2027 centred on automated decision-making technology in consequential decisions. | From 2027: clear and conspicuous notice where covered ADMT is used in a consequential decision (lending, housing, employment and similar), plus adverse-outcome explanations. No general “announce the AI on every sales call” duty survives — the FCC baseline still applies to Colorado calls. |
| EU | AI Act Article 50(1), applicable since 2 August 2026: AI systems interacting directly with natural persons must disclose, unless obvious to a reasonably well-informed, observant and circumspect person. Not deferred — Regulation (EU) 2026/1744 pushed back the Annex III high-risk regime to December 2027, but left Article 50 in force. | Inform the person they are interacting with an AI system, in the interaction itself. A realistic sales voice is precisely the case where “it’s obvious” does not apply. |
| Australia | No AI-specific disclosure statute. The Telecommunications (Telemarketing and Research Calls) Industry Standard 2017 governs telemarketing conduct; a Privacy Act automated-decision-making transparency obligation (privacy-policy level) commences 10 December 2026. | Standard telemarketing duties: calling-line identification, permitted hours, immediate termination on request, identifying the business and purpose. Saying “this is an AI assistant” is best practice, not (yet) statutory. |
Statuses verified as of 10 August 2026. General information, not legal advice — get counsel for your own campaigns and jurisdictions.
The hang-up question, honestly
Does announcing the AI cost you the conversation? The most-cited evidence says disclosure can carry a real penalty. A 2019 field experiment in Marketing Science (Luo, Tong, Fang and Qu) found that when a fintech’s voice chatbot disclosed its machine identity before the conversation, purchase rates fell by more than 79.7% and calls got shorter — even though the undisclosed bot sold as well as proficient human agents.
Three honest caveats. First, that study predates modern conversational voice agents by several years, and it measured purchases, not hang-ups. Second, its mitigation finding — disclosing later softened the penalty — is not available to you, because the statutes above require disclosure at the outset. Third, we found no recent peer-reviewed study of hang-up rates for disclosed AI voice agents that we could verify at the owner’s own page, so we will not quote the retention percentages that circulate in vendor blogs. The lever you actually control is script quality: a confident, specific, opt-out-offering disclosure is a different experience from a mumbled compliance line, even if nobody can honestly tell you the delta in basis points.
Design notes that make the scripts work
- First sentence, not first minute. Regulators say “outset”; listeners decide in seconds anyway.
- Give the agent a name. “This is Ari, an AI assistant” is disclosable and personable; “this is an automated system” invites the hang-up.
- Never apologise for being AI. Apology frames the call as an imposition. State it, then move to the reason.
- Make the human path real. An opt-out offer that dumps people into voicemail is worse than none. Escalate on request and on uncertainty — see how confidence thresholds decide when the agent should stop guessing.
- Log the disclosure. Keep the opening in your call recordings and transcripts so you can evidence it later.
- Mind the voice itself. Cloned voices raise a separate consent problem — covered in our guide to voice cloning on business calls.
This is the layer Zian builds for: our agents run live phone, SMS, email and WhatsApp outreach with disclosure-first openings, escalation to humans, and script variants split-tested through PrecisionPitch AI™ — the disclosure line is part of the script to be organised and refined, not a legal footnote.
FAQ
Do US federal rules already require me to say “this is an AI” on every call?
Not in those words, yet. The TCPA regime requires consent for artificial-voice calls and the FCC’s February 2024 ruling confirmed AI-generated voices count as artificial, so identification and callback-number duties apply now. An explicit AI-disclosure duty was proposed in NPRM 24-84 in August 2024, but no final rule had been adopted as of early August 2026 — and several states already require disclosure regardless.
What exactly does Maine require?
Maine’s law, Title 10 § 1500-DD, says a person may not use an AI chatbot to engage in trade and commerce in a manner that may mislead a reasonable consumer into believing they are engaging with a human being, unless the consumer is notified in a clear and conspicuous manner that they are not engaging with a human — see the statute text at the Maine Legislature. For a natural-sounding voice agent, that effectively means proactive disclosure at the start of the call.
Is the EU disclosure duty in force, or was it delayed with the rest of the AI Act?
It is in force. Article 50 transparency applies from 2 August 2026. The Digital Omnibus (Regulation (EU) 2026/1744) deferred the Annex III high-risk obligations to December 2027, but did not defer Article 50 — sales calls into the EU need disclosure now.
If disclosure hurts conversions, can I disclose later in the call instead?
No. The research that found a smaller penalty for late disclosure describes a tactic the rules do not permit: Maine, California’s artificial-voice rule and EU Article 50 all point to notification at the outset or in the interaction itself, and the FCC’s proposal is disclosure at the start of each call. Treat timing as fixed and spend your effort on the quality of the opening line.
Does Australia require AI disclosure on sales calls?
There is no AI-specific disclosure statute in Australia today. Outbound calls must follow the ACMA telemarketing standard — calling-line identification, permitted hours, ending the call on request — and a Privacy Act transparency obligation for automated decision-making takes effect on 10 December 2026 at the privacy-policy level. Disclosing the AI on the call is best practice, and pairs with channel rules like the SMS Sender ID Register for text follow-ups.