What is a good script for a call recording disclosure?

Why 'This Call May Be Recorded' Isn't Enough Anymore

For decades, "this call may be recorded for quality assurance" has been the background noise of every customer service line in America. That single sentence now sits on shaky legal ground — and treating it as automatically sufficient is one of the fastest ways to accumulate six-figure liability, one phone call at a time.

The core problem is jurisdictional. The United States splits between roughly 38 one-party consent states and a bloc of all-party consent states — sources count them differently, with one analysis listing 11 and another listing 12, flagging Nevada and Michigan as ambiguous. In all-party states, every person on the call must consent before the record button means anything.

Worse, "may be recorded" language isn't a guaranteed safe harbor anywhere. As compliance research makes clear, its adequacy depends on timing, whether affirmative consent is required, the stated purpose, and whether the caller can actually refuse. And California's reach extends across state lines under Kearney v. Salomon Smith Barney, so a caller's physical location — not your business's — can determine which law governs the call.

The stakes are not theoretical:

• California carries $5,000 statutory damages per violation — 100 improperly recorded calls could mean $500,000 in exposure, per legal analysis of the state's Invasion of Privacy Act.
• Federal law adds $100–$1,000 per repeat violation under 18 U.S.C. § 2520, plus criminal penalties up to five years.
• Capital One paid a documented $75.5 million class action settlement over recording practices.

This is why guessing each caller's location per call is operationally fragile. SalesArmor describes per-call jurisdiction tracking as "one mistake away from liability", and mature sales organizations have largely abandoned it. Area codes don't prove location, callers travel, and one missed guess in a California-bound call is a $5,000 event.

The emerging consensus is simpler: default to the strictest standard everywhere. Identify the strictest applicable law and build every recording practice around it, rather than maintaining a patchwork of state-specific scripts. At GrowthPros, we apply the same logic to lead follow-up — every consent-recorded lead carries a documented disclosure trail, because a lead without provable consent is a liability, not an asset.

A compliant disclosure also costs about four seconds. That's a small price against a $75.5 million precedent.

The One-Standard Fix: Universal All-Party Consent

Standardizing on all-party consent everywhere eliminates the operational risk of tracking jurisdiction per call, especially when caller location cannot be reliably verified. This approach aligns with the strictest applicable law governing cross-border calls, which research shows generally governs due to extraterritorial reach like California’s Invasion of Privacy Act. By adopting a universal standard, businesses avoid liability from misjudging state-specific rules — a protection highlighted by mature sales organizations that find per-call tracking "operationally fragile and one mistake away from liability."

Effective disclosure requires timing the notice before any substantive discussion begins, as mid-call notification cannot retroactively legitimize earlier recorded content under laws like California Penal Code § 632. The disclosure must also be refusable, offering callers a clear path to decline recording without penalty — such as continuing the call unrecorded or using an alternative contact method. Scripts that end with a direct question inviting affirmation, like “Is that okay with you?” or “Do I have your permission?”, capture verifiable consent on the recording itself and typically take about four seconds to deliver.

For GrowthPros, which delivers AI-powered voice, SMS, and email follow-ups within a five-minute window to ensure speed-to-lead advantage, this universal approach simplifies compliance across outbound campaigns. Since every lead includes an AI-initiated contact attempt, embedding a consistent, legally sound disclosure at the start of each interaction protects both the business and the lead’s rights. This is especially critical when AI transcription is involved, as separate disclosure for both recording and transcription is required when automated tools are used.

• Deliver the disclosure before any substantive business discussion to ensure validity
• End the script with a question that invites affirmative consent on the recording
• Provide a clear, non-penalized alternative for callers who decline recording
• Include explicit mention of transcription when AI tools are used to process the call
• Document consent or decline as part of the lead’s permanent record in the CRM

By building consent into the lead delivery process — complete with timestamp, IP address, and contacting party — GrowthPros ensures every interaction meets the highest standard of compliance while maintaining the speed and personalization that drive conversion. This universal all-party consent framework doesn’t just reduce legal risk; it creates a transparent, respectful foundation for every customer conversation.

Five Ready-to-Use Disclosure Scripts (Inbound, Outbound, IVR, AI)

A disclosure that works takes about four seconds of call time — and skipping it can cost $5,000 per call in California. That asymmetry is why the best scripts are short, state a reason for recording, and end with a question inviting a yes, according to sales compliance guidance. Here are five templates you can adapt today.

1. Inbound — notice-and-continue. For one-party states where notice suffices: "Thank you for calling [Business Name]. This call may be recorded for quality assurance, training, and accurate recordkeeping. Please tell our representative if you prefer not to be recorded." This standard inbound format works because it informs without blocking the conversation.

2. Inbound — explicit verbal consent. Safer for all-party states: "Before we continue, I need to let you know that this call will be recorded for [approved purpose]. Do I have your permission to proceed with the recording?" The question captures affirmative consent on the recording itself.

3. IVR keypress. "Thank you for calling [Business Name]. We would like to record this call for [approved purpose]. Press 1 to consent and continue. Press 2 to use our approved non-recorded option." Legal analysis ranks active keypress acknowledgment above beep tones, which are now considered obsolete for business use.

