Washington voice AI call laws
Washington is an all-party (two-party) consent state for call recording, everyone on the call must be informed it's being recorded. No AI-specific call-disclosure statute has been identified here yet; the federal TCPA and FCC AI-voice rules still apply. Verify the current rule with counsel.
What makes Washington different
Washington is one of the 14 all-party consent states in our tracker, and here the hard question is engineering rather than interpretation: how do you guarantee the disclosure is spoken on every call, every time, when an AI agent is doing the talking? The rule is simple to state and easy to violate at machine scale.
The consent rule
All-party consent means every participant must be informed the call is being recorded before recording begins. Because most AI stacks record by default for transcription and quality, the recording disclosure belongs in the first spoken turn. The same obligation follows the conversation onto meeting platforms: our compliance guides note that Zoom, Google Meet, and Teams calls carry the same recording-consent duties as phone calls and are often overlooked.
The AI-disclosure angle
As of this writing, no Washington-specific AI call-disclosure statute appears in our tracker, so the federal overlay is the binding AI rule: the FCC treats AI-generated and cloned voices as an artificial or prerecorded voice under the TCPA. One opening sentence can satisfy the recording duty and the AI-transparency default at once: this is an AI assistant for the company, and the call is recorded.
Penalties
Our tracker carries no Washington-specific penalty figures yet. State wiretap laws in general can carry criminal as well as civil exposure, and the federal TCPA's statutory damages of $500 to $1,500 per call apply on top. Verify current Washington figures with counsel.
How PyAI Trace maps to Washington
The failure mode in an all-party state is silent: a script edit drops the disclosure, and a thousand calls later nobody has noticed. PyAI Trace scores every call the moment it ends, flags any call where the recording disclosure was not spoken, and keeps the tamper-evident audit record that shows your policy was enforced. On PyAI Omni, the consent_line field in the configure frame speaks the disclosure before the model says anything else.
Washington AI Call Compliance Checklist
- Obtain all-party consent before recording any call
- Keep a tamper-evident audit trail of consent and disclosures per call
On top of Washingtonlaw, the federal TCPA and the FCC's 2024 ruling treating AI/cloned voices as an “artificial or prerecorded voice” apply to every call.
See the federal overlayPrimary sources
- Federal wiretap baseline, 18 U.S.C. § 2511
The federal one-party-consent baseline for recording communications.
- TCPA, 47 U.S.C. § 227; 47 CFR § 64.1200
The federal consent/robocall regime that applies in every state.
- FCC Declaratory Ruling (FCC 24-17, Feb 2024)
AI-generated and cloned voices are an 'artificial or prerecorded voice' under the TCPA.
Seed entry, pending counsel verification. Treat as a starting point, not a legal conclusion.