
Call Recording Laws for AI Agents by State
Navigate state recording laws to avoid costly fines and stay compliant when your AI phone agent handles customer calls.

Written by
Adam Stewart
Key Points
- Follow the stricter state's law when calls cross state lines
- Disclose both recording and AI usage at every call start
- Know which of the 12 all-party consent states affect your business
- AI creates extra compliance needs beyond simple recording laws
AI phone agents like Dialzara can handle thousands of calls monthly, but staying compliant with call recording laws is a must. Here's what you need to know:
- Federal Law: The U.S. Wiretap Act requires one-party consent for recording calls. If your business consents, you're covered federally.
- State Laws: 38 states follow the one-party consent rule. However, 12 states, including California and Florida, require all-party consent, meaning everyone on the call must agree to the recording.
- AI-Specific Rules: States like California now require businesses to disclose when an AI agent is being used. For example, California's AB 2905 imposes a $500 fine per call without proper AI disclosure.
- Cross-State Calls: The stricter law applies. If calling from a one-party state to an all-party state, you must follow the all-party consent rules.
Best Practice: Always disclose at the start of every call that the conversation is being recorded and that an AI agent is involved. Use a script like:
"This is an AI assistant calling on behalf of [Your Company]. This call may be recorded for quality purposes."
Following these steps not only avoids fines but also builds customer trust. This transparency is a key way AI phone agents improve customer engagement and satisfaction. Regular audits and tools like Dialzara can automate compliance, ensuring your business meets all state and federal requirements.
US Call Recording Laws by State: One-Party vs All-Party Consent Requirements
Federal Call Recording Laws for AI Agents
Federal laws provide the groundwork for call recording rules in the United States. Under 18 U.S.C. § 2511, commonly referred to as the federal Wiretap Act, the one-party consent rule applies. This means that a conversation can be legally recorded as long as at least one participant in the call is aware of and agrees to the recording [5][4]. For businesses using AI phone agents, like Dialzara, this is straightforward: the AI agent acts as your company's consenting party. In essence, your business's consent extends to the AI agent [1][5]. However, while federal law sets the stage, state-specific regulations add layers of complexity to call recording practices.
Across the U.S., 38 states and Washington D.C. adhere to the one-party consent standard. However, 12 states, including California and Florida, enforce stricter all-party consent rules [3]. This means that in these states, every participant on the call must be notified and consent to the recording, even if your business operates in a one-party consent state.
The One-Party Consent Rule
The one-party consent rule is straightforward: only one person involved in the conversation needs to be aware of and agree to the recording. When your AI phone agent manages calls, your business fulfills this requirement as the consenting party [1][5]. Under federal law, no additional announcement is required. However, if your call involves someone in one of the 12 all-party consent states - which account for roughly 35% of the U.S. population [3] - you must notify them about the recording.
For businesses operating across state lines, the safest approach is to assume all calls require all-party consent. Including a disclosure at the start of every call ensures compliance no matter where the caller is located [3].
AI-Specific Requirements Under Federal Law
AI-driven interactions add another layer of complexity to call recording laws. Unlike traditional recordings, AI systems capture real-time transcripts, extract structured data (like names and dates), and store conversation details for integration with CRM tools [5]. This expanded data collection increases the need for transparency and may trigger additional requirements under state laws.
Transparency isn’t just a legal requirement - it’s also becoming an ethical expectation. As Justas Butkus, Founder & CEO of AInora, explains: "The fundamental distinction in call recording law worldwide is between one-party consent and two-party (all-party) consent" [5]. Many states, like California, are already requiring businesses to inform callers when they’re interacting with an AI agent.
"Even in one-party jurisdictions, most compliance experts and regulatory guidance recommends informing the other party as a matter of best practice." - AInora [5]
A practical solution for businesses is to combine disclosures into a single opening statement. For example: "This is an AI assistant calling on behalf of [Your Company]. This call may be recorded for quality and training purposes." This covers both the AI nature of the call and the recording notification, ensuring compliance with federal laws while preparing for stricter state regulations [5].
sbb-itb-ef0082b
One-Party Consent States Checklist
In states with one-party consent laws, businesses can record calls if at least one party - such as the business itself - consents. Below is a detailed table of these states, followed by recommendations for AI disclosure practices.
Table of One-Party Consent States
| State | Consent Standard | AI Disclosure Recommendation | Relevant Notes |
|---|---|---|---|
| Alabama, Alaska, Arizona, Arkansas | One-Party | Disclosure advised | Meets federal standards[3] |
| Colorado, Georgia, Hawaii, Idaho | One-Party | Disclosure advised | In Hawaii, applies where a reasonable expectation of privacy exists[3] |
| Indiana, Iowa, Kansas, Kentucky | One-Party | Disclosure advised | Meets federal standards[3] |
| Louisiana, Maine, Minnesota, Mississippi | One-Party | Disclosure advised | Meets federal standards[3] |
| Michigan | One-Party | Disclosure advised (Interstate) | Confirmed as one-party per AFT v. Project Veritas[3] |
| Missouri, Nebraska, New Jersey, New Mexico | One-Party | Disclosure advised | Meets federal standards[3] |
| New York, North Carolina, North Dakota, Ohio | One-Party | Disclosure advised | High-volume business hubs[3][6] |
| Oklahoma, Oregon, Rhode Island, South Carolina | One-Party | Disclosure advised | Oregon: one-party for phone; all-party for in-person[3] |
| South Dakota, Tennessee, Texas, Utah | One-Party | Disclosure advised | Texas is one of the largest one-party jurisdictions[3][6] |
| Virginia, West Virginia, Wisconsin, Wyoming | One-Party | Disclosure advised | Meets federal standards[3][7] |
| Washington D.C. | One-Party | Disclosure advised | Follows the federal one-party standard[3][6] |
AI Disclosure Guidelines in One-Party States
While one-party consent laws align with federal standards, businesses should still prioritize proactive disclosure. Even though these laws don’t mandate announcing recordings, disclosing both the recording and AI usage at the start of every call is a smart practice. This approach ensures compliance if the call involves a participant from an all-party consent state, such as California.
"The safest approach - and the one most attorneys recommend - is to follow the stricter standard. If there is any chance you receive calls from two-party consent states, include a recording disclosure on all calls"[1].
To ensure compliance, program your AI assistant with a standardized greeting like:
"This is an AI assistant, and this call may be recorded for quality purposes."
This not only informs participants about the recording but also makes the AI use transparent[3].
In most cases, implied consent applies. If the caller stays on the line after hearing the disclosure, they are considered to have given consent[1][3]. Advanced AI phone systems, like Dialzara, can automate these disclosures, ensuring every call begins with the necessary compliance safeguards, even when dealing with interstate calls.
All-Party Consent States Checklist
In certain states, everyone participating in a call must be informed and agree before the conversation is recorded. This rule sets a higher bar compared to the federal one-party consent standard. Currently, 12 states enforce all-party consent laws: California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington [3].
Failing to comply with these laws can lead to hefty civil penalties, ranging from $1,000 to $10,000 per violation [1]. Additionally, states like Maryland and Massachusetts impose criminal penalties, which can include up to five years in prison [11]. For AI phone agents, there’s an added layer of responsibility: they must inform callers that the interaction involves AI and that the call is being recorded [3].
Table of All-Party Consent States
| State | Consent Standard | AI Disclosure Requirements | Penalties for Non-Compliance | Enforcement Notes |
|---|---|---|---|---|
| California | All-Party | Mandatory (AB 2905) | Civil/Criminal penalties | Strictest requirements; applies to interstate calls [3][12] |
| Connecticut | All-Party (Phone) | Mandatory disclosure | Up to $1,000 (Federal baseline) | All-party for phone; one-party for in-person [3] |
| Delaware | All-Party | Mandatory disclosure | Civil/Criminal penalties | Requires notification before recording [3] |
| Florida | All-Party | Mandatory disclosure | Civil/Criminal penalties | Strictly enforced; violations can be felonies [3][9] |
| Illinois | All-Party | Mandatory disclosure + Biometric | Civil/Criminal penalties | BIPA requires written consent for collecting voiceprints [10] |
| Maryland | All-Party | Mandatory disclosure | Civil/Criminal penalties | Requires consent from all participants [3][9] |
| Massachusetts | All-Party | Mandatory disclosure | Civil/Criminal penalties | Bans "secret" recordings; requires meaningful assent [3] |
| Montana | All-Party | Mandatory disclosure | Civil/Criminal penalties | Everyone must know they are being recorded [11] |
| Nevada | All-Party (Phone) | Mandatory disclosure | Civil/Criminal penalties | All-party for phone; one-party for in-person [3] |
| New Hampshire | All-Party | Mandatory disclosure | Civil/Criminal penalties | Strict consent required [3][9] |
| Pennsylvania | All-Party | Mandatory disclosure | Civil/Criminal penalties | Applies to all electronic communications [11] |
| Washington | All-Party | Mandatory disclosure | Civil/Criminal penalties | Requires notification for all private communications [3] |
Special Requirements for AI Agents in All-Party States
Here’s what your AI agents need to do to stay compliant when operating in these states:
If a caller continues the conversation after the disclosure, their consent is considered implied [1][3]. Your AI must clearly state two things at the start of every call: that it is an AI assistant and that the call is being recorded. A compliant introduction might sound like this:
"This is an AI assistant, and this call is being recorded for quality purposes."
When handling calls that cross state lines, the stricter law takes precedence. To avoid complications, many legal experts suggest a universal approach: provide a recording disclosure on every call, no matter where it originates.
"The safest approach - and the one most attorneys recommend - is to follow the stricter standard. If there is any chance you receive calls from two-party consent states, include a recording disclosure on all calls."
- George M. Espinoza Acosta [1]
Automation tools like Dialzara can simplify compliance. These systems ensure your AI agent delivers the required disclosure at the beginning of every call, whether it’s from Florida, Massachusetts, or elsewhere. Automating this process reduces the risk of human error and shields your business from potential legal troubles.
These practices align with broader efforts to ensure compliance across the country for AI-driven call centers.
California AB 2905: AI-Specific Call Recording Requirements

