Call Recording Consent: One-Party vs Two-Party States Guide

One-Party vs Two-Party Consent: The Basics

US call recording laws fall into two categories:

• One-party consent states (39 states + DC). Only one party to the call needs to know the call is being recorded. Since your business (or your AI) is a party to the call and you know it is being recorded, this requirement is automatically satisfied.
• Two-party (all-party) consent states (11 states). All parties to the call must consent to the recording. This means the lead must be informed that the call is being recorded and must agree to it before recording begins.

The term "two-party" is slightly misleading - it actually means "all-party." If three people are on a conference call in a two-party state, all three must consent.

The 11 Two-Party Consent States

As of 2025, these states require all-party consent to record a phone call:

1. California - Cal. Penal Code section 632. Violations can result in fines up to $2,500 per violation and civil damages of $5,000 per violation.
2. Connecticut - Conn. Gen. Stat. section 52-570d. Applies to in-person and telephone communications.
3. Delaware - Del. Code Ann. tit. 11 section 2402. Requires consent of all parties to the communication.
4. Florida - Fla. Stat. section 934.03. A felony to record without consent. Civil damages of $100 per day for each day of violation or $1,000, whichever is higher.
5. Illinois - 720 ILCS 5/14-2. One of the strictest recording consent states. Criminal penalties for violations.
6. Maryland - Md. Code Ann., Cts. & Jud. Proc. section 10-402. All-party consent required for both in-person and phone recordings.
7. Massachusetts - Mass. Gen. Laws ch. 272, section 99. Prohibits "secret" recording. All parties must consent.
8. Montana - Mont. Code Ann. section 45-8-213. Requires consent of all parties to the communication.
9. New Hampshire - N.H. Rev. Stat. Ann. section 570-A:2. All-party consent for phone and in-person conversations.
10. Pennsylvania - 18 Pa.C.S. section 5703. All-party consent. Criminal and civil penalties for violations.
11. Washington - Wash. Rev. Code section 9.73.030. All-party consent required. Also has specific AI disclosure requirements.

Important: When your business is in one state and the lead is in another, the general best practice is to follow the more restrictive law. If either party is in a two-party consent state, treat the call as requiring all-party consent.

How AI Should Handle Recording Disclosure

The AI's recording disclosure should be delivered at the very beginning of the call, before any substantive conversation takes place. Here is a recommended approach:

Recommended Disclosure Script

The AI's opening should include a recording notice as part of its natural introduction. Example:

"Hi [name], this is [AI name] calling from [Company Name]. You submitted a request on our website. I should let you know this call may be recorded for quality purposes. Is that okay with you?"

Key elements of this disclosure:

• Timing. The disclosure comes before any discussion of the lead's inquiry.
• Clarity. The word "recorded" is used explicitly. Vague language like "this call may be monitored" is weaker.
• Consent request. In two-party states, asking "Is that okay?" and getting an affirmative response provides explicit consent.
• Natural flow. The disclosure is woven into the introduction rather than sounding like a legal disclaimer.

Handling Consent Refusal

If the lead says they do not want the call recorded, the AI has two options:

1. Stop recording and continue the call. If your system supports real-time recording toggling, the AI can disable recording and proceed with the conversation. This is the best customer experience.
2. Continue without recording. If the system cannot toggle recording mid-call, the AI should note that the call will not be recorded and proceed normally. The call data (minus the recording) should still be logged for compliance purposes.

Do not end the call simply because the lead declines recording. The lead submitted your form and wants to talk - do not lose the opportunity over a recording consent issue.

State-by-State Implementation

For businesses operating across multiple states, the most practical approach depends on your call volume and risk tolerance:

Option 1: Universal All-Party Consent (Recommended)

Apply two-party consent rules to every call, regardless of where the lead is located. This is the simplest and safest approach:

• The AI always discloses recording at the start of the call
• The AI always asks for consent
• No need to determine the lead's state before the call
• Eliminates risk of misidentifying a lead's location

The downside is minor - you add a few seconds to every call. The upside is total compliance certainty and a consistent customer experience.

Option 2: State-Based Recording Logic

Use the lead's phone number area code or form-submitted location to determine their state, then apply the appropriate consent rules:

• Two-party state detected: AI discloses recording and asks for consent
• One-party state detected: AI may still disclose (best practice) but does not need explicit consent

