Maryland voice AI call laws
Maryland 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 Maryland different
Maryland is one of the 14 all-party consent states in our tracker, and the rule cuts in both directions: it covers the customer's side of the call and yours. The recordings your team makes for quality review, coaching, and dispute resolution are governed the same way an AI agent's default transcription recording is, so a Maryland policy has to account for every recorded conversation, not just outbound campaigns.
The consent rule
Everyone on the call must be informed it is being recorded before recording starts. In practice that means the disclosure is spoken in the first turn, every time. Calls between Maryland and one-party neighbors are exactly where a single stricter-rule default keeps you out of trouble: follow the strictest state on the line rather than maintaining per-call logic about who is where.
The AI-disclosure angle
As of this writing, no Maryland-specific AI call-disclosure statute appears in our tracker. The federal overlay still applies on 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. A single opening line covers the recording disclosure Maryland requires and the AI disclosure good practice suggests.
Penalties
Our tracker carries no Maryland-specific penalty figures as of this writing. State wiretap violations can carry criminal as well as civil exposure in general, and the federal TCPA's $500 to $1,500 per call statutory damages apply on top. Verify current Maryland figures with counsel.
How PyAI Trace maps to Maryland
Because PyAI Trace works from call audio, it applies the same recording-disclosure check to every recorded conversation you have: AI agents, human agents, phone providers, and meeting platforms alike. Each call gets a verdict and a tamper-evident audit hash, so your Maryland policy is something you can demonstrate, not just assert. You can scan your last 1,000 calls free to see where the gaps are, and PyAI Omni's consent_line field handles the spoken disclosure on PyAI-run agents.
Maryland 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 Marylandlaw, 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.