Skip down to the research record

Montana recording penalties: 4 cases for a forecast call

Quota Forecast Editorial Team · Published · 13 min read

A revenue leader who records forecast calls usually has a practical reason for it. A recording lets you check what a rep committed to, pull an exact quote for a deal review, and see where the forecast drifted from the pipeline. The legal question tends to surface later, often when someone asks whether the recording was allowed at all. Montana addresses that question in a criminal statute on privacy in communications. Its penalties depend on which part of the statute an act falls under and on how many prior convictions the person has. Before your team turns on a recorder for a forecast call, you should know what those penalties look like.

This post walks through four penalty cases in 45-8-213, MCA and applies each one to the same example call. It is general information, not legal advice. It is meant to help you see which questions need answers before the next call goes out.

The example call and the question it raises

Our example is a weekly forecast call at a private company. The revenue leader runs it over video with the sales team. A recording tool joins the meeting and, in this example, keeps the audio and a transcript so the leader can review what each rep committed to. The tool's help material describes how it gets in: "When the meeting begins, the Notetaker will join the waiting room to be allowed in by the meeting organizer." In practice, the organizer decides when the recorder enters the call.

Nobody on the call was asked in advance whether they minded being recorded, and nobody received a formal warning that the call was being recorded. The leader wants to know what penalty exposure looks like before the next call goes out, and the sensible starting point is the statute.

The statute starts with the offense itself. Its third subsection reads: "Except as provided in 69-6-104, a person commits the offense of violating privacy in communications if the person purposely intercepts an electronic communication." Two phrases matter for a call. The first is "purposely," and the second is "electronic communication." Neither term is defined in this post, and how a meeting recording maps onto them is one of the open questions in the plan below. The sentence also opens with a reference to 69-6-104, a section this post does not cover.

The penalty provisions treat subsections (1)(a) and (1)(b) as one group, and subsections (1)(d) and (1)(e) as another. Subsections (1)(a) through (1)(e) are not reproduced here, so this post cannot say which group the example call falls into. Each case below assumes the leader has been convicted for the call under one group, and then steps through the conviction count.

Every penalty in the quoted text is tied to a conviction count, not to how many recordings a team makes in a week. A team that records every call has no penalty rung at all until a conviction happens, because the count starts with the first conviction.

To keep the four cases comparable, the example call stays fixed. Only the conviction count and the group change. A real review would turn on the facts of each call, and any answer would need those facts.

Case 1: a first offense under (1)(d) or (1)(e)

The first case is the lightest in this set. The statute says: "A person convicted under subsection (1)(d) or (1)(e) is guilty of a misdemeanor for a first offense." Under that sentence, the leader, convicted for the first time under one of those subsections, is guilty of a misdemeanor. The sentence is short, and it is the only first-offense penalty quoted for this group.

That misdemeanor conviction becomes part of the record that a later offense will be measured against, which is why the count matters even at this step.

The quoted sentence gives no jail term and no fine for this first offense. If you have seen a dollar figure for a first misdemeanor somewhere else, treat it as unverified until it matches the statute. A number in a blog post, a vendor guide, or a forum reply does not stand in for the statute itself.

The label matters for what comes next. A first conviction in this group starts the count. In Case 4, a second conviction under (1)(d) or (1)(e) becomes a felony. Whether the count is kept separately for each group, or whether a conviction in one group counts toward the other, is an open question. Until that is answered, do not assume how the count works.

There is a practical lesson here too. Many leaders assume that a meeting tool's settings settle the question. The tool controls what it captures, and it can make recording easy to start. It does not change the statute, and the statute sets the penalty if a conviction happens. Keep the tool settings and the legal question on separate lists when you plan the next call, so that one never quietly answers the other.

Case 2: a second conviction under (1)(a) or (1)(b)

The second case moves to the other group. The penalty provision reads: "On a second conviction of subsection (1)(a) or (1)(b), a person shall be imprisoned in the county jail for a term not to exceed 1 year or be fined an amount not to exceed $1,000, or both." It sits in 45-8-213, MCA, the same section as the offense sentence.

