Skip down to the research record

Sales call recording: 10 wiretap exceptions that don't fit

Quota Forecast Editorial Team · Published · 12 min read

No exception in the Florida, Idaho, or Maryland excerpts covers a sales rep recording a deal call. Call recording tools are easy to switch on, and many teams assume that if a tool can record a call, the recording must be allowed. In the three statutes reviewed here, though, the rule starts from a prohibition on intercepting communications and then lists exceptions for particular people, roles, and situations.

This post reads the exceptions in those three state statutes. None of the exceptions names a sales team or a sales purpose. The reasons none of them fit matter more, because they show how to test any recording practice against a statute.

Key takeaways

  • Name the exception and the role it names before you rely on any recording rule.
  • Read the full wiretap section for each state where your team records calls, not an excerpt.
  • Keep a record of the state checked, the section read, and the decision.
  • Set the recording tool to match the decision before the first call is recorded.

Illustrative example: one rep's deal call

Take one plain case. A rep at a software company is on a video call with the operations director at a manufacturing firm. The software company sells a scheduling product, and the rep wants to record the call so the sales manager can review it later and the team can pull quotes for the proposal. The buyer has not been told the call is being recorded. The company uses a standard recording tool that starts on its own when a meeting begins.

Each section below returns to this call. Each time, we ask one question: does this exception cover what the rep is doing? The answer for each statute is the same, and the reasons for that answer are what matter.

What the Florida excerpts cover

Florida's wiretap provisions sit in the state's statutes on interception and disclosure of communications, and the Florida Legislature publishes the text online. The exceptions are each tied to a specific role or setting, and each is written as a narrow permission rather than a general one.

Read the excerpts in order, and notice that several exceptions apply "934.04-934.09," which means they are read together with neighboring provisions. A reader who stops at the exception itself will miss part of the rule.

The first excerpt covers an officer, employee, or agent of the Federal Communications Commission. That person may intercept a wire, oral, or electronic communication transmitted by radio, or use the information obtained, in the normal course of employment and in the commission's monitoring work under the federal communications chapter. The exception rests on a federal regulator's job. It does not rest on a business that wants a record of what its customers say.

The second covers an employee of a telephone company who intercepts a wire communication for the sole purpose of tracing where it came from. The interception must be requested by the recipient, and the recipient must allege that the communication is obscene, harassing, or threatening. A sales rep who wants a record of a prospect's call meets neither condition. The rep is not a telephone company employee, and the purpose is a deal record, not tracing an abusive call.

The third excerpt covers a fire station employing firefighters, and the fourth covers an agency operating an emergency telephone number "911" system. The text we have stops partway through both provisions, so this post cannot describe their full conditions. What the excerpts do show is that both are tied to emergency public services. Neither describes a commercial team, and neither would be read to reach a sales call.

The fifth excerpt covers a person protected under an active temporary or final injunction for repeat violence, sexual violence, or dating violence, or under another court-imposed prohibition of conduct toward that person. That person may intercept and record a communication received in violation of the injunction or order. The rep in our example is not a protected person, and nothing in the example involves a court order.

The sixth excerpt cross-references a provision describing a situation where no warrant or court order is required by law. It calls for a statement that all statutory requirements have been met, that the specified assistance is required, and that sets out how long the assistance is authorized and what it covers. That is a framework for help given to officials under a defined process. It does not describe a sales team recording its own calls.

Applied to the example, none of the Florida exceptions in these excerpts covers the rep's call. The federal monitoring, telephone company, emergency service, protected-person, and official-assistance provisions each fit specific people in specific situations, and the rep is not one of them.

What the Idaho excerpts cover

Idaho's wiretap chapter is in its state code, and the Idaho State Legislature page for section 18-6702 contains two exceptions that look a lot like the Florida ones. Of these, subsection (g) is the one a sales team might read as a general permission, which is why it deserves a closer look.

Subsection (f) makes it lawful for an employee of a telephone company to intercept a wire communication for the sole purpose of tracing its origin. The request can come from an appropriate law enforcement agency or from the recipient, and the recipient must allege that the communication is obscene, harassing, or threatening. Like the Florida version, this exception is about abusive calls and telephone company staff. It does not reach a rep's deal call.

Subsection (g) needs careful reading. It makes it lawful for an employee of a law enforcement agency, fire department, or ambulance service, while acting in the scope of his employment, and while a party to the communication, to intercept and record incoming wire or electronic communications. The phrase "while a party to the communication" is the part that catches attention. A sales rep is a party to a deal call, so it is tempting to read that phrase as a general permission to record.

It is not. The subsection names three kinds of employer, and a sales team is not one of them. The party-to-the-communication language adds a second condition on top of the first. It does not replace the list of who may rely on the exception. A reader who skips the employer list and goes straight to "party to the communication" has read the words in the wrong order.

Applied to the example, the rep is on the call, but the rep does not work for a law enforcement agency, a fire department, or an ambulance service. Subsection (g) does not apply, however natural the party-to-the-call reading feels.

What the Maryland excerpts cover

Maryland's exceptions appear in its wiretap statute, and the Maryland General Assembly's statute text sets out both excerpts we have. Both concern public safety and law enforcement, and each describes a specific job in a specific setting.

The first is paragraph (5). It makes it lawful for an officer, employee, or agent of a governmental emergency communications center to intercept a wire, oral, or electronic communication where that person is a party to a conversation concerning an emergency. Three features matter for a sales team. The person must work for a governmental emergency communications center. The person must be an officer, employee, or agent of that center. And the conversation must concern an emergency. A rep at a private software company is not part of a governmental emergency communications center, and a deal call is not a conversation about an emergency.

