Call recording consent: why the state list you found is wrong

Depending on which guide you open, somewhere between eleven and thirteen states are described as requiring all-party consent to record a conversation. The lists overlap heavily and differ at the edges, and the differences are not sloppiness — they are real ambiguity being flattened into a format that cannot hold it.

We could publish our own list. It would rank, because that is the format this query rewards. It would also be one more confidently-formatted answer to a question that does not have one, and if a contractor relied on it and got it wrong, the format would be the reason.

Four things a row in a table has nowhere to put.

• In-person and electronic are sometimes different. Several states treat a recorded phone call and a recorded face-to-face conversation under different provisions. A single label per state hides that.
• The statutes predate the technology. Much of this law was written for wiretapping, and how it extends to a modern call platform is a question of case law that has moved differently in different states.
• “Consent” is defined differently. Where an announcement followed by continuing the call constitutes consent, and what the announcement has to say, is not uniform.
• Expectation of privacy often qualifies the rule. Some statutes only reach conversations the parties reasonably expected to be private, which is a judgment, not a lookup.

Most businesses that record calls land in the same place, and it is defensible for reasons that have nothing to do with memorising states.

• Announce on every call, regardless of geography. Uniform practice removes the question of whose law applies from your operations and puts it where it belongs — in a conversation with your lawyer, once.
• Make the announcement genuinely audible. Buried at the end of a menu tree, it is a formality. First thing, in plain words, it is a disclosure.
• Log that it played. The announcement existing in your configuration is not evidence it played on the call in question.
• Ask whether you need the recording at all. A transcript or structured call notes often serve the actual business purpose — dispute resolution, training, intake accuracy — with a fraction of the exposure. This is worth asking before buying a system that records by default.
• Check your own states properly. The Reporters Committee guide below is organised per state and maintained; it is a far better starting point than any summary table, including one we might write.

We do not record calls. Tensvia works on messaging — Instagram, Messenger, text, WhatsApp, email — and the exposure discussed here comes from phone systems, which is usually a separate vendor.

We write about it because it comes up in nearly every conversation with a contractor or shop owner, and because it illustrates the thing we care about: a compliance control that lives in a setting nobody verifies is not a control. Same argument as consent enforcement — if you cannot show where the check runs, you do not have one.