Does the disclosure need to be a specific legal phrase?

No — there's no single mandated legal phrase in most states. What matters is that the disclosure is clear, understandable, and delivered early enough that the caller has a real opportunity to know the call is being recorded before it continues. Plain language works better than legalistic phrasing, which can actually undermine the goal of clear notice.

Where in the call should the disclosure happen?

As early as possible — ideally before any hold music, menu navigation, or substantive conversation begins. A disclosure buried after several minutes of hold time or deep in an IVR menu is weaker evidence of compliant notice than one delivered in the first few seconds.

Can I use the same script for an AI voice receptionist as I would for a human greeting?

Yes — the disclosure language works the same regardless of who or what delivers it. Most AI voice receptionist platforms let you customize the opening greeting, so adding the disclosure line there is usually a simple configuration change rather than a technical limitation.

Do I need a different script for outbound calls versus inbound calls?

The core disclosure language is the same, but outbound calls typically need the disclosure delivered by the caller (your staff or system) at the very start of the call, since the person being called hasn't chosen to initiate contact and may need a moment to process the notice before the conversation continues.

Call Recording Disclosure Scripts: Exact Wording That Works

The safest all-purpose call recording disclosure is a short line delivered before hold music or menu options: “This call may be recorded for quality and training purposes” — it works for human staff, IVR greetings, and AI voice receptionists alike. Once you know whether your business needs one-party or two-party consent disclosure — covered in one-party vs. two-party consent states — this article gives exact, ready-to-use scripts for the most common local business call scenarios, building on the broader framework in our call recording compliance guide.

Key Takeaways

Plain, clear language works better than legalistic phrasing for both compliance and caller experience.
Disclosure should happen early in the call — before hold music or menu navigation, not after.
The same core script works across human staff, IVR systems, and AI voice receptionists with minor adjustments.
Outbound calls need disclosure delivered clearly at the very start, since the recipient didn’t initiate contact.
Most AI voice receptionist and IVR platforms support a customizable opening greeting where this fits naturally.

The Universal Baseline Script

For most local business scenarios, a version of this line satisfies disclosure requirements everywhere: “Thank you for calling [Business Name]. This call may be recorded for quality and training purposes.” It’s short, plain, and delivered before any further call handling — which is exactly what makes it effective as blanket-compliant language regardless of which state applies.

Script for Human-Answered Calls

Staff answering live can incorporate the disclosure directly into their standard greeting: “Thanks for calling [Business Name], this is [Name] — this call may be recorded for quality purposes. How can I help you today?” Keeping it attached to the existing greeting, rather than as a separate awkward pause, makes it feel natural rather than bureaucratic.

Script for IVR / Auto-Attendant Systems

An automated menu system should deliver the disclosure before presenting any options: “Thank you for calling [Business Name]. This call may be recorded for quality and training purposes. For sales, press 1. For support, press 2.” Placing it first, before the menu, ensures the caller hears it regardless of which option they ultimately choose.

Script for AI Voice Receptionists

AI voice receptionist platforms typically allow a fully customizable opening greeting, which is the natural place to include disclosure: “Hi, thanks for calling [Business Name], this is [AI assistant name] — this call may be recorded for quality and training. What can I help you with?” Keeping the tone conversational, matching the rest of the AI receptionist’s voice and pacing, avoids making the disclosure feel like a jarring legal insert. See our AI voice receptionist compliance checklist for other points in the call flow worth reviewing alongside this.

Script for Outbound Calls

Outbound calls need the disclosure delivered by the caller (your staff or automated system) immediately: “Hi, this is [Name] calling from [Business Name] — just a heads up, this call may be recorded for quality purposes. I’m calling about…” Leading with the disclosure before the reason for the call gives the recipient a genuine opportunity to be aware before the substantive conversation begins.

Common Mistakes in Disclosure Wording

A few patterns weaken an otherwise reasonable disclosure: burying it after a long hold message or deep in a menu tree, using overly legalistic phrasing that callers tune out or don’t fully process, and inconsistency — using the disclosure on some call lines or locations but not others. A consistent, simple, early disclosure across every call-handling system a business uses is more defensible and more effective than a technically correct but inconsistently applied one.

Testing Your Own Call Flow

The best way to confirm a disclosure is actually working as intended is to call the business’s own main line and every tracking or department number and listen for it firsthand, the way a real caller would experience it. This simple test — worth repeating any time a phone system, IVR, or AI voice receptionist platform is changed — catches gaps that are easy to miss when reviewing configuration settings on paper rather than hearing the actual call experience.

Adapting Scripts for Different Industries

Some industries carry extra context worth folding into the disclosure without making it longer. A medical or dental practice might pair the recording disclosure with a brief privacy note, since callers in these industries are often more attuned to privacy concerns: “This call may be recorded for quality and training purposes, and we take your privacy seriously.” A legal intake line might keep the disclosure especially plain and separate from any discussion of the caller’s matter, to avoid any appearance that the recording notice was mixed in with substantive advice. A restaurant or retail business taking a high volume of quick calls can keep the baseline script as-is, since brevity matters more than added context in high-call-volume, low-complexity scenarios.

What to Do After Implementing a Script

Once a compliant disclosure is live across every call-handling system — human lines, IVR, AI voice receptionist, call tracking numbers — document exactly what script is used where, and note the date it was implemented. This record is useful both for onboarding new staff or locations consistently and, if a compliance question ever does arise, as evidence the business had a deliberate, documented disclosure practice in place. Pair this with the broader review points in call recording compliance for local business to make sure disclosure is just one piece of a complete, defensible compliance posture rather than the only step taken.