The second is paragraph (6)(i). It makes it lawful for law enforcement personnel to use body wires to intercept oral communications in a criminal investigation, if there is reasonable cause to believe an officer's safety may be in jeopardy. Again, the exception is for law enforcement in a particular setting with a particular risk. Nothing in it reaches a commercial team, and nothing in the rep's example describes a criminal investigation or a risk to an officer.

Applied to the example, the call is not an emergency, the rep does not work for a governmental emergency communications center, and nothing about the call involves law enforcement. Neither Maryland paragraph covers the recording.

Why none of them fit

Taken together, the three sets of excerpts share a pattern. Each exception names a role: federal communications monitors, telephone company employees, law enforcement, fire and ambulance staff, emergency communications centers, 911 agencies, and people protected by court orders. Each ties that role to a setting such as an emergency, a criminal investigation, an abusive call, or federal monitoring. None of the excerpts names a sales team, a sales purpose, or a commercial call.

That pattern is useful for revenue leaders for a practical reason. When a vendor, a manager, or an internal policy document says a recording is "allowed under a legal exception," ask two questions. Which exception is it? And which role does the exception name? If the answer is a role your sales reps do not hold, the exception is not doing the work. Recording may still be permitted under other parts of the same statute, or under a rule these excerpts do not show. But the exception someone cited is not the basis, and a policy built on it has no foundation.

The exceptions are also written to be narrow. A legislature that wanted to cover commercial recording could have named businesses or sales calls directly. Reading an exception as broader than its words is one of the easiest ways for a team to talk itself into a recording practice the statute does not support.

Where that leaves the deal call

The excerpts do not show that every recording of a deal call is unlawful, and they do not give the full picture of any one statute. The excerpts are partial in places. The Florida fire station and 911 provisions are cut off in the text we have, and the Florida cross-references point to provisions whose text is not reproduced here. A full statute, and any other law that applies, could change the analysis.

What the excerpts do tell you is what to stop assuming. Do not assume that because a rep is a party to the call, the rep is covered. Idaho's subsection (g) shows why that assumption fails: the party-to-the-communication language sits next to a list of employers, and the list controls who the exception helps. Do not assume the tool vendor has checked the law in every state where a prospect sits. Those are reasons to ask a lawyer before recording, not reasons to start recording and sort it out later.

The excerpts also leave open the questions that matter most to a sales team, including notice, consent, and how a multi-state call should be handled when the people on it are in different places. Those questions are answered, if at all, by the full statute, by the other law that applies, and in some cases by how courts have read the statute. None of that is in the excerpts, and none of it should be guessed at.

What to check before the next call is recorded

Use the example call to build a checklist. Work through it in order, and write down the answer at each step so the reasoning is visible later.

First, identify the statute that applies. The example call involves a rep in one place and a buyer in another. Which state's statute governs a call like that is a question for counsel. Do not decide it from where the rep's office is located alone, and do not decide it from where the tool's servers are located.

Second, read the full statute, not a summary. For each state where your team records calls, read the full section that covers interception and recording, along with the definitions it uses and the exceptions it lists. Pay attention to cross-references, because an exception may only make sense when read alongside the provisions it cross-references.

Third, check every exception against your team's actual roles. For the example call, the rep is not a telephone company employee, a law enforcement employee, a governmental emergency communications center employee, a fire or ambulance employee, or a person protected by a court order. Write that down next to each exception you checked, including the ones that obviously do not fit. The record is what a reviewer will look at later.

Fourth, decide on consent and notice with counsel. Build the answer into the recording script, the meeting invitation, or the consent step in the tool. Do not leave it in a rep's memory, because memory varies from rep to rep and from call to call.

Fifth, keep a record of the decision. Note which state's law was checked, which section was read, and what the team decided. For related reading on call records, see Call transcript record: 4 fields before a deal review. Revisit the record when the recording tool changes, when the team starts calling in a new state, or when the statute itself changes. A decision made once and never revisited quietly goes out of date.

Sixth, make the recording setting match the decision. If the answer is that a call may be recorded only with notice, the tool should give notice before recording starts, not after. If the answer is that a call should not be recorded at all, the automatic setting should be off for that call type. The policy and the tool need to say the same thing.

What to do with the example

Back to the example call. The rep wants to record it so the sales manager can review it later, and so the team can pull quotes for the proposal. None of the three sets of excerpts covers that purpose, so the team should not rely on any exception discussed here. The rep can still take careful notes, follow up in writing with a summary the buyer has seen, and use the notes for the proposal and the internal review. Those steps do not depend on any recording exception.

It is worth saying plainly why this matters to a revenue leader. A recording that turns out to be unauthorized creates risk for the company, for the rep, and for the deal itself. It can also damage the trust a sales team is trying to build with the buyer. For one state's recording penalty cases, see Montana recording penalties: 4 cases for a forecast call.

The exceptions in these excerpts were written for other people in other settings. Reading them carefully is the fastest way to see that, and it is why this post does not offer a shortcut. The rest of the answer comes from the full statute for each state where your team records, and from counsel who knows your deals, your customers, and where those customers are located. Build the recording practice on that answer, and keep a record of how you got there.

The next step you can take today is to pull the full wiretap section for each state where your team records calls and list every exception it names. Bring that list to counsel before the next call is recorded. Until counsel has answered the buyer-notice question, the call should not be recorded on the assumption that a statute covers it.

Frequently asked questions

Does a recording tool's default setting settle the question?

No. A tool that records automatically has made a technical choice, not a legal one.

Do the excerpts say whether the buyer must be told?

They do not say whether the buyer must be told or must agree, so that answer has to come from the full statute and from counsel.

General information, not legal or tax advice.

Sources