Key takeaways
- Plumbing calls carry sensitive details: addresses, when a home is empty, access codes, and sometimes health or vulnerability information.
- Recording needs at least one party's consent under federal law, and all parties' consent in some states[1].
- Ask every vendor about consent, retention, access, training use, sub-processors, security, breach notice and data return.
- Get the answers in writing, in the contract or a data processing agreement, not just on a sales call.
Why call data deserves care
An AI phone agent creates a detailed record of every caller: name, phone number, home address, the problem, and often much more. Homeowners mention that they are away until Friday, that the key is under the mat, that the gate code is 4-4-1-9, that an elderly parent lives alone, that someone in the house is on oxygen. A plumbing company would never print that information on a flyer, but a recording and transcript can hold all of it, stored by a third party.
The wider threat picture is not reassuring. The FBI's Internet Crime Complaint Center received 64,882 personal data breach complaints and 21,403 identity theft complaints in 2024, alongside 193,407 phishing and spoofing complaints[2]. Small businesses and their suppliers are part of that picture. You cannot control a vendor's security directly, but you can choose vendors that take it seriously and contract for it.
Customers notice too. In a 2025 Pew survey, 50% of US adults said they were more concerned than excited about the increased use of AI in daily life[3]. A clear answer about what happens to their call is part of earning their trust.
The legal baseline
Federal wiretap law allows a call to be recorded when the person recording is a party to the call or one party has consented, but some states require every party's consent[1]. A vendor should help you play a clear recording notice at the start of each call, and should be able to explain how consent works when callers are in different states.
State privacy laws add duties for larger businesses. The California Consumer Privacy Act applies to for-profit businesses doing business in California with gross annual revenue over $25 million, or that buy, sell or share the personal information of 100,000 or more California residents or households, or earn half or more of revenue from selling it[4]. Several other states have similar laws with their own thresholds. Even if none applies to you today, choosing a vendor that already meets these standards saves trouble later. This is general information, not legal advice; ask your attorney about the laws that apply to you.
The questions, by topic
Send these to every vendor on your shortlist, in writing, and ask for written answers.
Collection and consent:
- What do you record and store for each call: audio, transcript, summary, caller number, metadata?
- How is the recording notice played, and can I change the wording?
- Can I switch off recording for certain numbers, lines or times if I need to?
Storage and retention:
- Where is call data stored, and in which country?
- How long are recordings, transcripts and summaries kept by default, and can I set my own periods?
- When data is deleted, is it removed from backups too, and how long does that take?
Access and use:
- Who at your company can listen to my calls or read transcripts, and is that access logged?
- Are my calls used to train or improve your models or anyone else's? Can I opt out, and is the default opt-in or opt-out?
- Do you share call data with any third parties, and which sub-processors handle it?
Security and incidents:
- Is data encrypted in transit and at rest?
- Do you support multi-factor authentication and user roles for my staff accounts?
- Do you hold any independent security assessments or audits, and can I see a summary?
- How quickly will you tell me about a breach that affects my data, and what will you provide?
Exit:
- If I leave, can I export all recordings, transcripts and summaries, and in what format?
- After I leave, when is my data deleted, and will you confirm it in writing?
Questions about sensitive details on calls
Beyond the standard list, ask how the system handles the most sensitive things callers say. These answers separate vendors that have thought about real calls from those that have not:
- Can the system avoid asking for, or redact, card numbers, bank details and Social Security numbers if a caller starts reading them out?
- Can gate codes, lockbox codes and alarm codes be kept out of summaries, or shown only to the assigned technician?
- If a caller mentions a medical condition or that they live alone, does that appear in the summary, and who can see it?
- Can I search for and delete a specific call if a customer asks?
- Are summaries generated on the same systems as recordings, or sent to another provider to process?
There is no perfect answer to every one of these, but a vendor should be able to explain what it does today, what you can configure yourself and what is still planned.
What good and bad answers look like
| Topic | Good answer | Red flag |
|---|---|---|
| Retention | You choose a period; default is stated in the contract | We keep everything indefinitely |
| Training use | Not used for training without your written opt-in | Vague answer, or only in a long policy page |
| Staff access | Limited roles, access logged, support access only with your permission | Our team can review calls to improve quality, no detail |
| Sub-processors | Named list, with notice of changes | We use trusted partners |
| Breach notice | Specific timeframe in the contract | We'd let you know |
| Export | Full export in standard formats, at any time | Export on request, for a fee, at the end |
| Deletion | Written confirmation, backups included, stated timeframe | Data is deleted eventually |
Your side of the bargain
Vendors are only half of the picture. Much call data leaks from the business itself: a shared login, a forwarded email with a transcript attached, a former employee who still has access. Put these habits in place alongside any new phone system:
- Give each person their own login with multi-factor authentication; never share one account.
- Limit who can listen to recordings to the people who need to, and remove access the day someone leaves.
- Do not forward recordings or transcripts by email unless necessary; link to them in the system instead.
- Tell the agent not to ask for card numbers on calls, and keep payments in your payment system.
- Write down your retention periods and check once a quarter that the settings still match.
- Add a short privacy note to your website explaining that calls may be recorded and how long you keep recordings.
When a customer asks about their recording
Sooner or later a customer will ask whether their call was recorded, ask for a copy, or ask you to delete it. Decide your answer before it happens. Check that your vendor lets you find a call by phone number and date, export the audio and transcript, and delete a single call without affecting others.
Write a short internal procedure: who handles the request, how you confirm the person asking is the caller, how quickly you respond, and how you record that the request was completed. If a state privacy law applies to your business, it may set specific timeframes and rights; if not, treating requests promptly and politely is still good practice and good for your reputation. Never send a recording to anyone other than the caller without a clear reason, such as an insurer handling a claim with the customer's agreement.
Scoring the answers
Must-haves
Mark the non-negotiables: a recording notice you control, a retention period you can set, no training on your data without opt-in, full export and written deletion.
Score the rest
Rate each remaining answer good, acceptable or poor. Treat vague answers as poor until clarified in writing.
Check the paper
Make sure the answers you relied on appear in the contract, the data processing agreement or a signed letter.
Revisit yearly
Ask the same questions at renewal; policies and sub-processors change.
Example: comparing two vendors
Example: a shop shortlists two AI phone vendors. Vendor A lets the shop set retention from 30 days to two years, states in its agreement that call data is not used for training, logs staff access and offers a one-click export. Vendor B keeps recordings for the life of the account, says calls may be used to improve its services, and offers export only on request. Vendor B's voice sounded slightly more natural in the demo. The owner chooses A, because every must-have was met in writing, and puts the voice comparison into the pilot instead.
Frequently asked questions
Do AI phone vendors use my calls to train their AI?
Some do, some do not, and some ask. Ask directly, check the contract, and choose a vendor that does not train on your data without your written opt-in.
How long should call recordings be kept?
Only as long as you need them, often 90 days to a year, with longer retention for calls tied to a complaint, claim or warranty issue.
Is a small plumbing shop covered by privacy laws?
Many state privacy laws have revenue or data-volume thresholds that small shops do not meet, but recording-consent rules apply to everyone. Good data habits are worth following regardless.
What should a vendor contract include on privacy?
Retention periods, limits on training use, staff access controls, a named sub-processor list, a breach notice timeframe, and export and deletion rights.
References
Legal Information Institute, Cornell Law School (2026). 18 U.S. Code ยง 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) โ
FBI Internet Crime Complaint Center (IC3) (2024). Federal Bureau of Investigation Internet Crime Report 2024 (opens in a new tab) โ
Pew Research Center (2025). How Americans View AI and Its Impact on People and Society (opens in a new tab) โ
State of California Department of Justice, Office of the Attorney General (2026). California Consumer Privacy Act (CCPA) (opens in a new tab) โ