Skip down to the research record

Recorded call interception: 3 Minnesota terms to check

Quota Forecast Editorial Team · Published · 12 min read

A recorded call is intercepted under Minnesota law when a device acquires its contents, and three definitions in section 626A.01 do most of the work.

Key takeaways

  • Check what the meeting tool saves (audio only, audio plus chat, a transcript or a recording of the screen) before you analyze anything.
  • Map how each participant joins, because the wire communication term depends on the audio path.
  • Record the facts that bear on each speaker's expectation, and make sure the recording is announced at the start of the call.
  • Treat the chat note on its own line: it is outside oral communication and may fall under the first term if the tool saved it.
  • Write down what is covered, what is uncertain and what is outside the definitions, then take the uncertain items to counsel.

Start with one recorded deal call

A revenue leader at a software company in Minnesota joins a video call with a buyer at a prospective customer. Before the meeting starts, the leader turns on the recording feature of the meeting tool. Partway through, a colleague on the team types a note into the chat panel, and the buyer's operations lead dials in from a desk phone. After the call, the leader asks a simple question: is this recording an interception under state law?

The question is harder than it sounds, because the answer depends on how the statute defines its words. This post uses that one call as its example from start to finish. It walks through the three definitions that do most of the work for a deal call. They come from section 626A.01 of the Minnesota Statutes, which defines the terms the state uses for interception. You can read the full section on the Revisor of Statutes site. By the end, you should be able to sort the parts of a call into the categories the statute uses, and know which questions to take to counsel.

The first term: intercept

The statute defines "intercept" this way:

> "Intercept" means the aural or other acquisition of the contents of any wire, electronic, or oral communication through the use of any electronic, mechanical, or other device.

Reading the definition in parts helps. "Aural or other acquisition" means taking in what is said or sent. "Contents" points at the substance of the message, not just the fact that a call took place. "Through the use of any electronic, mechanical, or other device" means the taking-in is done with equipment.

Apply that to the leader's call. The meeting tool's record function captures the audio from both the leader and the buyer. That is acquisition of contents through an electronic device, so the spoken part of the call fits the first term without much argument. In this example, the recording tool is the device.

The chat note is different, and the difference matters. The first term covers "wire, electronic, or oral" communications, so a typed message is not automatically outside it. A chat message can be a communication the statute reaches. But the first term does not decide which category the chat note belongs to. The other two terms do that work. The first term also has a practical limit: the recording captures the chat note only if the tool saves the chat. So the first question on any call is what the tool actually stored, not what the meeting looked like on screen.

The word "contents" also deserves a second look. The leader's meeting tool produces more than the words spoken. It may log who joined, when they joined, and how long they stayed. Those records describe the call without capturing what anyone said or typed. Whether they are "contents" under the definition is a separate question from the audio, and the definition's focus on contents is the reason to keep the two apart in your notes.

The same section has one more clause worth reading when you check your tools. It is a numbered item that refers to "that which is otherwise commonly used for a purpose or purposes other than overhearing or recording conversations." The item is about what a piece of equipment is used for, not about the call itself. Read the whole section before you apply it to a specific product, because a short quote can be easy to misapply.

The second term: wire communication

The statute defines "wire communication" this way:

> "Wire communication" means any aural transfer made in whole or in part through the use of facilities for the transmission of communications by the aid of wire, cable, or other like connection between the point of origin and the point of reception, including the use of such connection in a switching station.

Three phrases carry most of the weight. "Aural transfer" limits this term to spoken sound. "In whole or in part" means a call does not have to travel entirely over a wire to qualify, because part of the path can be enough. "Other like connection" is the open phrase. The statute names wire and cable, then adds "other like connection" without listing what else counts.

The definition looks at the path the audio travels, from the point of origin to the point of reception. In the leader's call, the operations lead's audio comes in over a desk phone. That is the easiest part of the call to place under this term, since a telephone line is a wire connection in the plain sense.

The two laptops joined over the internet are harder. Whether an internet connection between two computers is an "other like connection" is an open point. Do not assume an answer either way. Ask the meeting vendor how audio is carried between participants, and ask counsel whether that path fits the phrase. The question is where the audio travels, not where anyone is sitting.

The questions for the vendor are concrete. Does audio travel directly between the two laptops, or through a server the vendor runs? Is the phone participant's audio bridged into the same session, and if so, at what point? Does the tool store the audio and the chat in the same file, or in separate ones? Each answer changes what you have to analyze. Get the answers in writing, with the date you received them, so the analysis rests on something you can show later.

The second term also does not reach the chat note. It speaks only of an "aural transfer," and typed text is not aural. So the chat note falls outside this term even if the audio of the same call falls inside it.

The third term: oral communication

The statute defines "oral communication" this way:

> "Oral communication" means any oral communication uttered by a person exhibiting an expectation that such communication is not subject to interception under circumstances justifying such expectation, but the term does not include any electronic communication.

The definition has three conditions for the spoken part of a call. The words must be uttered by a person. That speaker must show an expectation that the communication is not subject to interception. And the circumstances must justify that expectation. The final clause then removes "any electronic communication" from the category entirely.

The test turns on facts, because the circumstances that justify an expectation differ from call to call. For the leader's call, those facts include who was on the line, whether the setup suggested privacy, whether the call was announced as recorded at the start, and whether the buyer's side knew the tool was running. Write these facts down for each call. They are the facts you would need in order to argue the question either way.

The expectation belongs to the person speaking, so the test can come out differently for the leader and for the operations lead. Whether a speaker was told the call was being recorded is one fact that may bear on that speaker's expectation, and it is a fact you can document. That is one reason the start of the call matters.

