What to say when a call is being recorded?

Why a Sloppy Recording Disclosure Can Cost You Millions

A single sentence at the start of a phone call — or its absence — can be the difference between a compliant sales operation and a seven-figure legal settlement. Most sales teams recording calls daily have never read the rules governing those recordings.

The stakes are not theoretical. In 2019, Tiger Natural Gas settled a class action for $3.7 million after allegedly recording conversations with more than 27,000 potential customers without complying with California's two-party consent law, as documented in Vonage's compliance analysis. One disclosure script, delivered consistently, could have prevented the entire case.

Regulators enforce these rules at the individual-offense level. According to the Reporters Committee for Freedom of the Press, FCC fines for recording or broadcasting calls without prior notice range from $4,000 to $51,827 per offense. At scale, a sales team making hundreds of recorded calls a week multiplies that exposure fast.

Timing matters as much as the disclosure itself. The FCC upheld a $4,000 fine against a radio station where the host revealed recording intent only mid-call — because mid-call notification is legally too late. Notice must be clear, delivered before any substantive conversation begins, and actually received by all parties.

For lead buyers and outbound sales teams, the compliance surface is wider than most realize:

• Consent rules vary by state — roughly 11 to 14 U.S. states require all-party consent, including California, Florida, Pennsylvania, and Washington.
• Interstate calls demand the stricter standard; the practical guidance is to assume the toughest applicable law governs.
• The FTC's Telemarketing Sales Rule requires express informed consent and 24 months of retained authorization records.
• Beep tones are authorized in California but not in Florida, Maryland, Massachusetts, or Pennsylvania — verbal disclosure is the safer default.

This is why consent infrastructure belongs at the lead level, not the afterthought level. Every lead GrowthPros delivers carries a consent record — disclosure text, timestamp, IP address, and the named contacting party — so buyers inherit a documented trail rather than a compliance gamble. If your team records calls without knowing which consent standard applies in each party's state, you are carrying Tiger Natural Gas–style risk on every dial.

The good news: the fix is a script, a system, and a log. The rest of this article covers exactly what that script should say.

The Exact Disclosure Script: What to Say and When to Say It

A disclosure script is only effective if it hits three elements: notification at the start of the call, a stated purpose, and a clear explanation of how the recording will be used and stored. Miss any one of them, and the recording may be worth less than nothing — the Tiger Natural Gas class action, alleging illegal recordings of more than 27,000 potential customers, settled for $3.7 million over violations of California's two-party consent law.

Timing comes first. Notice must be clear, delivered before substantive conversation begins, and actually received by all parties — compliance guidance is blunt that mid-call notification is too late. The FCC upheld a $4,000 fine against a radio station whose host disclosed broadcast intent only halfway through a call, so regulators mean it.

Content comes second. Expert guidance recommends stating the purpose of the recording — quality assurance, training, regulatory compliance — along with how the recorded information will be used, stored, and protected. Be specific and honest: Canada's PIPEDA framework warns organizations not to claim recordings are for quality assurance if they will actually be used for other purposes.

Here is a sample script that covers all three elements:

• Notification: "This call may be recorded."
• Purpose: "We record calls for quality assurance and training purposes."
• Use and objection: "If you prefer not to be recorded, let us know and we can accommodate you through alternative channels."

Why verbal disclosure instead of a beep tone? Beep tones are authorized in California, but verbal disclosure is the safer choice across jurisdictions, since states like Florida, Maryland, Massachusetts, and Pennsylvania have no statute authorizing beep tones as standalone consent mechanisms. If your calls cross state lines, assume the stricter (all-party) standard applies — a best practice recommended for any multi-jurisdiction operation.

In most jurisdictions, continued participation after disclosure implies consent. If the caller objects, offer meaningful alternatives — a non-recorded line, an in-person visit, written correspondence, or an online transaction. And record the caller's verbal consent explicitly; it is a best practice that strengthens your position in stricter-consent states.

Finally, embed the disclosure in your systems rather than relying on agent memory: IVR prompts for inbound calls, locked scripts for outbound. Maintain consent records — timestamps, disclosure text, and the named contacting party — for at least 24 months, as the FTC's Telemarketing Sales Rule requires for verifiable authorizations. This is how we approach it at GrowthPros: every lead we deliver carries a consent record with its disclosure text and timestamp attached, so the compliance trail travels with the lead into your CRM.

One-Party vs. All-Party Consent: The Jurisdiction Trap

The most expensive recording mistake a sales team can make isn't what it says — it's where the other person is standing when it says it. Call recording consent law in the United States splits into two incompatible models, and if your team doesn't know which one governs the call, the disclosure script doesn't matter.

Under one-party consent, only one participant — typically the recorder — needs to know the call is being recorded. This standard applies federally and in most U.S. states, according to state-by-state legal analysis. But roughly 11 to 14 states take the opposite approach: all-party consent, where every participant must agree before the record button is defensible. California, Florida, Pennsylvania, and Washington top that list, and sources differ slightly on the count — Otter.ai identifies 13 all-party states, while the Reporters Committee for Freedom of the Press counts about 11, with four states splitting rules by conversation type.