California's AB 2905 has raised the bar for AI-driven calls, setting some of the toughest disclosure requirements in the country. Effective January 1, 2025, this law goes beyond standard consent rules for call recording. It specifically focuses on calls using artificial voices, demanding upfront transparency before any AI interaction begins.
Key Provisions of AB 2905
AB 2905 made significant changes to Section 2874 of the California Public Utilities Code, targeting AI-powered calls made through automatic dialing systems. The law defines an "artificial voice" as one generated or significantly modified using artificial intelligence - often referred to as a "synthetic voice." Before an AI agent delivers its message, a natural voice (that is not recorded) must clearly state:
- The purpose of the call
- The business's name, address, and phone number
- A request for the recipient's consent to proceed
This applies to all AI voice interactions, regardless of the call's length or purpose.
Noncompliance carries hefty penalties: $500 per undisclosed AI call and up to $5,000 per violation under the California Invasion of Privacy Act [8].
"California's AB 2905 represents the most significant development in AI call compliance for 2025. The legislation specifically targets AI interactions and imposes strict disclosure requirements that go beyond traditional call recording laws." - Hostie [8]
To meet these obligations, businesses must adapt their scripts and technical systems accordingly.
How to Comply with AB 2905
For businesses using AI phone agents, compliance with AB 2905 requires a few critical adjustments. Start by revising scripts to include immediate AI disclosure. For example, an AI agent might say: "Hello, I am an AI assistant for [Business Name]. This call is being recorded and uses an artificial voice. Do you consent to continue?"
For outbound calls, a natural voice introduction - either live or unrecorded - must precede any AI interaction. This step ensures compliance with the law's requirement for transparency before engaging with an artificial voice.
To streamline compliance, consider implementing geo-detection technology. These tools can identify California area codes (e.g., 213, 310, or 415) and trigger enhanced disclosure scripts automatically. Additionally, maintain detailed consent logs for every call, capturing timestamps and the exact script used. Platforms like Dialzara can automate this process, ensuring proper documentation.
Finally, always offer human handoff best practices for callers who prefer to interact with a person instead of an AI.
Because California requires all-party consent for call recording, these rules apply to any call involving a California resident - even if your business is based in another state. Adopting these enhanced standards across the board can simplify operations and reduce compliance risks.
Compliance Guidelines for AI Phone Agents
Incorporating compliance measures into your AI phone agents from the start is crucial. It not only shields your business from potential fines but also helps foster trust with your customers.
Standardized AI Disclosures
Every call must include a clear, standardized disclosure. Your AI agent should inform the caller of two key points: that they are interacting with an AI assistant and that the call may be recorded [3][5].
A simple script can make this process seamless. For example: "This is an AI assistant calling from [Company Name]. This call may be recorded for quality and training purposes. How can I help you today?" [3][5]. Both elements - acknowledging the AI and the recording - are essential for compliance [5].
In many areas, continuing the conversation after this disclosure implies consent. However, in sensitive industries like healthcare or legal services, it’s a good idea to ask explicitly: "Do I have your consent to proceed?" [3][5].
Training Your AI Agent for Compliance
Platforms such as Dialzara can simplify compliance by automating disclosures, ensuring they’re never missed, and creating an audit trail complete with timestamps and metadata [3][5]. Program your AI agent to consistently deliver these mandatory disclosures at the start of every call.
For businesses handling calls across different states, geo-detection can be a game-changer. It enables your system to identify all-party consent states like California and apply stricter disclosure requirements for area codes such as 213, 310, and 415 [2]. This is especially important in states like California, where failing to disclose AI use can result in fines of $500 per call under AB 2905 [2].
Your AI agent should also be equipped to handle objections to call recording. If a caller declines to be recorded, the system should either disable the recording while continuing the conversation or end the call if recording is mandatory for business purposes [1][5]. Additionally, offering a human handoff option - such as saying "transfer" to speak with a person - gives customers more control and builds trust [2].
Once your disclosures and training are in place, regular audits will ensure these measures remain effective.
Regular Legal Audits
Legal requirements for call handling and recording can change frequently, making routine audits essential. Conduct quarterly reviews to confirm that disclosure scripts are functioning properly and that your AI agent complies with caller preferences [3]. At least once a year, review state-specific laws to stay ahead of new regulations like California's AB 2905 [1][2].
Key areas to focus on during audits include verifying the accuracy of scripts, reviewing consent records with timestamps, checking configuration logs, and ensuring staff training is current [2]. Monthly call samples should also be reviewed to confirm disclosures are delivered promptly and audio quality is clear [3].
"Compliance isn't just about following rules - it's about proving you followed them." - Hostie [2]
Set up automated retention policies to delete recordings after 30 to 90 days unless longer retention is required by law [5][1]. This reduces data liability and simplifies compliance. Use AES-256 encryption for stored recordings and TLS 1.2+ for data in transit to meet security standards [5]. For interstate calls, always follow the stricter state’s laws. For example, if your caller is in an all-party consent state like California, that standard applies - even if your business operates in a one-party consent state [3][4].
Conclusion
Staying compliant with call recording laws for AI agents requires a clear understanding of consent regulations. In the U.S., 38 states follow one-party consent laws, while 12 require all-party consent. The safest route? Notify every caller that they’re speaking with an AI assistant and that the call may be recorded [3][14].
The stakes for non-compliance are high. For example, in April 2026, a Chicago company faced a $4.2 million settlement for recording 5,000 calls without proper consent - an average of $840 per call [14]. California's AB 2905 further tightens the rules, enforcing $500 fines for each undisclosed AI-generated call [8][13].
"The simplest approach: notify on every call and you're covered in all 50 states." - NextPhone [3]
These cases highlight the importance of AI in business call answering. Tools like Dialzara’s platform help ensure compliance by automating disclosures at the start of every call, logging consent with precise timestamps, and integrating with over 5,000 business applications. This not only keeps your business legally compliant but also builds trust with your customers.
When handling interstate calls, always adhere to the strictest applicable law. Maintaining regular audit trails further safeguards your business as regulations continue to evolve. With the right processes and tools, compliance becomes a natural part of delivering consistent, high-quality customer service around the clock.
FAQs
How do I know which state’s law applies to an interstate call?
To figure out which state's law governs an interstate call, you need to account for the laws in both the state where the call is received and the state where the recording takes place. States generally fall into two categories: one-party consent or all-party consent laws, depending on the jurisdiction. If you're unsure, the safest bet is to get explicit consent from all parties involved to avoid any legal issues.
What should my AI agent say to get valid consent fast?
To promptly secure valid consent, your AI agent should clearly inform the caller that the conversation is being recorded and request their agreement before moving forward. A straightforward script might be: "This call is being recorded for quality and compliance purposes. Do you agree to continue?" This approach not only aligns with state laws, particularly in two-party consent states, but also ensures the process remains quick and efficient.
Do I need written consent if my system stores voiceprints or transcripts?
Yes, if your system stores voiceprints or transcripts, you’ll typically need to get explicit consent from everyone involved. States like California have all-party consent laws for call recording and data collection. To stay compliant, make sure you review local laws and secure the required permissions before storing this kind of information.
Summarize with AI
Related Posts
AI Call Centers: Staying Compliant in Real Time
Real-time AI monitoring, automated consent logs, PII masking and time‑zone controls to keep SMB call centers TCPA, state, HIPAA and PCI-DSS compliant.
5 Ways to Disclose AI Use in Customer Calls
Five practical ways to disclose AI on customer calls: open disclosure, IVR prompts, privacy updates, consent, and post-call notices.
Call Recording Laws for AI Phone Agents
Ignoring call-recording and AI-disclosure laws exposes businesses to steep fines and legal risk.
How AI Call Monitoring Meets Legal Standards
Explains consent, disclosure, industry rules, data controls, and audit-ready practices for legally compliant AI call monitoring across U.S. jurisdictions.