4. Outbound. "Hello, this is [Agent Name] calling from [Business Name] about [brief reason]. Before we continue, I would like to record this call for [approved purpose]. Is that okay with you?" Outbound calls carry extra weight: FTC Telemarketing Sales Rule — actually the Telemarketing Sales Rule — requires prompt disclosure and two-year recordkeeping.

5. AI recording plus transcription. "Before we continue, please note that this call may be recorded and transcribed using automated tools for [approved purpose]. Do you consent to the recording and transcription?" Compliance guidance is clear: automated transcription requires separate disclosure — the script must describe both the recording and the transcript.

Three rules make any script effective:

• Keep it under four seconds — long disclosures lose callers and invite hang-ups.
• State a reason — quality assurance, training, or recordkeeping all work; "because we can" does not.
• End with a question — a "yes" on the recording is affirmative consent you can produce later.

GrowthPros applies this last principle to every lead we deliver: each contact carries a consent record with the disclosure text, timestamp, and named contacting party, so the trail exists before your team ever picks up the phone. Whatever script you choose, legal best practice says to identify the strictest standard that applies to your calls and build around it — because caller location can't be reliably verified, and one mistake can mean six-figure exposure.

Beyond the Script: Opt-Outs, AI Transcription, and Retention

A script is only the first four seconds of a much longer compliance process. What happens after the caller answers — or refuses — determines whether your disclosure actually protects you.

Consent that cannot be refused is not legally meaningful consent, according to compliance guidance from Smith.ai. Callers who decline must have a real alternative: an unrecorded continuation or a different contact channel. Build a declined-consent process, not just a script:

• Pause the recording immediately and confirm it stopped before continuing the conversation.
• Offer an alternative — an unrecorded line, a callback, or a written channel.
• Document the decline: who declined, when, and what alternative was offered.
• Train employees never to pressure a caller into reversing the decision.

If automated tools create transcripts, your notice must accurately describe both the recording and the transcription — a recording-only disclosure doesn't cover the transcript. A compliant version looks like: "Before we continue, please note that this call may be recorded and transcribed using automated tools for [approved purpose]. Do you consent to the recording and transcription?" That template comes from Dial Raven's disclosure script library, and it matters for any business running AI-driven follow-up calls, including the speed-to-lead sequences GrowthPros attaches to every delivered lead.

Indefinite retention is a liability surface, not a safety net. The FTC's Telemarketing Sales Rule requires two years of recordkeeping for telemarketing records, while financial services firms face roughly six years under Exchange Act Rules 17a-3 and 17a-4. Pair retention limits with restricted access and honored deletion requests.

If an answering service or call-handling vendor records calls on your behalf, your business — not the vendor — remains legally accountable for the consent notification. That principle, highlighted in Smith.ai's call recording analysis, means your disclosure script needs to travel with your calls wherever they're handled. The stakes justify the effort: California carries $5,000 statutory damages per violation, and 100 improperly recorded calls could mean $500,000 in exposure. Four seconds of script, backed by a real process, is the cheapest insurance you'll ever buy.

Want leads that arrive with their consent trail already attached — disclosure text, timestamp, and all? Book the 15-minute qualification call and see how qualified, consent-recorded leads get followed up inside the promised window.

How GrowthPros Handles Consent on Every Lead

A disclosure script is only as defensible as the consent trail behind it. If you can't prove the person on the other end of the line agreed to be contacted — and recorded — your carefully worded script is built on sand.

That's why GrowthPros treats consent as a deliverable, not an afterthought. Every lead we deliver carries a consent record containing the disclosure text the prospect saw, the timestamp, the IP address, and the named party who made contact. When the lead lands in your CRM — whether that's Salesforce, HubSpot, Follow Up Boss, or ServiceTitan — its consent trail arrives with it.

This matters because of how recording liability actually works. As compliance research makes clear, the engaging business remains legally accountable for consent notifications even when a vendor handles the calls — outsourcing doesn't outsource liability. And the stakes are steep: California carries $5,000 statutory damages per violation, meaning 100 improperly recorded calls could theoretically mean $500,000 in exposure.

Before any outbound contact, we also DNC-scrub every list. That protects you from the telemarketing layer of risk, where FTC Telemarketing Sales Rule requirements cover everything from prompt disclosures to two-year recordkeeping. Opt-outs are honored immediately and permanently across SMS, voice, and email.

Here's what attaches to every lead:

• The exact disclosure text the prospect received
• A timestamp documenting when consent occurred
• The IP address captured at the point of consent
• The named party who initiated contact

The result: your call recording disclosures start from a documented foundation rather than an assumption. When your agent says "this call will be recorded," you already know the contact was legitimately sourced, DNC-scrubbed, and consent-recorded. Compliance guidance emphasizes that a disclosure is part of a process — notice, consent, storage, retention — not a single sentence. Your process begins before the phone ever rings.

For dead lead reactivation, the same principle applies: we only target pre-existing, opted-in relationships, never cold lists. FCC one-to-one consent direction is built in from day one, so revived contacts come with the same documented foundation as fresh ones.

Compliance isn't a checkbox at the end — it's the starting point. If you want leads that arrive qualified, time-stamped, and consent-recorded, book a 15-minute qualification call. It's free, honest about fit, and commits you to nothing.