A practical point follows from this. If the expectation test depends on facts about each speaker, then a single line in a policy document cannot settle it for every call. The analysis has to be done call by call, or at least for each recording setup, with the facts written down at the time.

The chat note is simpler. The final clause excludes electronic communication from the definition of oral communication. So the typed note is not oral communication, whatever anyone expected. It can still be an electronic communication under the first term, if the tool captured it. That is why the chat note needs its own line in your analysis.

Putting the three terms together

For the leader's call, the analysis runs in four steps. Treat each one as a separate question, because a single call can fall partly inside the definitions and partly outside them.

First, the acquisition step. The recording tool acquires the audio and, if it saves them, the chat messages. Acquisition through a device is the first term, so the audio and any saved chat both need to be checked against it.

Second, the audio path. The operations lead's desk-phone audio is a plausible wire communication under the second term. The laptop-to-laptop audio depends on how the meeting platform carries it, and the statute's phrase "other like connection" is where that question lives.

Third, the spoken exchange. The leader's words and the buyer's words count as oral communications only if the expectation test is met for each speaker, under the circumstances of this call. Record the facts that bear on that test.

Fourth, the chat note. The note is excluded from oral communication by the final clause of that definition. It may still be an electronic communication captured under the first term, so check whether the tool saved it.

Once you have worked through these four steps, you have a clear list of what is covered, what is uncertain, and what is outside the definitions. The uncertain items are the ones to take to counsel, and the list should be written down so the reasoning can be reviewed later.

A written result for the leader's call might look like this in plain sentences. The recording tool acquires the spoken audio, so the first term is met for the audio. The operations lead's phone audio is a plausible wire communication, while the laptop audio depends on the vendor's answers. The spoken words of each speaker are oral communications only if the expectation test is met, and the facts for that test are listed in the call notes. The chat note is excluded from oral communication, and it is covered by the first term only if the tool saved it. Written this way, each conclusion points to the fact it depends on, and a reviewer can check the reasoning without rebuilding it from memory.

Illustrative example: sorting one call into four steps

Suppose a call has three participants. Two join from laptops and one joins from a desk phone, and the tool saves the audio and the chat in one file.

At step one, the tool's acquisition of the audio meets the first term, so the saved chat must be checked against that term too. At step two, the desk-phone audio is a plausible wire communication, while the laptop audio depends on the vendor's answers. At step three, each speaker's words count as oral communication only if the expectation test is met, so the call notes record the facts for each person. At step four, the chat is outside oral communication and may fall under the first term if the tool saved it.

The result is a short list of what is covered, what is uncertain and what is outside the definitions. The uncertain items go to counsel.

What these definitions do not settle

The three definitions tell you what the statute covers. They do not tell you what to do about it. Whether consent is needed, what notice a participant must receive, and what penalties apply are separate questions. Those questions have to be checked in the rest of the law, and they can change the answer for the leader's call even when the definitions point one way.

It also helps to be clear about what a "covered" result means. If the first term is met and the other terms are not, the recording is still a question for counsel, not a verdict. Equally, a finding that the spoken audio is an oral communication does not tell you whether the recording was allowed. The definitions sort the facts into categories. The rest of the law decides what follows from each category.

The definitions also do not reach past their own state. If your team records calls with people in other states, each state's definitions need a separate check. The terms in this post come from one state's statute, and a term that looks similar in another state may be defined differently. Do not carry the answer for Minnesota over to a call that involves a participant somewhere else without checking that state's text. For one example of another state's penalty rules, see Montana recording penalties.

Finally, statutes get amended. The version of section 626A.01 you read today is the one to check against, and a copy saved in a sales playbook last year may be out of date. Link to the official source, not to a summary of it, and confirm the text before you rely on it.

Before your next recording

Start with the tool. Find out exactly what it saves: audio only, audio plus chat, a transcript, or a recording of the screen. Each of those outputs gets its own check under the three terms. A forecast call setup checklist can help you list those settings.

Next, map how each participant joins. A desk phone, a mobile app and a browser can produce different audio paths. Write down which participants used which path, since the second term depends on it.

Then look at the start of the call. Decide how recording is announced and make sure the announcement is recorded in the meeting itself, so you have proof of what was said. The third term turns on the expectation of each speaker, and the start of the call is where that expectation is most visible.

When you speak with participants at the start, keep the wording plain and specific. Say that the call is being recorded, name the tool if it matters, and say whether the chat is kept. A short, consistent statement is easier to prove later than a vague remark, and it gives every speaker the same starting facts.

Keep one page of notes for each recording setup your team uses. The page should list the tool, what it saves, how participants join, how recording is announced, and the open questions for counsel. Reuse the page for similar calls, and update it when the tool or the statute changes.

Last, have counsel read the full text of section 626A.01 and the rest of the chapter before you set a team policy. The definitions in this post are the starting point for the analysis. The decision about how your team records should come from someone who can review the facts, the full law and the tool's actual setup together.

Next step today

Check your meeting tool today and write down what it saves. Keep that note with the call facts, since the first term depends on it.

Frequently asked questions

When does a recorded call count as an intercept?

A recorded call counts as an intercept when a device acquires the contents of a wire, electronic or oral communication, as the first term defines it.

Is a chat message oral communication?

No, because the definition of oral communication excludes any electronic communication, so a typed note falls outside it. It may still fall under the first term if the tool saved it.

Does the wire communication term cover a laptop call?

It is an open question: whether an internet connection between two computers is an "other like connection" depends on how the vendor carries the audio, so take it to counsel.

General information, not legal or tax advice.

Sources