Applied to the example, a second conviction in this group means a county jail term of up to 1 year, a fine of up to $1,000, or both. The ceiling language sets a maximum. The sentence gives no minimum, so it tells you the most a court can impose under this provision, not what a court will impose in a given case.

Two things are worth noting. First, "or both" means the court can impose a jail term, a fine, or both together. A reader who sees only the fine figure may miss the jail term entirely. Second, this sentence covers a second conviction, not a first one. This post gives no penalty for a first conviction under (1)(a) or (1)(b).

For a revenue leader, the practical point is that a second conviction in this group carries jail time as a possible penalty. That is a different category of exposure from a fine alone. It is the first point in this set where recording practice and personal exposure sit side by side, which is why the conviction count belongs in the planning conversation and not only in a legal memo.

Case 3: a third or later conviction under (1)(a) or (1)(b)

The third case keeps the same group and raises the count. The statute reads: "On a third or subsequent conviction of subsection (1)(a) or (1)(b), a person shall be imprisoned in the state prison for a term not to exceed 5 years or be fined an amount not to exceed $10,000, or both." It is the same section of 45-8-213, MCA, and the place of imprisonment is stated plainly.

In the example, a third conviction in this group means state prison for up to 5 years, a fine of up to $10,000, or both. The change from Case 2 is where the imprisonment happens: the county jail becomes the state prison. The fine ceiling rises from $1,000 to $10,000, and the jail ceiling rises from 1 year to 5 years. Side by side, the two provisions show how quickly the statute escalates within this group.

The words "third or subsequent" matter. The provision does not stop at a third conviction. A fourth or later conviction in this group falls under the same language. Nothing in the quote lowers the penalty as the count climbs.

This is where the stakes stop looking like an administrative issue for the team. A prison term is a different kind of exposure than a fine. This post does not cover how a prior conviction is counted, what must be proven, or how much time between convictions matters. Each of those points is on the question list in step 4 below.

Case 4: a second or later conviction under (1)(d) or (1)(e)

The fourth case is the other group, with a different ladder. The statute reads: "On a second or subsequent conviction of subsection (1)(d) or (1)(e), a person is guilty of a felony and shall be imprisoned for a term not to exceed 5 years or be fined an amount not to exceed $25,000, or both." The provision sits in the same section quoted in the first case.

In the example, the leader's first conviction under (1)(d) or (1)(e) was the misdemeanor from Case 1. A second conviction in the same group makes it a felony. The top of the range is up to 5 years of imprisonment, a fine of up to $25,000, or both. "Second or subsequent" means the felony label applies from the second conviction onward in this group.

Here are the ceilings from the cases side by side:

GroupConvictionImprisonment ceilingFine ceiling
(1)(a) or (1)(b)SecondCounty jail, up to 1 year$1,000
(1)(a) or (1)(b)Third or laterState prison, up to 5 years$10,000
(1)(d) or (1)(e)Second or laterFelony, up to 5 years$25,000

The fine ceiling for a second conviction in the (1)(d) or (1)(e) group is $25,000, which is more than double the $10,000 ceiling for a third conviction in the other group. The two ladders are separate, and this post does not say how a conviction in one group interacts with a conviction in the other, so do not add the counts together.

The felony label is the one to take most seriously. A felony is a different category of conviction from a misdemeanor. This post does not cover what else a felony could affect, such as other licenses, employment, or records. That gap is another item for step 4. A leader who sees "felony" in a statute should not treat it as a formatting detail in a planning document. It is the point where the recording question becomes a question about the leader's career.

The reading to avoid is that the felony line means the team should stop recording altogether. What the quoted penalties do show is that the second conviction in this group is where the stakes change, so the lawfulness of a recording should be settled well before the team reaches that point.

Illustrative example: one conviction, then a second

Suppose the leader is convicted once under (1)(d) or (1)(e). That first conviction is a misdemeanor and starts the count. If a second conviction follows in the same group, it is a felony with a ceiling of up to 5 years in prison, a fine, or both. Whether a conviction in the other group would change this count is one of the questions for step 4.

