Dialpad call recording and AI summaries need a notice before recording starts: a greeting telling every caller the call may be recorded or transcribed by you and your service providers, plus privacy wording explaining the AI summaries. All-party consent states and UK and EU data-protection rules make that notice essential, and Dialpad requires it on recorded inbound lines.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe practical rule is to give one clear notice on every call, in both directions, rather than trying to work out each caller's law. Callers' area codes, mobile numbers and travel make location guesswork unreliable, and a few seconds of greeting cost far less than defending a recording made without consent. This page is general information, not legal advice; a lawyer who knows your sector should check your final wording.
Which laws decide whether you need consent to record a call?
Call recording consent depends on where the people on the call are: US federal law needs one party's consent, some US states need everyone's, and UK and EU rules require clear notice.
The US: one-party federal law, all-party states
Federal law (18 U.S.C. 2511(2)(d)) makes it lawful for a person who is a party to a call, or who has one party's prior consent, to record it, unless the recording is for a criminal or tortious purpose. That is the "one-party consent" baseline. A group of states go further and require every party's consent, or at least everyone's knowledge. These are the ones checked on each state's own statute for this page:
| State | Statute | What it requires, in short |
|---|---|---|
| California | Penal Code 632 | Consent of all parties to record a confidential communication; fines up to $2,500 per violation |
| Connecticut | General Statutes 52-570d | For phone calls: all parties' consent in writing or at the start of the recording, a recorded verbal notice at the start, or an automatic warning tone about every 15 seconds |
| Florida | Statutes 934.03 | Lawful when all parties have given prior consent |
| Illinois | 720 ILCS 5/14-2 | No surreptitious recording of a private conversation without the consent of all other parties |
| Maryland | Courts and Judicial Proceedings 10-402 | Lawful for a party where all parties have given prior consent |
| Massachusetts | General Laws chapter 272, section 99 | No secret recording without prior authority from all parties |
| Montana | 45-8-213 | No hidden recording without the knowledge of all parties; a warning by one person lets either party record |
| New Hampshire | RSA 570-A:2 | No interception without the consent of all parties |
| Washington | RCW 9.73.030 | Consent of all participants; an announcement to everyone counts as consent, and the announcement must itself be recorded |
Dialpad's own convenience list of all-party consent states adds Delaware, Michigan, Nevada and Pennsylvania, and Dialpad says some states have conflicting or unclear laws. Its contact centre recording article counts 11 two-party states while its area-code list covers 13, which is a good illustration of why no list should be your only safeguard. The guide to what an AI scribe consent form should say under US recording laws covers the same state split from a clinic's side.
The UK: tell callers you are recording and why
The ICO's guidance on monitoring workers says you must tell callers that you are recording the call and why, that a recorded message is good practice, and that where one is not possible staff must tell callers that calls may be recorded. The rest of the privacy information, such as how long you keep recordings and who sees them, can be given another way, for example by email or a link to your website. The same guidance says it is not usually proportionate to record the content of every call in all cases, so have a reason: evidence of transactions, training or quality.
Separately, the Investigatory Powers (Interception by Businesses etc. for Monitoring and Record-keeping Purposes) Regulations 2018 let a business record calls on its own system for set purposes, such as establishing facts or checking standards, only if it has made all reasonable efforts to inform every person who may use the system that calls may be intercepted. For outbound sales calls, the PECR rules on live marketing calls add their own duties: check numbers against the TPS and CTPS registers and do not call anyone who has objected.
The EU: confidentiality of communications plus the GDPR
Article 5(1) of the ePrivacy Directive (2002/58/EC) requires member states to prohibit listening, tapping, storage or other interception of communications by anyone other than the users without the consent of the users concerned. Article 5(2) leaves room for legally authorised recording in the course of lawful business practice to provide evidence of a commercial transaction, which each country implements in its own law. On top of that, data-protection law such as the GDPR means callers must be told what you do with recordings and summaries. If you have customers in the EU, take local advice on the exact basis you rely on.
What does Dialpad require in a recording greeting?
A Dialpad recording greeting must tell callers two things: that the call may be recorded or transcribed, and that a third party such as your service providers may do the recording or transcription.
Dialpad standardised inbound greetings for Main Lines, Departments and Contact Centers, and says greetings are mandatory for recorded or transcribed calls; if you have not set one, it applies a default. An exact script is not required. Dialpad's own examples, from its article on understanding call recording and transcription:
| Greeting | Accepted? | Why |
|---|---|---|
| "This call may be recorded or transcribed by us and our service providers for quality assurance." | Yes | Mentions recording, transcription and providers |
| "Calls are recorded by our service providers to..." | Yes | Names recording and a third party |
| "This call may be recorded for quality purposes." | No | No transcription, no service providers |
| "We might record this call for training purposes." | No | Same gap |
Dialpad's standard greeting for callers in two-party states reads: "Your call may be recorded or transcribed by us and our service providers for system and quality training." For transcribe-only calls it says the call "may be transcribed" instead.
To set one, go to Admin Settings, open the Contact Center, Department or Main Line, select Advanced Settings, then Automatic Call Recording and Transcription, then Call recording greeting, and either pick a default message or choose Record greeting to write your own with the text-to-speech tool. A greeting built with that tool and the required language is verified automatically and shows a Verified badge; once your welcome greeting is verified you can choose "No Message" to drop the second disclosure that would otherwise play when an agent answers. An uploaded MP3 that contains the disclosure stays unverified until Dialpad's Customer Care team reviews it, and swapping a verified greeting for a new unverified file immediately reverts the line to Dialpad's default disclosure.
Where does Dialpad play the greeting, and where doesn't it?
Dialpad plays the recording greeting on inbound calls to recorded Main Lines, Departments, Contact Centers and Coaching Teams, but not for office-wide automatic recording or a user's own Record button.
| How the call is recorded | Greeting plays? | What you must do |
|---|---|---|
| Inbound to a recorded Main Line, Department or Contact Center | Yes, default or your own | Check the wording names recording, transcription and providers |
| Office-wide automatic recording (Office Settings, Office-Wide Settings, Making Calls) | No; Dialpad warns callers will not hear one | Agents tell every caller verbally, at the start |
| Recording your own calls with the Record button | No greeting is described in Dialpad's recording guide | Say it before you press Record |
| Outbound calls | Not covered by the inbound standard; a contact centre can set a separate outbound greeting | Use an agent script on every outbound call |
| Calls matching an exception list | Recording skipped, or only your agent's side recorded | Decide which you want per list |
The two-party consent setting deserves care. Under Advanced Settings, Automatic Call Recording & Transcription, Inbound Calls, the "Call Greeting Played" section offers All calls (the default) or All except One-Party Consent. The second option checks the caller's US area code against Dialpad's list and skips the greeting for one-party states. Blocked, unknown and non-US numbers are treated as two-party, so they still hear it, and if a transfer or merge adds a leg from a two-party state, the greeting plays for that leg. Dialpad's two-party consent greeting article notes it only applies to US inbound calls and that each line can be set separately.
Area codes describe where a number was issued, not where the caller is standing. A customer with a Florida mobile number calling from a holiday let elsewhere still triggers the one-party logic of the area code. Leaving the setting on All calls removes that guesswork for a few seconds per call.
Do AI call summaries need their own notice?
AI call summaries in Dialpad need a notice that providers transcribe and process the call, which a compliant greeting gives, plus privacy wording on what summaries are for and who sees them.
Dialpad AI Recaps use Dialpad GPT to produce an AI call summary, the call's outcome, its purpose and AI action items, ready seconds after the call. They depend on Dialpad AI being on, which an admin must enable at company level first (Company Settings, AI Settings, General AI Settings, "Allow AI to be used company-wide"), then per office (Office, AI Settings, "Allow AI to be used office-wide") and per shared line. Office and line settings also decide whether AI starts automatically on every call, whether the live transcript opens on its own, and whether users can start and stop AI during calls. Individuals switch it on under Your Settings, AI Settings, "Allow AI to be used for your personal calls and meetings".
One setting changes what your notice should say. Admins choose whether Dialpad AI may improve based on your conversations ("Allow Dialpad AI features to improve based on my conversations" under the company's AI settings); Dialpad says training is optional, that AI features keep working with it off, and that a company with a Business Associate Agreement cannot turn it on. If you allow it, your privacy notice should say recordings may help train a provider's models; if not, say they do not.
The EU AI Act's Article 50(1) is sometimes quoted here, but it puts a duty on providers of AI systems that interact directly with people, such as an AI agent answering the phone, to make sure people know they are dealing with AI. A summary written after a call between two people is a different job; if you also run an AI voice agent, that agent needs its own disclosure. For how to use the summaries once you have them, see logging AI call summaries in your CRM.
Before a recap goes into a customer record, check it. An illustrative recap from a removals quote call:
Summary: Customer is moving a 3-bed house on 14 March and wants a
full packing service. Agent quoted $3,200 including insurance.
Outcome: Quote given, follow-up needed.
Action items: Email written quote; book a video survey.
What to fix: the agent gave a range "from $2,900 to $3,400 depending on the survey", not a fixed $3,200, so correct the figure before anyone relies on it; "including insurance" was the customer's question, not the agent's answer; and the customer's mention of a medical condition affecting the move date should not be in a shared summary at all. Treat recaps as drafts that a person approves, which the checks in reviewing AI call transcripts for quality and compliance make routine.
Consent scripts you can adapt
Use these as starting points and have your final versions checked. Replace the bracketed parts.
1. Inbound greeting for every caller (fits Dialpad's rules and the strictest states):
Thanks for calling [business name]. This call may be recorded and
transcribed by us and our service providers, and we use AI to write
a short summary for our records. Our privacy notice at
[web address] explains how we use and keep recordings. If you'd
rather not be recorded, tell the person who answers.
2. Outbound call opening, said before the conversation starts:
Hi [first name], it's [your name] from [business name]. Before we
start, this call is recorded and transcribed by us and our service
providers so we have an accurate note of what we agree. Is that
all right with you?
3. Office-wide recording, where no greeting plays:
Just so you know, our calls are recorded and transcribed for our
records and training. Are you happy to carry on?
4. Before taking card details (pause first, then say it):
I've paused the recording while you read me the card number. I'll
let you know when it's back on.
5. Privacy notice paragraph for your website:
Call recordings and AI summaries. We record and transcribe calls to
and from [business name] using our telephone provider, Dialpad, to
keep an accurate record of quotes and bookings and to train our staff.
An AI tool produces a short written summary of each call, which a
member of our team checks before it is added to your customer record.
We keep recordings for [period] and summaries for [period]. Our
provider [does / does not] use call data to improve its AI. You can
ask us not to record a call, or ask for a copy of a recording, by
contacting [email address].
Script 2 asks a question on purpose. Dialpad's guide says a caller who continues after hearing a recording notice is consenting, but on an outbound call you started, a clear yes is easier to show later than silence.
The pre-recording checklist
Work through this before switching on recording or AI on any Dialpad line. Each item says why it matters and how to check it.
Decide
- Why you record. Quotes, disputes, training or compliance. The ICO expects a reason, and the reason shapes your retention period. Check: one sentence per line in your records.
- Which lines record. Main Line, each Department, Contact Centers, Coaching Teams, office-wide. Check: list every line and its setting.
- Whether AI runs automatically. Auto-start on every call, or users start it. Check: Office and line AI settings.
- AI training on or off. Check: the company AI training setting matches what your privacy notice says.
Announce
- Greeting wording. Recording, transcription and service providers named. Check: listen to it from an outside phone.
- Greeting coverage. All calls, not only two-party states. Check: Call Greeting Played set to All calls on every recorded line.
- Outbound script. Every outbound recorded call opens with script 2. Check: listen to five outbound recordings a month.
- Office-wide gap. If office-wide recording is on, agents say script 3. Check: spot-listen to the first ten seconds of recordings.
Explain
- Privacy notice. Recordings, AI summaries, retention, sharing and how to object. Check: the greeting's web address works on a phone.
- Staff notice. Staff know calls are recorded and why, which the 2018 regulations and ICO guidance both expect. Check: written into your staff handbook.
Control
- Pausing. Pause Recordings allowed for card payments and sensitive moments. Check: test a pause on a call.
- Access. Who can hear recordings: admins assigned to a shared line, coaches, agents for their own calls. Check: review permissions quarterly.
- Exceptions. Any exception list entries in E.164 format (for example +1415), and whether matching calls are skipped or agent-side only. Check: test-call from a listed area code if you can.
- Deletion. When a user deletes a recording it stays playable from Conversation History for up to 24 hours before it is fully deleted. Check: your retention schedule allows for that.
If keeping that line-by-line audit of greetings, settings and test calls in a spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
Worked example: a removals firm with callers in several states
An illustrative removals firm with six Dialpad users takes quote calls from people moving between states, plus a few enquiries from overseas customers relocating. It wants recordings to settle disputes about what was quoted, and AI Recaps so quotes reach the CRM without retyping.
| Line | Calls a month | Setting chosen | Notice |
|---|---|---|---|
| Main Line | 300 inbound | Automatic recording and transcription, inbound | Script 1 as a verified text-to-speech greeting; All calls |
| Quotes department | 120 inbound, 90 outbound | Recording both directions; AI auto-start on | Greeting inbound; script 2 outbound |
| Crew mobiles | Varies | No recording | None needed |
| Office-wide recording | Not used | Off | Avoids the no-greeting gap |
A quick sum on the greeting: script 1 runs about 14 seconds. Across 420 inbound calls a month, callers spend roughly 98 minutes listening to it. Switching to All except One-Party Consent might save some of that, but most of the firm's moves start or end in California, Florida or Washington, all-party consent states, and a customer moving between states can be in either one when they call. The firm keeps All calls.
The realistic failure came on day one: an office manager had switched on office-wide automatic recording months earlier to settle a delivery dispute and forgotten it. Those calls played no greeting at all, even though the Main Line now had a proper one, because office-wide recording does not play one. The fix was to switch office-wide recording off and rely on line-level recording with greetings, and to add "office-wide recording off" to the quarterly check.
If you want help fitting recording notices and AI summaries into how your phones already run, I offer one-to-one AI consultations for small businesses.
How long should you keep recordings and AI recaps?
Keep Dialpad recordings and AI recaps only as long as the reason for recording lasts; set a period for each type of call, state it in your privacy notice and delete on schedule.
The ICO's guidance ties call recording to a purpose, and the retention period follows from the purpose: a recording kept to settle quote disputes is useful until a dispute is no longer possible, while one kept for training is useful until it has been used. Write the period down per call type rather than keeping everything "just in case", because every extra month is more personal data to protect and to hand over if asked.
Dialpad itself adds three things to plan around. Recordings live in each user's inbox under the Recordings tab and in Conversation History, and can be downloaded as MP3 files, so copies can spread to laptops. Recordings can also be backed up to Google Drive, which is a second place your schedule has to cover. And when a user deletes a recording, it can still be played from Conversation History for up to 24 hours before it is fully deleted. AI recaps copied into your CRM follow the CRM's retention, not Dialpad's.
A filled-in schedule from the illustrative removals firm:
| Item | Kept for | Reason the firm chose | Where copies live |
|---|---|---|---|
| Quote call recordings | 12 months after the move date | Its terms give customers that long to raise a claim | Dialpad only; downloads banned |
| Complaint call recordings | Until the complaint closes, plus 6 months | Evidence if the complaint is reopened | Dialpad plus the complaint file |
| Training examples | 6 months, then deleted | Long enough for one round of new-starter training | Shared training folder |
| AI recaps (checked) | As long as the customer record | They are the record of what was quoted | CRM |
| Unchecked AI recaps | Not kept outside Dialpad | Unverified summaries should not become the record | Dialpad only |
The periods are the firm's own choices, not legal minimums; yours should come from your terms, your sector's rules and your accountant's or lawyer's advice. Whatever you pick, put the same numbers in script 5's privacy paragraph so the notice and the practice agree.
What should happen when a caller says no?
When a caller objects to recording, stop recording or offer another way to continue; Dialpad supports pausing recordings and recording only your agent's side, and both choices should be logged.
- Pause if you can. Contact Center admins can allow agents to stop and restart recordings with Pause Recordings; company-level recordings pause too. Main Line and Department settings also let you allow the operator to pause.
- Turn off AI for the call. If users are allowed to start and stop AI during calls, stop it so no transcript or recap is produced.
- Offer email. Some callers would rather have the quote in writing anyway.
- Record the objection. A note on the contact record stops the next colleague recording them without asking.
- Never resume silently. If recording restarts, say so, as in script 4.
For a whole group of callers who should not be recorded, such as a sector where you have agreed not to, an exception list on the line can skip recording for their numbers or record only your agent's side, which Dialpad says can still help with quality control and disputes.
Mistakes that leave recordings without proper notice
- Office-wide recording left on. No greeting plays; agents must say it every time.
- An old greeting that only says "recorded". Dialpad now expects transcription and service providers to be mentioned; an old file may be replaced by the default disclosure.
- Outbound calls with no script. The inbound greeting does nothing for calls you make.
- Trusting area codes. Mobile numbers travel; the strictest-state approach is simpler.
- Recording card numbers. Pause before payment details are read out.
- A privacy notice that says nothing about AI. Callers hear "transcribed" but cannot find out what happens to the summary.
- Announcement not captured. Washington's statute treats an announcement as consent only if the announcement itself is recorded, so start recording before the greeting or script, not after.
For a sector view of the same questions, whether AI call summaries are safe for law firms on Dialpad covers confidentiality, and what a small business must do under the GDPR when using AI tools covers the privacy-notice side in more depth.
Dialpad recording consent: quick answers
Does Dialpad announce call recording automatically?
Only on some lines. Inbound calls to a Main Line, Department or Contact Center with recording or transcription on play a compliance greeting, and Dialpad applies a default one if you set none. Office-wide automatic recording plays no greeting, and recording your own calls with the Record button relies on you, so staff must tell callers themselves.
Can I skip the greeting for callers in one-party consent states?
Dialpad lets you, but think twice. The All except One-Party Consent option skips the greeting for US inbound callers whose area code is in a one-party state, using Dialpad's own list. Area codes do not prove where a mobile caller is, so playing it on all calls is the safer default.
Do I need consent to use Dialpad AI Recaps?
You need a notice. Dialpad's greeting rules already require mentioning transcription by service providers, and data-protection law such as the GDPR expects you to explain what happens to the summaries. Put the AI summary purpose, retention and sharing in your privacy notice and point callers to it.
Can I write my own Dialpad recording greeting?
Yes, as long as it says the call may be recorded or transcribed and that a third party, such as your service providers, may do it. Greetings created with Dialpad's text-to-speech tool are verified automatically; an uploaded MP3 waits for manual review before the extra disclosure can be switched off.
What if a caller does not want to be recorded?
Stop recording or offer another route. Contact Center admins can let agents pause recordings, and exception lists can record only your agent's side of matching calls. If neither suits, offer to continue by email, note the objection on the contact record, and never restart recording without telling the caller.
Further reads
- Dialpad Connect vs Support vs Sell: Which Does Your Team Need? — Which Dialpad product your team needs before you set recording rules.
- How Much Does Dialpad Cost Per Month for a Five-Person Team? — What Dialpad costs a five-person team each month.
- Which Dialpad Plan Syncs With Salesforce or HubSpot? — Which Dialpad plan syncs calls and recaps to Salesforce or HubSpot.
- How to Turn Sales Call Recordings Into Coaching Notes With AI — Turn the recordings you keep into coaching notes.
- Best AI Note Taker for Accountants: Cost, Consent and Retention — Consent and retention choices for AI note takers in a professional firm.
- How to Set Up Dialpad Voicemail With Greetings and Transcription — Set up Dialpad voicemail greetings and transcripts.
Show 4 more related tutorials
- Best Aircall Alternative for a Small Team on Price and AI — Three seats priced on Aircall, Dialpad, RingCentral and Quo, with the AI each includes and the steps to move a number across.
- How Much Does Dialpad Cost in the UK? Plans, VAT and Numbers — Dialpad's UK list prices, the VAT sum to run before you budget, the number types on offer, and a checklist for the quote.
- Can Otter AI Record Phone Calls? How to Get Calls Into Otter — Get phone calls into Otter through iPhone, Android or Zoom Phone recording, pick the plan that fits your call volume and say the consent line first.
- How to Set Up Dialpad for a Small Team: Numbers, Users, Hours — The setup order that works for a five-person team on Dialpad: numbers and porting, licences and users, departments, business hours and the mobile app.
Browse all AI-for-business tutorials
Sources: Dialpad help centre articles on understanding call recording and transcription, the two-party consent greeting, adding all-party consent states to the exception list, setting up call recording for a contact centre, enabling automatic call recording, recording a call, AI Recaps, turning on Dialpad AI and AI training preferences; Dialpad's call recording disclosure guide; 18 U.S.C. 2511 (Cornell LII); state statutes for California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire and Washington (state legislature sites or their archived copies); ICO guidance on monitoring workers and live marketing calls; the Investigatory Powers (Interception by Businesses etc.) Regulations 2018; Directive 2002/58/EC Article 5 (EUR-Lex); EU AI Act Article 50 (AI Act Service Desk) (all read 22 November 2026).
