Last updated 2026-07-09
TL;DR
Ohio is a one-party consent state under Ohio Revised Code 2933.52. Only one person on the call has to consent, and that person can be you. Federal TCPA rules layer on top for autodialed or marketing calls. Recording a call you are not a party to is a fourth-degree felony. And one-party consent will not save you if you record into a two-party state like Pennsylvania or California.
Is Ohio a one-party or two-party consent state for recording calls?
Ohio is a one-party consent state. Under Ohio Revised Code Section 2933.52, it is illegal to intercept a wire, oral, or electronic communication unless at least one party to that communication gave prior consent. [1] If you are on the call and you hit record, you are that consenting party. You do not have to tell the other person.
"One-party" is not the same as "no rules." Three exceptions matter a lot for outbound sales teams.
You cannot record a call you are not part of. If a manager secretly patches into a rep's call and records it without being an active participant, that is a third-party intercept, and it is a crime under Ohio law.
The one-party rule only covers Ohio law. If the person you are calling sits in a two-party (all-party) consent state like California, Maryland, or Pennsylvania, that state's law may also reach the call, and recording without a disclosure could expose you there. [2]
Federal law sits on top of all of it. The Electronic Communications Privacy Act, 18 U.S.C. 2511, mirrors one-party consent at the federal level, so an Ohio-to-Ohio call is generally clean. [3] But the TCPA, 47 U.S.C. 227, brings its own consent and disclosure rules the moment you add autodialing or a marketing pitch, and those rules have nothing to do with state wiretapping consent. [4]
What exactly does Ohio Revised Code 2933.52 say?
The statute defines "intercept" as the acquisition of the contents of any wire, oral, or electronic communication through the use of any electronic, mechanical, or other device. [1] Subsection (A) makes it a crime to intercept those communications. The consent exception lives in ORC 2933.52(B)(4), which permits interception when "one of the parties to the communication has given prior consent to the interception." [6]
The word "prior" carries weight. Courts read it to mean consent given before the recording starts, not after the fact. Start recording, then announce it, and you have technically violated the statute for everything captured before the announcement. In practice, Ohio prosecutors rarely chase business-to-business recording disputes, but the civil door stays open regardless.
ORC 2933.52 also reaches electronic communications, which pulls in text messages and email under Ohio's definitions. That matters for SMS teams. Capturing electronic messages without consent runs through the same framework as recording a voice call.
For how state wiretapping laws stack up nationally, see telephone call recording laws and is it against the law to record phone calls.
What are the penalties for illegal call recording in Ohio?
Illegal interception under ORC 2933.52 is a fourth-degree felony. In Ohio, a fourth-degree felony carries a prison term of 6 to 18 months and a fine of up to $5,000. [10] That is real exposure, not a citation.
The criminal side is only half of it. ORC 2933.65 creates a civil cause of action. Someone whose communication was illegally intercepted can sue for the greater of actual damages or $200 per day of violation, with a $10,000 minimum, plus punitive damages, attorney fees, and litigation costs. [1] Class actions are possible in theory, though Ohio has not produced the flood of state-wiretapping class litigation that California has.
Here is the penalty structure in one view.
| Violation type | Statute | Maximum penalty |
|---|---|---|
| Criminal interception (no consent) | ORC 2933.52 | Felony 4, up to 18 months prison + $5,000 fine |
| Civil damages (illegal intercept) | ORC 2933.65 | Greater of actual damages or $10,000 minimum |
| Federal ECPA criminal violation | 18 U.S.C. 2511 | Up to 5 years federal prison |
| TCPA per-call violation (marketing) | 47 U.S.C. 227 | $500 to $1,500 per call |
The TCPA row is about placing the call without proper consent, not about recording it. But an outbound sales call triggers both bodies of law at once. Getting the recording right does nothing for a broken TCPA process, and vice versa.
Do you need to tell callers you are recording the call in Ohio?
Legally, no. Ohio's one-party consent rule does not require you to tell the other party you are recording. [1] You consent for yourself, and the statute is satisfied.
"Legally allowed" and "strategically smart" are different questions. Plenty of outbound teams announce recording anyway, for good reasons.
Disclosure changes behavior on both ends. Reps stay on script. Prospects treat the conversation more seriously.
It also solves your cross-state problem in one sentence. California, Maryland, Pennsylvania, and roughly nine other states require all parties to consent or at least be notified. [2] If you dial a national list, you often will not know where a given lead sits. Announcing on every call is the cheapest fix there is.
The FTC Telemarketing Sales Rule already forces identification and disclosure at the start of many outbound telemarketing calls, and FCC rules add more for certain call types. [9] ORC 2933.52 does not erase any of that.
A one-line notice at the top of the call, something like "This call may be recorded for quality and compliance purposes," costs nothing and removes most of the risk before the prospect says a word.
How does federal TCPA law interact with Ohio's recording rules?
The TCPA, 47 U.S.C. 227, governs whether you can make the call at all. Ohio's wiretapping law governs whether you can record it. Two separate tracks, and you have to clear both. [4]
For outbound teams, the overlap shows up in a few concrete places.
Consent stacking. The TCPA requires prior express written consent before you place autodialed or prerecorded marketing calls to cell phones. [4] That consent is a different animal from recording consent. A lead who gave you TCPA consent did not consent to being recorded, and the reverse holds too.
Prerecorded messages. Drop a ringless voicemail or a prerecorded message into your outbound flow and you are deep in TCPA territory. FCC rules require prior express written consent for prerecorded calls to wireless numbers. [5] Whether you are separately "recording" a prerecorded call is a different question, but these tactics sit close together in any compliance review.
Recordings as evidence. TCPA defendants often reach for call recordings to prove what was said, either to show consent or to document disclosures. If that recording was made illegally under ORC 2933.52, you have manufactured evidence you cannot use and liability you cannot shake off.
For the full statute, tcpa law covers it in detail. For the state-by-state recording map, recorded phone call laws pairs well with this piece.
What happens when you record a call from Ohio into another state?
This is the trap that catches outbound teams most. Your reps sit in Ohio. Your leads sit everywhere.
Ohio's one-party rule protects you under Ohio law. The law of the state where the other party sits may apply too, especially where that state takes an aggressive extraterritorial view. The working rule in U.S. courts is that the stricter standard governs. Dial into California (two-party), Maryland (two-party), or Pennsylvania (all-party), and those laws can reach your call even though you placed it from Columbus. [2]
Courts have not settled the choice-of-law question cleanly. Some federal circuits look at where the recording device sits. Others look at where all parties are located. The 6th Circuit, which covers Ohio, has handled wiretapping cases but has not drawn a bright line that shields every Ohio-origin recording from other states' laws. [8]
The answer most compliance attorneys land on is simple: disclose on every call, or segment your dialing lists by state and handle two-party states separately. For most small teams, disclosure is cheaper than segmentation.
Before you dial into neighboring markets, indiana call recording laws and pa call recording laws are worth a read.
Can employers in Ohio record employee calls without telling them?
Yes, with conditions. Ohio's one-party consent rule applies here too. If the employer is a party to the call (a supervisor is on the line, say), one-party consent is satisfied. [1]
The more common setup is a call-monitoring system with no human supervisor listening live. Courts have generally allowed this under the "business extension" doctrine drawn from federal ECPA, which permits interception in the ordinary course of business using equipment furnished by the carrier or employer. [3] Ohio courts have applied it.
Quality-assurance recording in call centers is standard practice and generally protected under this doctrine. The equipment has to be used in the ordinary course of business, and limits exist. Recording calls between employees and union representatives, for one, opens separate labor-law issues.
Any employer running an outbound sales floor should have a written policy that employees read and acknowledge. Ohio law does not require it. You do it because it removes ambiguity and kills the argument that an employee reasonably expected the call was private.
Are there any exceptions to Ohio's call recording consent requirement?
ORC 2933.52(B) lists several. The ones that matter for outbound teams:
Consent. One party consents, as covered above. [1] This is the exception legitimate businesses rely on.
Law enforcement. Police with a valid court order can intercept communications. Not your concern as a sales operation.
Provider monitoring. Communications providers can monitor for service quality and fraud prevention as part of running their network.
Publicly accessible communications. If a communication is broadcast publicly, interception is permitted.
None of these hand businesses a carve-out to record for their own convenience with nobody on the call aware. The one-party consent exception is the one that carries commercial use.
One nuance: Ohio has no separate "pen register" statute piling extra requirements onto basic call metadata beyond ORC 2933.52. Some states treat call detail records differently from call content. In Ohio, the wiretapping statute governs content, and federal law handles most metadata collection.
How should outbound sales and marketing teams set up compliant call recording in Ohio?
Start with a call-level disclosure. A spoken recording notice at the top of every outbound call is the single highest-leverage step you can take. It covers you under Ohio law, cuts your risk on calls into two-party states, and builds a documented process.
Document your TCPA consent workflow on a separate track. Recording consent and TCPA calling consent are different obligations with different paper trails. LeadCompliant's compliance kit includes consent form templates and a state-by-state recording reference you can build your call guides around, worth a look before you lock your scripts.
Segment your lists if you have the data. If your CRM or data vendor gives you state of residence, flag the all-party states: California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington. [2] Those need an affirmative disclosure before you record.
Train reps on the rule, more than the script. A rep who understands why the disclosure exists is far less likely to skip it under pressure.
Audit your platform settings. Many VoIP and sales engagement tools (Salesforce, Salesloft, Gong, and the like) can play an automated disclosure at call start. Turn it on. It costs nothing and it creates a consistent record.
Store recordings securely with a retention and deletion schedule you actually follow. Most TCPA defense work runs on producing recordings as evidence. If you cannot find a recording from 18 months ago, it did not happen, at least not in a way that helps your defense. Set the retention period, write it down, and stick to it.
How does Ohio compare to neighboring states on call recording?
Ohio sits in a region of mostly one-party states, but its neighbors are not uniform. One of them will bite you.
| State | Consent standard | Disclosure required | Key statute |
|---|---|---|---|
| Ohio | One-party | No (recommended) | ORC 2933.52 |
| Indiana | One-party | No | IC 35-33.5-1 |
| Michigan | One-party | No | MCL 750.539c |
| Kentucky | One-party | No | KRS 526.010 |
| Pennsylvania | All-party | Yes | 18 Pa. C.S. 5703 |
| West Virginia | One-party | No | WV Code 62-1D-3 |
Pennsylvania is the outlier, and it borders Ohio directly. It requires all parties to consent to recording. [7] Dial into Pittsburgh, Philadelphia, or anywhere else in the state without a disclosure and you may have a problem under Pennsylvania law even while sitting in Columbus.
For how markets further out are structured, georgia call recording law and new york call recording law are useful comparisons, and arizona call recording laws covers the Southwest if your list stretches there.
What should you do if you receive a claim that you illegally recorded a call in Ohio?
Do not delete anything. That is step one. Destroying records after a claim arises can count as spoliation of evidence, which stacks a fresh, serious problem on top of the original claim.
Pull the relevant call logs and recordings and preserve them. Then call counsel. ORC 2933.65 civil claims run on a statute of limitations, and how you handle the first 48 hours often shapes the whole dispute.
When the claim involves a federal TCPA cause of action, and it often does when illegal recording rides alongside improper calling, know that TCPA class actions are the vehicle plaintiffs' attorneys favor. A single illegal call is rarely worth litigating. A pattern of undisclosed recordings across thousands of calls is exactly the case class counsel files.
Your defense usually turns on consent documentation. Show that the lead got a disclosure (verbal on the recording, written in a lead form, or both) and that your policy required disclosure on every call, and you are in far better shape than the team that relied on "Ohio is one-party, so we never told anyone."
For teams operating nationally, texas call recording laws and maryland call recording laws show the range of risk across your biggest markets.
Frequently asked questions
Is Ohio a one-party consent state for phone call recording?
Yes. Ohio Revised Code 2933.52 requires only one party to a call to consent to recording. If you are on the call and you record it, you are that consenting party, and you do not have to tell the other person under Ohio law. If the other party sits in a two-party state like California or Pennsylvania, that state's law may also apply and could require disclosure.
Do I have to tell someone I am recording a phone call in Ohio?
No. Ohio law does not require you to disclose that you are recording. One-party consent is enough. Most compliance attorneys still recommend announcing it if you make calls into other states, because roughly a dozen states require all parties to consent or be notified. A brief verbal notice at the start of every call clears the cross-state risk at zero cost.
What is the penalty for illegally recording a phone call in Ohio?
Illegal interception under ORC 2933.52 is a fourth-degree felony, carrying up to 18 months in prison and a $5,000 fine. The civil statute, ORC 2933.65, lets victims sue for the greater of actual damages or a $10,000 minimum, plus attorney fees and punitive damages. Federal ECPA violations add the possibility of up to five years in federal prison.
Can I record a business call in Ohio without telling the other party?
Yes, under Ohio's one-party consent rule. You consent for yourself by recording, and business calls work the same as personal ones. The main risk is an other party located in an all-party state such as Pennsylvania or California. Many businesses add a verbal disclosure to every call to handle that risk cleanly.
Can my employer record my calls at work in Ohio without telling me?
Generally yes. Under Ohio's one-party rule and the federal business extension doctrine (ECPA, 18 U.S.C. 2511), employers may monitor and record business calls in the ordinary course of business using company equipment. Best practice is a written employee policy acknowledging call monitoring, which removes ambiguity and undercuts any argument that employees had a reasonable privacy expectation on company systems.
Does Ohio's call recording law apply to text messages and online chats?
Yes. ORC 2933.52 covers wire, oral, and electronic communications, and electronic communications include text messages and most digital messaging. Intercepting those without at least one party's consent carries the same felony exposure as recording a voice call. Capturing texts for business purposes where you are a party to the conversation is generally permissible under the one-party framework.
What if I am in Ohio and the person I am calling is in California?
California is a two-party (all-party) consent state. California Penal Code 632 can apply to calls where a party is in California, regardless of where you dial from. Record without disclosing and you may be liable under California law even though Ohio would allow it. The safest fix is to announce recording on every call, which satisfies both states at once.
Does Ohio law require a beep tone when recording a call?
No. ORC 2933.52 does not require a beep tone or any audible signal during recording. Some FCC rules, particularly for certain operator services, do require a beep, but Ohio's general wiretapping statute has no such requirement. If you choose to disclose voluntarily, a verbal statement at the start is enough and more informative than a tone.
How long should I keep call recordings in Ohio for compliance purposes?
Ohio's wiretapping statute sets no required retention period. TCPA plaintiffs can sue up to four years from the date of violation under federal law. Most compliance attorneys suggest keeping outbound sales recordings for at least four years to support a defense if a TCPA or wiretapping claim arises. Set a written retention and deletion schedule, document it, and follow it consistently.
Is there a difference between Ohio call recording law and federal wiretapping law?
Both follow one-party consent, so for Ohio-to-Ohio calls the practical result is the same. The federal Electronic Communications Privacy Act (18 U.S.C. 2511) mirrors Ohio's standard. The difference is enforcement: federal ECPA carries penalties up to five years, while ORC 2933.52 is a state felony. You must comply with both, and the stricter standard governs when they conflict.
Can a recorded call be used as evidence in an Ohio court?
Yes, if it was lawfully made. A recording obtained with at least one-party consent under ORC 2933.52 is generally admissible. A recording made illegally may be suppressed, and the recording party faces separate criminal and civil exposure. Outbound teams often want recordings to prove consent or disclosures in TCPA disputes, which is one more reason to record lawfully every time.
Do Ohio call recording rules apply to VoIP and internet-based calls?
Yes. Ohio's definition of wire and electronic communications in ORC 2933.52 is broad enough to cover VoIP calls, and the FCC treats ECPA protections as applying to VoIP. If you make calls through a cloud phone system or sales engagement platform, the same one-party consent rule applies. Check your platform's recording disclosure settings and confirm they are enabled.
What is the difference between Ohio call recording law and Ohio eavesdropping law?
In Ohio, they are effectively the same statute. ORC 2933.52 covers interception of wire, oral, and electronic communications, which is the framework for both recording and eavesdropping. The line is whether you are a party to the call (one-party consent applies) or a third party secretly listening (no exception covers you, and you face felony liability).
Sources
- Ohio Legislature, Ohio Revised Code 2933.52 (interception of communications) and 2933.65 (civil damages): Ohio requires only one-party consent to record a communication; illegal interception is a fourth-degree felony with civil damages of at least $10,000
- National Conference of State Legislatures: Approximately a dozen states require all-party consent for call recording, including California, Maryland, and Pennsylvania
- U.S. Department of Justice, Electronic Communications Privacy Act (18 U.S.C. 2511): Federal ECPA permits interception with one-party consent and recognizes a business extension doctrine for employer monitoring
- Ohio Legislature, Ohio Revised Code 2933.52(B)(4): The consent exception in ORC 2933.52(B)(4) permits interception when one of the parties to the communication has given prior consent
- Pennsylvania General Assembly, 18 Pa. C.S. Section 5703 (Wiretapping and Electronic Surveillance Control Act): Pennsylvania requires all parties to a conversation to consent to recording, making it an all-party consent state
- U.S. Court of Appeals for the Sixth Circuit: The 6th Circuit, covering Ohio, has addressed wiretapping and interception standards without drawing a bright-line extraterritorial rule
- Federal Trade Commission, Telemarketing Sales Rule (16 CFR Part 310): FTC Telemarketing Sales Rule imposes identification and disclosure requirements at the start of outbound telemarketing calls
- Ohio Legislature, Ohio Revised Code 2929.14 (felony sentencing ranges): A fourth-degree felony in Ohio carries a definite prison term of 6 to 18 months