Call recording consent prompt: scripts and IVR setup
Add a short consent line before you connect the call. Use these scripts and a one‑step IVR so you stay compliant without hurting answer rates.
Telecom engineering and support at CallFlow (ALERTSIO LLC)

You add a short call recording consent prompt before the call connects, then start recording only after consent. Use a 4–7 second announcement or a quick “press 1” IVR (a phone menu) so callers move on fast. By the end of this guide, you’ll have a working consent step and two routes (recorded and not recorded). Expect 20–30 minutes including testing.
Start with the shortest working consent
One-party consent means only one person on the call agrees to the recording (often you). All-party (also called two-party) consent means everyone on the call must agree. Laws vary by US state and by country.
A safe default is a 4–7 second disclosure before you connect the caller. If you serve all-party jurisdictions, get explicit consent (for example, press 1 in an IVR) before recording starts. If the caller doesn’t consent, route them to a path where recording is off.
In the US, check your callers’ states and choose your method accordingly. See our state-by-state overview: Business call recording by state. Outside the US (India, the Philippines, Thailand, Bangladesh, Pakistan), rules differ. If you’re not sure, treat calls as all-party and use explicit consent.
Announcement-only (implied consent by staying on the line) is fastest. It fits one-party rules and tends to keep completion rates high because the call just moves on. Press 1 (explicit consent) adds a small drop-off but gives you a wider compliance margin in all-party states or countries. If you serve mixed geographies, use caller-state routing (rules that route by the caller’s number state) when possible; otherwise, use explicit consent everywhere.
Scripts you can copy (announcement and IVR)
Use clear, short lines in one voice. Keep each under 20 words so you stay in the 4–7 second range.
- Business announcement (one-party): “This call may be recorded for quality. By continuing, you consent.”
- All-party IVR: “Press 1 to consent to call recording and continue. Press 2 to continue without recording.”
- Buyer/agency (pay-per-call): “This call may be recorded for quality. By continuing, you consent. No company names will be shared.”
- Healthcare/financial: “For quality, this call may be recorded. By continuing, you consent. Do not share card or PIN.”
- Simple non-recorded option: “To continue without recording, press 2.”
- Multi-language opener (English first): “This call may be recorded. For Tagalog, press 2.” (route to a Tagalog IVR)
- Multi-language opener (Hindi first): “Yeh call record ho sakta hai. For English, press 2.”
When you add a language branch, send the caller to a language IVR with the same consent options. See multi-language IVR menus for a quick pattern. Keep wording neutral. Avoid legal terms that slow callers down.
Where the consent step sits in your call flow
Put the consent line as the first step after your business number, before any queue (a hold line with music) or ring group (several phones that ring together). That way every caller hears the same short notice, and you can branch based on consent across all routes.
Start recording only after consent. The prompt itself should not be recorded. Route non-consent callers to voicemail or to an unrecorded path. Keep recorded and non-recorded traffic on separate routes. Place consented calls into a number or campaign where recording is on, and send non-consent to one where recording is off (or to voicemail).
Set the ring timer (how long a phone rings before the next step) on the agent legs (each destination phone) to 15–25 seconds. This helps avoid the agent’s personal voicemail grabbing the call. If you use simultaneous ring (ring several phones at once), keep it to 2–3 targets. Too many legs can cause voicemail races.
For a press 1 menu, allow one retry. Set the DTMF timeout (keypad tone input wait) to 3–5 seconds. If there’s no input after the retry, send the caller to the non-recorded path.
Illustrative example: one-digit consent then route
A dental office takes daytime calls to two mobiles. After hours, calls go to voicemail. The consent prompt is 5 seconds. The DTMF timeout is 3 seconds, with one retry. When consented, each mobile rings for 20 seconds, then falls to voicemail if no one answers. Voicemail is not recorded.
This example keeps the consent experience tight and predictable. You can swap the ring strategy to priority (try A first, then B) or simultaneous ring (ring several phones at once) if needed, and the consent logic still holds.
Build your call recording consent prompt step by step (in any call routing platform)
Follow these steps. You can do them on most routing systems in under 30 minutes.
Write and record a clean 4–7 second prompt. Use a calm voice. Normalize the audio level so it isn’t louder than your agents.
Create an IVR (phone menu) with two options: consent (1) and no-consent (2 or timeout). Set the DTMF timeout to 3 seconds and allow one retry.
Point the consent path to your ring strategy. Use priority (try A, then B) or simultaneous ring (ring several phones at once) with 15–25 second ring timers per target.
Point the no-consent path to voicemail or to a path where recording is off. If your platform controls recording at the number or campaign level, send consented calls to a recorded number/campaign and non-consent to an unrecorded one.
Place consented calls into a campaign or number where recording is on, and send non-consent to one where recording is off.
Test with two phones. Confirm DTMF works, the correct branch is taken, and recordings start only after consent. Spot-check that the prompt itself is not in the file.
Check live logs for branch selection and results (answer or voicemail). Keep screenshots of settings for your QA notes.
With CallFlow, you can build this with IVR menus, call recording, queues, voicemail, and routing rules in one place without adding a second number. For tone and pacing tips while you record your lines, see IVR prompt best practices. For a structured test run, use the test call forwarding checklist.
Keep answer rates high while staying compliant
Keep the prompt short, in one voice, and free of legalese. Do not stack menus. If you need language options, offer one shortcut (for example, “For Tagalog, press 2”) and move the caller straight to a language IVR with the same two consent choices.
If you use simultaneous ring, cap it to 2–3 targets and 20 seconds. This cuts the chance a personal voicemail grabs the call. If a mobile voicemail still takes calls early, drop that target or extend the ring on another leg so a live person answers first.
For pay-per-call, add these after the consent branch: duplicate-caller rules (block repeat callers for a set time) and per-target windows (hours each buyer takes calls). Then apply buyer routing (rules that decide which buyer gets the call). That way only consented calls can be billable or delivered. If you verify leads by recording, keep those recordings only on the consented path. See ideas in call recording for lead verification.
You can’t record only one side of a two-party call in most routing setups. To keep buyers off recordings, deliver those calls on an unrecorded route. If you need recordings for agent QA, record your in-house support route, and deliver buyer leads on a separate unrecorded campaign or number. Buyers can still see call metadata in their portal without audio.
Run weekly QA. Pick 10 calls at random. Confirm the prompt plays, DTMF is captured, recordings start after consent, and non-consent calls are not recorded. Fix any outliers right away.
Country notes: outside the US, treat calls as all-party if you’re unsure. Use explicit consent and a short non-recorded fallback. Update your scripts in the local language where you have volume.
Set it up now and verify
Draft your 4–7 second line, build the two-branch IVR, and point your recorded path only after consent. Make two test calls from different phones. Check logs and recordings to confirm timing and branches.
You can set this up in CallFlow today. Create an account at CallFlow or contact us if you want help reviewing the flow.
Frequently asked questions
Do I need explicit press-1 consent, or is staying on the line enough?
Staying on the line can count as implied consent in one‑party jurisdictions and keeps drop‑off low. Explicit press‑1 consent gives clearer proof and is safer for callers from all‑party jurisdictions, but it adds a small extra step. If you serve mixed states, either route callers by state to different consent flows or use press‑1 everywhere to be conservative.
Which US states require all‑party consent to record business calls?
Can I collect consent in Spanish or another language first?
Yes. Offer a short language selection first (for example, “For Spanish, press 2”), then play the same consent options in that language. Route each language branch to identical consent handling: press‑1 for consent, press‑2 or timeout for no‑consent. Keep each prompt short and test DTMF and recordings in every language branch to make sure consent is captured cleanly.
Should I re‑prompt existing customers on every call?
If you already have a clear, dated recording consent tied to the customer, you don’t have to re‑prompt every call. If the consent status is unknown, from a different campaign, or the caller’s state requires all‑party consent, prompt each time. For simplicity, many businesses run the quick consent IVR for every inbound call so the routing decision is consistent and easy to audit.
How long should the consent prompt be to avoid drop‑offs?
Keep the disclosure to about 4–7 seconds and a single short sentence so callers move on quickly. If you use press‑1, add a 3–5 second DTMF wait with one retry. Short prompts reduce abandonment; language options or extra legal wording increase drop‑offs, so exclude unnecessary phrasing and test live call completion rates after changes.
Can I keep buyers off the recording while still recording the agent’s side?
You can’t reliably record only one audio leg in typical routing setups. The safer approach is route separation: send buyer deliveries down an unrecorded campaign or number, and send internal agent calls or QA lines to a separate recorded campaign. Use IVR branching so consented QA calls flow to the recorded path while buyer leads go to the unrecorded path. With CallFlow you can keep recordings and unrecorded deliveries on different campaigns and still share call metadata with buyers.
From the team
CallFlow Engineering TeamTelecom engineering and support at CallFlow (ALERTSIO LLC)
The engineers and support staff who build and operate CallFlow's call-routing platform. We write from what we see running inbound routing for pay-per-call marketers, agencies and small businesses every day: routing rules, carrier behaviour, spam flags, and the configuration mistakes that quietly cost calls.
Ready to get started with CallFlow?
No subscription. Transparent usage billing. Per-number spam scores. Built for scale.
Create Free Account →