The risk with this approach is that area codes are not always accurate. People move, use VoIP numbers, and keep old area codes. A lead with a Texas area code might be sitting in California. If you choose this approach, consider defaulting to all-party consent when location cannot be confirmed.

Federal Considerations

Federal wiretapping law (18 U.S.C. section 2511) is a one-party consent statute. However, the federal law sets a floor, not a ceiling. State laws can be (and frequently are) more restrictive. You must comply with both federal law and the applicable state law.

Additionally, the FCC has ruled that AI-generated voices constitute "artificial or prerecorded voices" under the TCPA. This means AI calls already require prior consent under federal law. Adding a recording disclosure to the call is a natural extension of the consent framework you should already have in place.

Recording Disclosure Language Requirements

While specific language requirements vary by state, effective recording disclosure should include:

• The word "recorded." Use it explicitly. "Monitored" or "quality assurance purposes" alone may not satisfy the recording consent requirement.
• Timing before the conversation. The disclosure must come before any substantive discussion. A disclosure buried in the middle of the call may not protect you.
• An opportunity to object. In two-party states, the other party must have a reasonable opportunity to decline. Implied consent (continuing the call after hearing the disclosure) may be sufficient in some states but not all. Asking for explicit consent is safer.
• Documentation. Log whether the lead consented to recording. If they declined, log that the call proceeded without recording. This documentation is your proof of compliance.

Interaction with HIPAA

If your AI calls healthcare leads (dental, medical spa, veterinary), call recordings create an additional layer of compliance requirements. A recording of a patient discussing their health needs is Protected Health Information (PHI) under HIPAA and must be stored, accessed, and eventually destroyed according to HIPAA rules.

For a complete guide on HIPAA compliance for AI calling, see our HIPAA AI calling guide. For general TCPA compliance with website form AI callback, see our TCPA compliance guide.

Best Practices Checklist

• Disclose recording at the start of every AI call
• Ask for explicit consent in two-party states (or universally, for simplicity)
• Have a process for calls where the lead declines recording
• Log consent/refusal status for every recorded call
• Retain consent records for at least 5 years
• Review your state list annually - laws change, and states occasionally update their recording consent requirements
• When in doubt about a lead's location, default to all-party consent
• Train your AI to recognize phrases like "do not record this" or "I do not want to be recorded" and respond appropriately

Disclaimer: This guide provides general information about call recording consent laws. It is not legal advice. State laws change, and court interpretations evolve. Consult with a qualified attorney for guidance specific to your business and the states where you operate.

Want help configuring compliant AI callback with proper recording disclosures? Book a discovery call and we will review your multi-state setup.

Frequently Asked Questions

What happens if I record a call without consent in a two-party state?

Penalties vary by state but can be severe. In Florida, it is a felony. In California, civil damages can reach $5,000 per violation. In Illinois, criminal penalties apply. Beyond statutory penalties, illegally recorded calls are generally inadmissible as evidence and can expose your business to civil lawsuits from the recorded party.

Does "implied consent" count in two-party states?

In some two-party states, courts have held that continuing a call after hearing a recording disclosure constitutes implied consent. However, this is not universally accepted across all 11 two-party states. Massachusetts, for example, requires actual knowledge and consent, and a brief automated disclosure at the start may not always be sufficient. Asking for explicit verbal consent ("Is that okay?") is the safer approach.

Which state law applies if the caller and the lead are in different states?

There is no universal rule, and courts have reached different conclusions. The majority approach is to apply the law of the state where the recording occurs, but some courts apply the law of the state where the recorded party is located. The safest practice is to follow the more restrictive of the two states' laws. If either party is in a two-party state, get consent.

Can the AI just not record calls to avoid this issue entirely?

Yes, not recording calls eliminates the recording consent issue entirely. However, call recordings provide valuable benefits: quality assurance, dispute resolution, training data, and compliance documentation. A better approach is to record with proper consent rather than forgoing recordings altogether. The disclosure takes only a few seconds and most leads have no objection.

Do these rules apply to call transcriptions generated by AI?

Generally, yes. A real-time transcription is functionally equivalent to a recording - it captures the content of the conversation in a retrievable format. If your AI system generates transcripts (even without audio recording), the same consent rules likely apply. Treat transcription the same as recording for consent purposes.