A support manager in Tampa pulls up a recorded call in a Gong review. The rep is good, the customer is annoyed, and the clip would make a perfect training example. Then someone asks where the customer was sitting when the call started. Sacramento. Nobody on the team knows whether the customer was told the call was being recorded.

According to recent reports, that small gap is what a recording policy exists to close. Recording sales and support calls is routine business, and the coaching value is real. The legal exposure sits in a few specific places, and a policy that names them in advance costs far less than a class action built around them.

The federal rule is the easy part. Under 18 U.S.C. § 2511(2)(d), a participant in a communication, or anyone acting with one participant's prior consent, can record it, so long as the aim is not a crime or a tort. That is one-party consent, and the Reporters Committee for Freedom of the Press (RCFP) calls it a floor that states may exceed.

Florida is the first place a Tampa team finds the floor is not the ceiling. The state appears on the RCFP list of primarily all-party states and on a widely used 2024 survey as well, so a team that records its own customers starts from the stricter side, and a read of how Florida law treats recorded conversations belongs ahead of any decision to switch recording on by default.

The map you need is not a map of your offices. It is a map of your callers. A sales team in Tampa that books demos with prospects in California, Illinois and Washington is subject to the argument about those states every time a prospect picks up, because courts have disagreed about whether the recorder's law or the recorded person's law governs. A CRM field for the caller's state, filled at booking, turns that argument into a lookup.

Two California statutes cover recorded calls, and they do different jobs.

Penal Code § 632 makes it an offence to record a confidential communication without the consent of all parties. A conversation is confidential when the surrounding facts suggest that someone on it wants it kept among the participants, and the statute carves out settings where the parties should expect that it could be overheard or recorded. A support call to a organization's published line, where a recorded message plays first, looks different from a private conversation.

In a recent development, penal Code § 632.7 is narrower in the devices it covers and wider in what it requires. It applies to recording communications between cellular and cordless phones, and between those and landlines, without all parties' consent, and it has no "confidential communication" element. A call centre that takes calls from customers' mobile phones is squarely inside that list. Smith v. LoanMe, Inc. (Cal. 2021) settled that the section binds the participants themselves, so the company on the line is covered along with any eavesdropper.

Sources indicate that the remedy is where the policy earns its keep. Section 637.2 gives the injured person a right to sue, and the plaintiff does not have to prove actual damages first. A customer who learns about a recording from a deposition notice can bring the claim without proving any loss.

In a recent development, kearney v. Salomon Smith Barney, Inc. (Cal. 2006) is the decision to read before writing a call-centre script, and its facts resemble the Tampa scene. A firm in Georgia, where the practice was lawful, taped its calls with California clients and said nothing. The California Supreme Court recognised a real conflict between the two states' laws, used comparative impairment to pick California's, and applied it to the firm's conduct going forward. For the earlier tapings it ordered neither damages nor restitution.

The line worth putting in a policy meeting comes from the same opinion. A business that tells every party to a call, at the very beginning, that it aims to record has not violated the provision. The fix is therefore a sentence at the start of the call, and recording can continue.

In a recent development, the counterpoint came from Nevada. Ditech Financial LLC v. Buckles (Nev. 2017) went the other way: NRS 200.620 had no application to an interstate call whose recording took place outside Nevada. That decision protects a recorder outside the state in a Nevada case, and it offers no comfort in a California one. The same logic applies to a team whose home-state rules, such as when Arizona businesses can record calls and meetings, say yes while the person on the other end sits somewhere stricter. Practitioners advise assuming the stricter state's law applies, and the case history explains why.

Some states split by how the conversation happens. Connecticut's criminal law is one-party, but its civil provision, Conn. Gen. Stat. § 52-570d, reaches phone recordings made without every party's consent. A spoken notice captured on the recording, or an automatic warning tone, avoids the liability. Nevada splits as well, with phone calls treated as all-party and in-person talk as one-party, per secondary sources. Oregon runs the other way according to RCFP: all-party for in-person conversations, one-party for phone calls.

Sources indicate that for a business, those splits matter because support and sales conversations move between channels in a single day. A video demo, a phone follow-up and an in-person onsite visit with the same client can fall under three different readings in the same state. A policy that says "we disclose at the start of every recorded interaction, in every channel" avoids the sorting exercise.

Michigan and Delaware deserve a mention because published lists disagree about them. Michigan's MCL 750.539c has been read by state and federal courts to give participants an exception, though the Michigan Supreme Court has not squarely decided the point. In Delaware, two provisions of Title 11 point different ways: § 2402 allows recording with one party's consent, and § 1335 has been read to demand everyone's. When two published lists disagree, the disclosure script is the cheapest answer.

A call-recording policy has two audiences, customers and employees, and the second one is where well-meaning policies overreach. Sales reps sometimes record their own calls on a phone. Support staff record a hostile caller to protect themselves. The instinct to ban all of it is understandable.

The National Labor Relations Board (NLRB) has made blanket bans legally risky. Its 2015 decision in Whole Foods Market, Inc. (363 NLRB No. 87) struck down rules that made any recording depend on management approval, since employees could take them as a ban on recording done as protected group activity. The Board stressed that employers may still keep recording rules if they are narrowly drawn, and the Second Circuit upheld the ruling without condemning every no-recording rule. Stericycle, Inc., 372 NLRB No. 113 (2023), supplies the current test: a work rule is presumed unlawful if an employee could reasonably read it as discouraging Section 7 activity, and the employer rebuts that only by showing a legitimate and substantial business interest that a narrower rule could not serve.

A staff rule should therefore describe what it protects (customer confidentiality, call-quality systems, the employer's own recording programme) and say what it leaves alone. "No recording of any kind, ever" is the drafting you want to avoid.

When I build one of these for a company, I start from the caller list and work backwards. The finished policy fits on two pages and covers six things:.

That last item has a live example. State consent rules get amended, and an amendment is the sort of event a named owner exists to catch. None of this replaces advice from a lawyer licensed where your callers live, and a short conversation with one is worth having before the script goes live.

Do one thing this week. Export last month's recorded calls, sort them by the caller's state, and mark every state where the script did not play. That list is your first draft of the policy, and it will tell you more than any template.

→ Read original article