What the warning exemption covers

The sentence contains two carve-outs, and it reads: "This subsection does not apply to elected or appointed public officials or to public employees when the interception is done in the performance of official duty or to persons given warning of the interception." The sentence is part of 45-8-213, MCA, and it applies to the subsection it sits in, not to the whole statute.

Read it in two parts. The first covers elected or appointed public officials and public employees, but only when the interception is done in the performance of official duty. The example team works at a private company, so on those facts this part does not apply. A revenue team at a public agency has a different set of facts, and it should test whether the official-duty language fits its recordings.

The second part covers persons given warning of the interception. This is the part most relevant to a forecast call. What counts as a warning, how it must be given, and whether one given after the call starts is enough are all open questions. Treat the warning as one fact to document, not as a switch that settles the whole question. A line buried in a calendar invite may or may not count in the sense the statute uses.

Some recording tools are built with consent in mind. One vendor's help page says its feature "allows your team to gather recording consent from your leads and discuss billing information without sensitive details being included in transcripts." A feature like that can make the warning step easier to carry out. It does not decide whether the warning meets the statute's test, so the feature and the legal question stay separate.

The carve-out also refers to "this subsection." It is not explained here how the warning language works with subsections (1)(a) through (1)(e), or how the exception that opens subsection (3) fits in, which points to section 69-6-104. Until those points are answered, the carve-out is a reason to ask, not a reason to relax about recording.

The warning is one of the few things in the statute a team can act on directly. A warning that was given but cannot be shown later does little for the team, and a team that documents warnings without knowing what the statute counts as a warning may be documenting the wrong thing. Both halves need attention.

Before your next forecast call

Here is a short plan for a revenue leader who wants to be ready before the next call. Several of these steps are useful even while the legal questions are still open, and none of them asks you to settle those questions alone.

  1. Read the full statute. Start with the offense sentence in subsection (3), then read the penalty provisions quoted above, then read the subsections those quotes do not reach. The full text is in 45-8-213, MCA.

  2. List the calls you plan to record. Include the attendees, what the recording captures, who can reach the audio and transcript afterward, and how long those files stay. For the meeting settings themselves, see forecast call setup. Large audio files need handling of their own. One transcription provider's documentation puts it this way: "For files over 1 GB, see the Downsampling guide to reduce file size before redaction." A plan that cannot answer those questions is not ready for a recorder.

  3. Decide how attendees will be warned, and keep a record of when the warning was given. The statute's carve-out refers to persons given warning, so that record is what lets you show the warning was given. A record does not settle the question by itself, and it should not be treated as a legal opinion.

  4. Take the questions this post could not answer to a Montana lawyer, in one meeting, and ask for the answers in writing. Which subsection does the example fall under? Does section 69-6-104 change the answer? What counts as a warning? Are conviction counts kept separately for each group? How is a prior conviction counted, and what must be proven? Does time between convictions matter? What else could a felony conviction affect?

  5. Look at the recording tool's settings. Find out whether it announces itself when it joins, how it stores audio and transcripts, and who has access to them. For a related checklist on call records, see call transcript record. A different vendor's speech-to-text documentation, not the recording tool's, says: "The unredacted transcript is only returned when you explicitly set redact_pii_return_unredacted to true, and redact_pii must also be true (otherwise the request is rejected with a 400)." Keep those settings on a list separate from the legal question, so that a vendor default is never mistaken for an answer to the statute.

  6. Settle in advance what happens if someone on the call says they do not want to be recorded, and share that decision with the team. A leader who has to make that call in the middle of a forecast review will make it under pressure, and the answer may not match the plan.

The four cases are a starting point for that conversation. They show how the penalties climb with each conviction, and how the two groups of subsections follow different ladders. They do not tell you whether your team's recordings are lawful. That answer depends on facts about your own calls, and the sooner the question is on the calendar, the sooner the team can plan its recordings with confidence.

Sources