Massachusetts voice AI call laws
Massachusetts 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 Massachusetts different
Massachusetts sits in the all-party consent column of our tracker, and with no Massachusetts-specific AI call-disclosure statute identified as of this writing, the recording rule is the load-bearing state obligation for AI calls here. That makes the operational question narrow and unforgiving: was the disclosure actually spoken, on every call, without exception?
The consent rule
Every party on the call must be informed it is being recorded. That covers more than outbound AI campaigns: inbound support lines, callbacks, and the human-agent calls you record for quality review all sit under the same rule. Our compliance guides make the point that AI calls and human calls carry the same recording obligations, so one policy should cover both.
The AI-disclosure angle
With no state AI statute identified yet, the federal frame governs: the FCC's 2024 ruling puts AI-generated and cloned voices inside the TCPA's artificial-or-prerecorded-voice rules, with prior express written consent generally required for marketing calls. Disclosing the AI at the start of the call is the safe operating default even where no statute compels it, and it pairs naturally with the recording disclosure Massachusetts does require.
Penalties
Our tracker carries no Massachusetts-specific penalty figures as of this writing. State wiretap violations can carry criminal as well as civil exposure generally, and federal TCPA statutory damages of $500 to $1,500 per call stack on top. Confirm current Massachusetts penalties with counsel.
How PyAI Trace maps to Massachusetts
PyAI Trace helps you enforce the policy you set and prove it later, on any call source. It checks that the recording disclosure was spoken on every call, human or AI, phone line or meeting platform, and returns a per-call PASS, WARN, or FAIL verdict with a tamper-evident audit hash. On PyAI Omni agents, the consent_line field carries the disclosure, and Trace confirms it was delivered.
Massachusetts 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 Massachusettslaw, 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.