Recording consent
Voice MCP gates call recording behind a two-party (all-party) consent check across 13 states, inferred from the caller's area code — and it fails closed for international and unidentifiable callers.
Call recording in Voice MCP is only turned on when a tenant opts in — and even then, recording is gated behind a jurisdiction check that decides whether a verbal recording acknowledgment is required before capture begins.
How the jurisdiction is decided
The gate classifies the caller by their North American Numbering Plan (NANP) area code into one of four jurisdictions:
- Two-party (all-party consent) — the caller's US area code maps to a state that requires every party to consent.
- Single-party — a US number whose area code is not in the two-party set; one party's consent suffices.
- International — a non-US number; treated as requiring opt-in (GDPR posture).
- Unknown — the caller isn't a standard phone number at all: an empty or unparseable caller ID, or a non-telephone identity (for example a SIP
client:address) with no area code.
The 13 two-party states
These states are classified as all-party (two-party) consent jurisdictions:
CA, CT, DE, FL, IL, MD, MA, MT, MI, NV, NH, PA, WA.
When a caller's area code maps to any of these states, a verbal recording acknowledgment is required before the call is recorded.
The gate fails closed
A verbal acknowledgment is required for two-party callers, for international callers, and for unknown callers. Anything the system can't confidently place as single-party defaults to requiring the acknowledgment.
International and unidentifiable callers default to requiring consent
International (non-US) numbers require the acknowledgment under a GDPR posture. So do callers the
system can't place at all — an empty or unparseable caller ID, or a non-telephone identity such as a
SIP client: address. The gate is conservative by design: it fails closed toward asking for consent,
never toward silently recording.
Recording is opt-in first
Two things must both be true before a call is recorded: your workspace has enabled call recording (it is off by default), and the jurisdiction gate's acknowledgment requirement is satisfied.