California CIPA and AI Sales Calls: The 2026 Operator Guide
California is the highest-risk jurisdiction in the US for AI call recording and AI listening. CIPA (Cal Penal Code 631-632) requires all-party consent, and the active Ambriz v. Google interception theory extends exposure to AI listeners that do not even record. Here is what sales teams need to know.
Last verified June 2026. This page is informational only; consult qualified California counsel for your specific deployment.
§The CIPA Statute in Plain English
The California Invasion of Privacy Act sits at Cal Penal Code Sections 630 to 638. The two sections that drive AI call-recording risk are:
Section 631: Wiretapping (interception of communications)
Prohibits intentional intercept, eavesdrop, or wilful disclosure of confidential communications without consent of all parties. The Ambriz theory leans on this section to argue that AI processing of call audio constitutes interception regardless of whether traditional recording occurs.
Section 632: Recording of confidential communications
Prohibits recording of confidential communications without consent of all parties. This is the section that catches Fathom, Fireflies, Otter, Gong, Chorus, and Avoma if call recording happens without disclosure to all participants. The conservative reading is that all participants must affirmatively consent or have constructive notice; mere participation is not consent.
Section 637.2 provides the private right of action: $5,000 per violation or three times actual damages. This is the section that funds the plaintiffs' bar class actions and drives the bulk of enforcement risk. Section 638 covers unauthorised connection to telephone lines but is less commonly invoked in AI-call cases.
§The Ambriz v. Google Interception Theory
Ambriz et al. v. Google LLC (Northern District of California, docket 3:23-cv-05437-RFL) was filed on 23 October 2023. It alleges that Google's Cloud Contact Center AI, which listens to and processes customer-service call audio, constitutes interception of confidential communications under CIPA Section 631 even when no traditional recording is created. The theory extends CIPA exposure from recording vendors to any AI listener.
The pivotal development came on 10 February 2025, when the court denied Google's motion to dismiss (2025 WL 830450). The court adopted a "capability test", drawing on the Javier v. Assurance IQ line of cases: an AI vendor that has the capability to use intercepted call audio for its own purposes, such as training its models, is an unauthorised third-party eavesdropper at the pleading stage, regardless of whether it actually re-uses the data. That ruling is the doctrinal template that later AI-wiretap class actions have built on, and it reaches any AI-listener vendor including Microsoft Teams Copilot, Zoom AI Companion, plus sales-side vendors (Gong, Chorus, Clari Copilot, Avoma, Fathom, Fireflies).
As of June 2026 Ambriz remains in discovery and has not reached a merits or class-certification decision. The capability theory is also now contested: subsequent Ninth Circuit rulings have pressed for proof of concrete injury (Article III standing) rather than mere technical capability, and that tension is unresolved. The conservative compliance posture for AI sales tools is to operate as if the capability theory will apply to you.
§Compliance Posture Recommendations
Based on the conservative reading of CIPA plus the Ambriz theory, sales teams calling California prospects with AI-equipped tools should adopt the following posture. None of this is legal advice; confirm with qualified counsel.
1. Explicit AI disclosure in the call opener
Replace "this call may be recorded" with "this call is handled by an AI assistant and may be recorded; if you do not consent, please disconnect now or ask for a human agent." The explicit AI mention plus the disconnect/opt-out option is the conservative compliant posture.
2. Affirmative consent capture for outbound voice AI
For outbound AI voice calls (Vapi, Retell, Bland, Synthflow deployed for outbound), prior express written consent is required not just for CIPA but for TCPA per FCC Ruling 24-17. The CIPA layer adds requirement that the consent specifically mention AI processing, not just recording.
3. Geographic-routing detection at call setup
Detect California area codes (and resident self-disclosure during the call) at call setup. Apply the explicit AI disclosure plus opt-out for any call where any party is California. Some teams apply the disclosure universally to avoid the per-call routing complexity; this is the safest posture.
4. AI processing of recording must be disclosed even when call is recorded with consent
Consent to recording is not automatically consent to AI processing of the recording under the Ambriz theory. Disclose AI processing of stored recordings (call summaries, AI scorecards, AI search) in privacy notices and in the recording disclosure itself.
5. Audit trail of consent capture
Maintain a verifiable audit trail of consent (recording of the disclosure plus consent acknowledgement, timestamped, retained for the statute-of-limitations period plus margin, typically 4 years from call). The audit trail is the primary defence against a CIPA class action alleging that consent was not obtained.
§Vendor Posture on CIPA
Major AI sales-tool vendors have varying postures on CIPA disclosure. None of these vendors will guarantee CIPA compliance for the customer; the operator carries the compliance burden. The vendor posture is about what features are available to support compliance.
| Vendor | Auto-disclosure feature | CIPA-specific notes |
|---|---|---|
| Gong | Yes (configurable per-org) | Customisable opening disclosure; consent log available |
| Chorus by ZoomInfo | Yes (default opt-in) | Standard disclosure; consent log via ZoomInfo admin |
| Clari Copilot | Yes (configurable) | Manual configuration of California-specific notice; consent log available |
| Avoma | Yes (default) | Standard call-start disclosure; consent capture optional add-on |
| Fathom | Yes (default) | Mandatory bot announcement at meeting join; consent log via account |
| Fireflies | Yes (default) | Bot announcement at join; consent log via account |
| Otter.ai | Yes (default) | Bot announcement; consent log via account |
| Vapi | Operator configures | Disclosure must be implemented in the agent's opening script |
| Retell AI | Operator configures | Disclosure must be implemented in the agent's opening script |
| Bland AI | Operator configures + templates | Disclosure templates available but operator implements |
§The B2B Call Exception (And Why It Does Not Save You)
A common misconception in sales: "CIPA only applies to consumers; B2B sales calls are exempt." This is not correct. CIPA applies to all confidential communications, not just B2C. The relevant distinction is whether the communication is confidential, not whether the parties are individual consumers or business representatives.
California courts have repeatedly held that a typical business sales call (where the prospect would have a reasonable expectation that the conversation is not being broadcast or recorded) is confidential under CIPA. The fact that both parties are at work, calling business numbers, with business email addresses, does not strip the call of confidential status.
Some California courts have carved out narrower exceptions for calls where the prospect has clear notice that recording is happening (an inbound customer service line with prominent IVR disclosure, for example). These exceptions do not extend to outbound sales calls where the AE initiates contact without prior disclosure.
§Litigation Reference
The procedural milestones that set the current risk posture, rather than headline dollar figures, are what matter here:
- + Ambriz v. Google LLC (N.D. Cal., MTD denied 10 Feb 2025): The bellwether. The court let the CIPA Section 631 claim against Google's Cloud Contact Center AI proceed on the capability test. Now in discovery; no merits or class-certification ruling yet.
- + Javier v. Assurance IQ (9th Cir.): The earlier session-replay line of cases the Ambriz court drew its capability reasoning from. Establishes that a software vendor can be a third-party wiretapper under CIPA.
- + Williams v. DDR Media, LLC (N.D. Cal., 20 Nov 2024, 2024 WL 4859078): A counterweight. The court granted summary judgment for the defendant on a session-replay CIPA claim, showing these theories do not always survive. Not every AI-listener claim wins.
- + Article III standing pushback (9th Cir., 2025): Later rulings have required plaintiffs to show concrete injury, not just a vendor's technical capability. The split with Ambriz is unresolved and threatens some of the post-Ambriz filings.
No court has yet produced a final judgment on AI-listener-as-interception in the outbound sales-call context. The theory has survived a motion to dismiss but faces a live standing challenge, so sales teams should assume the plaintiff-favourable capability reading until a higher court resolves it.