New York voice AI call laws
New York is a one-party consent state for call recording, at least one participant (which can be you) must consent. AI-specific disclosure legislation is pending or newly enacted here, track its status before relying on it. Verify the current rule with counsel.
What makes New York different
New York is a one-party consent state today, but it has one of the busiest AI legislative pipelines in our tracker: multiple AI-use and call-center transparency bills have been proposed (our dataset notes SB 2453 and SB 4050 among them), with none in effect as of this writing. This page is less about what New York law says now and more about how quickly that could change.
The consent rule
One-party consent means your own consent to record is enough under New York law. The geography does not cooperate, though: Connecticut, Massachusetts, and Pennsylvania, all all-party states in our tracker, sit next door, and New York businesses call into them constantly. The practical default for New York operations is still to disclose recording on every call, because the strictest state on the line sets the safe rule.
The AI-disclosure angle
Our tracker marks New York's AI-disclosure status as pending: track the proposed bills until one is enacted, and do not treat a proposed bill as current law in either direction. Meanwhile the federal overlay binds every call: the FCC treats AI-generated and cloned voices as an artificial or prerecorded voice under the TCPA, with prior express written consent generally required for marketing calls.
Penalties
Our tracker carries no New York-specific penalty figures as of this writing; pending bills vary. The federal numbers apply in full: $500 per violating call under the TCPA, trebled to $1,500 for willful or knowing violations, with no statutory cap. Verify the current legislative status with counsel.
How PyAI Trace maps to New York
A pending-law state rewards teams that can change policy fast. PyAI Trace rule packs are configuration, not code, so when a New York disclosure bill is enacted you add the rule and every subsequent call is scored against it, with a tamper-evident audit trail proving when your policy changed. Adopting PyAI Omni's consent_line early costs you one configuration field now, and the disclosure is already part of the agent if the law starts requiring it.
New York AI Call Compliance Checklist
- Obtain at least one-party consent before recording any call
- Keep a tamper-evident audit trail of consent and disclosures per call
On top of New Yorklaw, 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.