Rights and contracts
Does 'this call may be recorded for training' cover AI training?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
The familiar notice that 'this call may be recorded for quality and training purposes' usually does not clearly cover licensing recordings to train AI models. Callers reasonably read training as staff coaching, so treat existing recordings as ambiguous, update the script and privacy notice for future calls, and license only de-identified transcripts after counsel reviews consent.
Key takeaways
- A recording notice establishes that recording happens; it does not settle every later use of the recording.
- Training in the standard notice has long meant coaching staff, a narrower purpose than training AI models.
- Wiretap, privacy, biometric and consumer protection laws may each apply to the same recording for different reasons.
- De-identified transcripts carry far less risk than raw audio, which holds voices and every spoken personal detail.
- Updated script wording helps future calls only, so older archives need a separate decision.
What did callers agree to when they heard the notice?#
Callers who heard 'this call may be recorded for quality and training purposes' were told two things: that the call would be recorded, and why. Staying on the line after the notice is often treated as consent to the recording where consent is required, although courts and states differ on the details. Whether it is consent to every later use of that recording is a separate question.
The stated purposes matter. In context, quality meant supervisors reviewing calls and training meant coaching new agents. Licensing recordings to an outside developer to train AI models involves a new recipient and a new purpose that most callers would not have pictured when they heard the phrase.
Some companies' privacy notices already describe broader uses, such as improving products and services or sharing with service providers. Those notices are part of the analysis, but general language in a policy the caller never read is weak support for a use the spoken notice did not mention.
Which laws may apply to call recordings used for AI?#
Several bodies of law may apply to the same recording, each for a different reason, and counsel assesses them together deal by deal. A recording made lawfully can still raise questions when it is put to a new use.
Location matters throughout. The relevant rules can depend on where each caller was, not only where your call center sits, so archives that span many states need a state-by-state view.
Agents are parties to the call too. Their voices and names appear in every recording, and employee notices and, in some states, employee privacy rights apply. Include call center staff in the consent review, not only customers.
| Law area | What it generally governs | What to check for AI use |
|---|---|---|
| Federal and state wiretap laws | Consent to record or intercept a call; some states require consent from every party | Which states callers were in and what notice they heard |
| State comprehensive privacy laws | Notice of purposes, disclosures to third parties, opt-outs and sensitive data | Whether licensing counts as a sale or a new purpose needing notice or consent |
| Biometric privacy laws | Voiceprints and other biometric identifiers | Whether audio or derived voice features would be delivered |
| FTC Act Section 5 | Deceptive or unfair practices, including changes to data practices | Whether the use conflicts with what callers were told |
| Customer contracts | B2B calls about a client's account, systems or data | Confidentiality and data-use clauses covering business callers |
| Payment card rules | Card numbers read aloud during calls | Whether pause-and-resume recording or redaction removed them |
Audio or transcripts: which carries less risk?#
Transcripts carry less risk than audio, and de-identified transcripts carry less still. A voice is personal to the speaker, can be linked back to them and may be treated as biometric data in some places once voice features are extracted. A transcript with names, numbers and addresses removed keeps the structure of the conversation without the speaker.
For most AI developers interested in service conversations, the value sits in the structure anyway: the reason for the call, the questions asked, the decision and the outcome. That is why transcripts tied to the resulting job or ticket are usually the practical unit to license.
Speaker labeling matters for preparation. Agent turns and caller turns carry different risks: callers volunteer addresses, card numbers and health details, while agents read back account information. Reviewers should check both sides of the conversation, not only the caller's.
| Format | What it contains | Typical preparation | Licensing outlook |
|---|---|---|---|
| Raw audio | Voices, background speech and every spoken detail | Hard to de-identify fully | Usually excluded for older calls |
| Full transcript | Words spoken, often with speaker labels | Remove names, phone numbers, addresses, account and card numbers | Possible after preparation and consent review |
| De-identified transcript | Conversation flow, issue, steps and outcome | Automated detection plus human review | Usually the most practical option |
| Call summary with outcome | Reason for call, resolution and follow-up | Light review | Lowest risk, least detail |
How should the script change for future calls?#
The script for future calls should name AI development as a purpose in plain words, so callers hear it rather than find it in a policy. Wording is a decision for counsel, but a version for review might say that calls are recorded for quality, staff training and improving services, including developing AI tools, which may involve sharing de-identified transcripts with outside developers.
Updated wording does not reach backward. Calls recorded under the old notice stay under the old notice, which is why the change date matters as much as the words.
Keep every version of the script, with its live dates, alongside the recordings' retention policy. When a buyer or regulator asks what callers heard during a given period, the answer should be on file rather than reconstructed from old IVR configurations.
- Update the spoken greeting, IVR prompts and any agent-read script at the same time.
- Mirror the language in the privacy notice and in chat and email auto-replies, so every channel matches.
- Offer a way to decline AI use where the law or your policy calls for it, and record the choice against the call.
- Log the date the new wording went live in the phone system, so recordings can be split into before and after.
- Check whether your contact center vendor's terms let you export and license the recordings at all.
Illustrative: an HVAC company reviews its call archive#
Illustrative: a fictional HVAC and plumbing company has years of recorded booking and dispatch calls in its cloud phone system, linked to customer records and jobs in ServiceTitan. A model developer is interested in how call-takers diagnose problems over the phone and decide whether to send a technician.
Counsel concludes that the old quality and training notice is too ambiguous to support licensing the audio. The company excludes all historical audio, updates its greeting and privacy notice, and logs the change date. For older calls it will consider only de-identified transcripts tied to job outcomes, and only after a further consent review.
In the meantime it licenses dispatch notes, estimates and job histories, which carry much of the same diagnostic reasoning without anyone's voice.
How SourceX handles recorded calls#
SourceX treats recorded calls as a high-sensitivity record family within the SourceX five-step transaction. In the Rights step, the supplier documents the notice wording, where callers were located and when notices changed. In Preparation, transcripts are de-identified, and audio is excluded unless the supplier and its counsel decide otherwise.
The privacy record in the SourceX Evidence Packet notes which notice version applied to each date range, so a buyer can see exactly which calls were licensed and on what basis.
Frequently asked questions
Does the analysis change for business-to-business calls?
Somewhat. Wiretap laws protect business callers too, and some state privacy laws cover people acting for a business. B2B calls also add contract duties: a client's account details, pricing or technical data discussed on a call may be confidential under your agreement with that client.
Is de-identification alone enough to license old recordings?
Not on its own. De-identification lowers privacy risk but does not resolve whether the recording was made and used consistently with the notice and applicable law. Automated detection tools also miss details, so human review matters. Counsel weighs both the consent question and the quality of preparation.
Do we have to notify callers from past years?
That depends on the laws that apply and the use you plan. Contacting past callers is often impractical, which is one reason companies exclude older audio and rely on de-identified transcripts or on recordings made after an updated notice. Counsel can advise whether notice or consent is needed.
What if our phone or contact center vendor already uses calls for AI?
Check the vendor's terms and settings. Some providers reserve rights to use customer recordings to improve their own AI features, which may not match what your callers were told. In some recent lawsuits, plaintiffs have argued that a provider able to use call content for its own purposes is a third party listening without consent under state wiretap laws. That exposure is separate from licensing, but it affects what you can promise a buyer.
Are chat transcripts treated the same as calls?
Written chats contain no voice data, so they are usually easier to prepare. The purpose and disclosure questions are the same as for calls: what the chat notice said, whether personal details were removed and whether customer contracts restrict use. Interception questions can still arise, so counsel should review chat tools too.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.