The stakes are not theoretical. Tiger Natural Gas settled a class action for $3.7 million after allegedly recording conversations with more than 27,000 potential customers in violation of California's two-party consent law, as documented in Vonage's compliance analysis. California also makes evidence obtained in violation inadmissible in any proceeding — so a recording made improperly can be worthless even if no fine follows.

International borders add another layer:

• Canada: PIPEDA requires informing callers at the start and stating purposes clearly; implied consent applies if the caller proceeds, per the Office of the Privacy Commissioner's guidance.
• EU: GDPR demands consent from all parties plus a lawful basis for recording, per consent disclosure guidance.
• Germany: Recording without consent is criminalized under §201 of its Criminal Code.
• Australia: Organizations must tell the other party at the beginning so they can end the call or request a non-recorded line.

The practical problem is geography: on any interstate or international call, you often don't know which state or country the other party is in. A rep in Texas — a one-party state — dialing a prospect in Florida breaks Florida law the moment the recorder runs without consent. The RCFP's advice for cross-state calls is blunt: err on the side of caution and assume the stricter state law applies.

That's the safest operating rule for any distributed team: treat every call as an all-party consent call. Deliver notice at the outset, state the purpose, capture consent explicitly, and log it. GrowthPros builds this standard into every lead it delivers — each consent record carries the disclosure text, timestamp, IP address, and named contacting party — precisely because interstate sales teams can't afford to guess which jurisdiction governs any given dial.

What to Do When a Caller Objects to Being Recorded

"Sure, no problem — let me turn that off." That simple sentence might be the most underrated compliance move in your entire call script. What you do in the next ten seconds after a caller objects matters just as much as the disclosure you gave at the start of the call.

The Office of the Privacy Commissioner of Canada, under PIPEDA guidance on call recording, is explicit: if the caller objects, the organization should provide meaningful alternatives. Those alternatives might involve not taping the call, visiting a retail outlet, writing a letter, or conducting the transaction over the Internet. An objection can't be treated as a dead end — it has to be treated as a routing decision.

Australia takes a similar position, requiring organizations to tell the other party at the beginning of the call so they can end the call or request a non-recorded line, per the same international comparison of recording laws. In practice, that means your agents need real options at their fingertips, not an apology and a hang-up.

A workable alternatives menu looks like this:

• A genuinely non-recorded line the agent can warm-transfer to immediately
• An in-person or retail appointment for the transaction
• Written correspondence by mail or secure email
• An online self-service channel to complete the transaction

The stakes of getting this wrong are not theoretical. A class action against Tiger Natural Gas over more than 27,000 improperly recorded calls settled for $3.7 million under California's two-party consent law. And the FCC has upheld fines where notice came too late — including a $4,000 penalty against a radio station host who disclosed broadcast intent only mid-call, according to the Reporters Committee for Freedom of the Press. Notably, that same FCC record shows a fine reduced from $4,000 to $2,000 where the station stopped recording after the objection — proof that honoring an objection quickly actually mitigates risk.

There's a second, subtler trap: purpose honesty. PIPEDA guidance is direct — an organization should not state that it is recording for quality assurance purposes if the recording will actually be used for other purposes. If the audio feeds marketing, lead scoring, or AI training, say so. Your stated purpose must match your actual use.

At GrowthPros, this is why every lead we deliver carries a consent trail — disclosure text, timestamp, and the named contacting party — so clients can verify that what was said on the call matches what the data will be used for. Building the alternative into your script costs nothing. Building the settlement into your budget costs millions.

Build a Consent Trail: Scripts, Systems, and Records That Hold Up

A disclosure that lives only in a policy document protects no one. What holds up — in a dispute, an audit, or a courtroom — is a consent trail: the right words, delivered by the right system, with proof of delivery you can actually produce.

Start by embedding the disclosure so it can't be skipped. For inbound calls, that means an IVR announcement before the caller reaches a human; for outbound, a locked script the agent cannot deviate from. Otter.ai's guidance is blunt: notice must be clear, given before substantive conversation begins, and actually received by all parties — mid-call notification is too late. The FCC once upheld a $4,000 fine against a radio host who disclosed recording intent only partway through a call, per the Reporters Committee's recording guide.

Verbal consent is the gold standard. Implied consent — the caller staying on the line after the beep — works in many jurisdictions, but the RCFP advises that recording the subject's explicit verbal consent is a best practice. A simple "Do I have your permission to record?" captured at the top of the call removes ambiguity later.

Then keep the receipts. The FTC's Telemarketing Sales Rule requires express informed consent in every telemarketing transaction and mandates maintaining records of verifiable authorizations for 24 months. That means every call record should carry:

• A timestamp showing when the disclosure played relative to the conversation
• The exact version of the disclosure script or IVR message used
• The consenting party's identifier and, for digital leads, their IP address
• The named contacting party or campaign source

This is why the stakes are real: Tiger Natural Gas settled for $3.7 million over more than 27,000 illegally recorded calls under California's two-party consent law. A metadata trail is what separates a defensible operation from a class-action target.

GrowthPros builds this discipline into every lead it delivers: each one arrives DNC-scrubbed, with its consent record — disclosure text, timestamp, IP, and the named contacting party — attached before it ever reaches a client's CRM. The same logic applies to your own calls: systematize the disclosure, capture the consent, and store the proof. If you can't produce the record on demand, assume you don't have consent at all.