Last updated 2026-07-09

TL;DR
Washington requires consent from all parties before recording a private phone call. Under RCW 9.73.030, recording without consent is a class C felony and a civil violation worth up to $5,000 per recorded call. That applies to in-state calls, and likely applies when any party is in Washington. Businesses must announce recording before it starts, every time.
Is Washington a one-party or two-party (all-party) consent state for call recording?
Washington is an all-party consent state. Every person on the call must consent before you record it. [1]
This matters enormously for outbound sales and support teams. Most federal guidance under the Electronic Communications Privacy Act only requires one-party consent, meaning the person doing the recording can be their own consent. Washington rejects that standard entirely. If even one participant is in Washington and you record without telling everyone, you have a problem.
The controlling statute is RCW 9.73.030, which says it is unlawful to intercept or record any "private communication transmitted by telephone" without first obtaining the consent of all parties. [1] The word "all" is doing real work there. It is not enough that you know you are recording. The other party has to know and agree too.
Washington's standard is stricter than federal law and stricter than most states. For a side-by-side look at how state standards compare, see our overview of telephone call recording laws. If your team calls into multiple states, the safest default is always to follow Washington's all-party rule for every call. It costs you nothing extra and protects you everywhere.
What does RCW 9.73.030 actually say, and what does it cover?
RCW 9.73.030 is the core privacy statute. It prohibits intercepting or recording a "private communication" transmitted by telephone, telegraph, or radio without the prior consent of all parties. [1] It also bans using any device to amplify or record conversations without consent.
The statute text reads in part: "It shall be unlawful for any individual, partnership, corporation, association, or the state of Washington, its agencies, and political subdivisions to intercept, or record any: (a) Private communication transmitted by telephone, telegraph, radio, or other device between two or more individuals between points within or without the state by any device electronic or otherwise designed to record and/or transmit said communication regardless how such device is affixed to the telephone." [1]
A few things to pull out of that language. First, it covers communications "between points within or without the state," which means cross-state calls are potentially covered when a Washington party is involved. Courts have generally read this to mean that if one end of the call sits in Washington, the statute applies. Second, it says "any device," so recording software, call center platforms, and even screen-recording tools that capture audio all count. No carve-out exists for business use.
RCW 9.73.030 also reaches in-person conversations, beyond phone calls. For outbound calling teams, the telephone provision is the one that matters.
One nuance worth knowing: the law covers "private" communications. If a call is not private, consent requirements may not apply. Courts have not been generous with that exception. A call to a customer is almost always private. Do not count on that word to save you.
What are the penalties for recording a call without consent in Washington?
The penalties are serious and come from two directions: criminal and civil.
On the criminal side, violating RCW 9.73.030 is a class C felony under RCW 9.73.080. [2] A class C felony in Washington carries up to five years in prison and up to a $10,000 fine under RCW 9A.20.021. [9] Criminal prosecution of businesses for recording calls is rare in practice, but it is real exposure for individuals, including sales managers who set up recording policies.
On the civil side, RCW 9.73.060 gives any injured party a private right of action. The statute allows for actual damages, plus "a statutory penalty of five thousand dollars" per violation, plus attorneys' fees and litigation costs. [3] Note the $5,000 is per violation, not per lawsuit. Each recorded call without proper consent is its own violation. A campaign of 1,000 calls recorded without disclosure could theoretically generate $5,000,000 in statutory damages exposure before you factor in actual damages and fees.
Here is the comparison that should concern compliance teams:
| Penalty type | Amount | Source |
|---|---|---|
| Criminal (class C felony) | Up to $10,000 fine + up to 5 years | RCW 9.73.080 |
| Civil statutory damages | $5,000 per violation | RCW 9.73.060 |
| Attorneys' fees | Actual, paid by defendant | RCW 9.73.060 |
| TCPA federal overlay | Up to $1,500 per call (willful) | 47 U.S.C. § 227(b)(3) |
The TCPA does not directly regulate call recording. But if a call itself was placed without proper consent, you could face both TCPA exposure and Washington recording exposure from the same call. [4] That stacking is exactly why outbound teams need to treat these as connected risks, not separate buckets. For a broader picture of federal call rules, see our guide on TCPA law.
How do you get valid consent to record under Washington law?
Washington law does not require written consent. It requires that all parties know and agree to the recording before it happens. [1] Most businesses satisfy this with a verbal announcement at the start of the call.
The most common approach is a beep tone or a verbal disclosure. The beep tone method (a recurring tone every 15 seconds during a recorded call) is explicitly recognized as adequate notice under RCW 9.73.030(b). [1] If the called party keeps talking after hearing the beep, courts treat that as implied consent. This is the cheapest option for businesses that already have call recording enabled on their phone system.
The verbal announcement is more reliable and easier to prove. Something like "This call may be recorded for quality and training purposes," said before the substantive conversation begins, is generally enough. The key word is "before." You cannot record the first 30 seconds of a call, then announce you are recording. The consent has to precede the recording.
Do not assume a general disclosure in your website's terms of service covers you. Courts have not validated that approach under Washington law. If a person calls your inbound line, a recorded greeting announcing the recording is fine. If your agent calls a consumer outbound, the agent needs to say it live at the top of the call.
For calls with multiple parties, like a conference call with a Washington participant, everyone on the line needs to hear the disclosure and have the chance to object before recording starts. Drop someone into a recorded conference bridge without telling them and you are exposed.
Does Washington's law apply when only one party to the call is in Washington?
This is one of the genuinely unsettled questions in Washington recording law. The short answer: probably yes, and you should assume it applies.
RCW 9.73.030 covers communications "between points within or without the state." [1] Washington courts have read this broadly. The general rule most compliance attorneys follow is simple: if either party sits physically in Washington at the time of the call, Washington's all-party consent rule applies.
There is no clean federal preemption here. The ECPA sets a floor of one-party consent at the federal level, but it explicitly allows states to impose stricter rules. [5] Washington has done exactly that, and no federal law overrides it for intrastate or mixed-jurisdiction calls.
For outbound sales teams calling consumer lists, you often do not know where your called party is physically located. They may have a Texas area code but be sitting in a Seattle apartment. The only practical answer is all-party disclosure on every call. It is not expensive, and it removes the jurisdictional guesswork entirely.
If you want to see how other all-party states handle this same cross-border problem, the Maryland call recording laws analysis covers similar terrain, and Pennsylvania call recording laws offer another useful comparison.
Are there any exemptions to Washington's call recording consent rule?
Yes, but they are narrow and mostly irrelevant to private businesses doing outbound sales.
RCW 9.73.030 has explicit exceptions for certain law enforcement activities, emergency services providers recording 911 calls, and financial institutions recording trading communications under federal rules. [1] Some of these exceptions require a court order or prior legal authorization.
There is also an exception for a "common carrier" acting in its normal course of business to protect equipment or to investigate fraud or theft of service. This does not cover a typical sales team or contact center.
Washington courts have recognized a limited exception where both parties are clearly aware the call is being recorded by the nature of the system, like a prison phone system where every call is announced as recorded at the outset and the prisoner has signed an acknowledgment. That logic does not transfer to consumer sales calls.
One question teams ask often: does the one-party consent rule apply if the person recording is a participant in the call? No. Washington has expressly rejected the one-party consent rule. Even if you are one of the parties, you must get everyone else's consent. [1]
If your business operates in a sector with specific federal recording mandates (broker-dealers under FINRA, for example), those federal rules can create their own disclosure frameworks, but they do not eliminate the Washington consent requirement. You have to satisfy both.
Do Washington call recording rules apply to text messages and voicemail?
Text messages are a genuinely complicated area under RCW 9.73.030. The statute covers communications transmitted by "telephone, telegraph, radio, or other device." [1] Washington courts have not issued a definitive ruling on whether SMS messages fall within the statute, but the weight of legal commentary suggests they likely do. Most Washington-focused attorneys advise treating text messages as covered and not intercepting or storing them without disclosure.
Voicemail is different. Leaving a voicemail is not recording a conversation, because there is no real-time two-way communication being intercepted. The person calling leaves a message the recipient can choose to store. That said, if you are using a technology that intercepts a voicemail in transit before delivery, that is a different matter.
For outbound SMS campaigns, the bigger compliance risk is not Washington's recording statute but the TCPA's consent rules for automated or prerecorded messages to cell phones. Washington's recording law and the TCPA are separate frameworks. For your SMS obligations, the SMS compliance resources cover TCPA rules in detail.
For voicemail drops (ringless voicemail), the FCC has treated those as "calls" subject to TCPA requirements. Whether they also trigger Washington recording statute concerns is unsettled, but the safer position is to treat any recorded message delivered to a Washington number as requiring compliance with both frameworks.
How does Washington's law compare to federal law and other strict states?
Federal law under the Electronic Communications Privacy Act (18 U.S.C. § 2511) allows one-party consent for recording phone calls. [5] At the federal level, one participant, including the person doing the recording, can consent for themselves and that is enough. Washington is one of roughly 12 states that reject this standard.
Here is how Washington stacks up against key comparison states:
| State | Consent standard | Statutory damages | Criminal exposure |
|---|---|---|---|
| Washington | All-party | $5,000/violation | Class C felony |
| California | All-party | $5,000/violation | Up to $2,500 fine + 1 yr |
| Maryland | All-party | $10,000/violation | Misdemeanor |
| Pennsylvania | All-party | $1,000/violation | 2nd degree misdemeanor |
| New York | One-party | Varies | Misdemeanor |
| Texas | One-party | Actual damages | Class A misdemeanor |
| Federal (ECPA) | One-party | $10,000/violation | Up to 5 years |
Washington sits in the stricter camp. Maryland actually has higher statutory damages per violation, but Washington's felony classification stands out. Compare the New York and Texas standards (both one-party) to understand why your consent script needs to change based on where your called party sits. See our New York call recording law and Texas call recording laws guides for those specifics.
For a general overview of which states require all-party consent and which do not, see our article on is it against the law to record phone calls.
What should outbound sales teams actually do to comply with Washington recording laws?
The practical answer is simpler than the legal detail suggests. You need to do three things consistently.
First, disclose before you record. Every outbound call that might be recorded needs a verbal disclosure at the very start, before any substantive conversation. Train your reps to say it as the first sentence after the greeting. Put it in your script. Make it non-optional. Something clear like "Just so you know, this call is being recorded" is enough. You do not need legal language.
Second, configure your phone system to either require disclosure before recording starts or to play a beep tone. Most enterprise call center platforms (Five9, Genesys, NICE, RingCentral, etc.) can insert a beep or a disclosure announcement. Your IT or telephony vendor can set this up. If they cannot, find a vendor who can.
Third, document your consent process. Washington's civil penalty ($5,000 per call) is strict liability for the violation. But if you ever end up in litigation, you want to show a court that you had a policy, you trained on it, and your system enforced it. Keep records of your disclosure scripts, training materials, and the call recordings themselves (yes, the recordings are your proof).
If you want a ready-made starting framework, LeadCompliant's compliance kit includes a call recording disclosure checklist and a state-by-state consent matrix. Every team's situation is different, and this article is not legal advice. Talk to a licensed attorney before making policy decisions that affect your business.
For teams worried about the full picture of cold calling into Washington, pairing these recording rules with a solid DNC scrub and TCPA consent process is what closes the gap. Our guide on recorded phone call laws covers multi-state scenarios in more depth.
What happens if you get sued for violating Washington's call recording law?
The private right of action under RCW 9.73.060 is straightforward and plaintiff-friendly. [3] Any person whose communication was recorded without consent can sue. They do not have to prove actual harm to collect the $5,000 statutory penalty. They just have to prove the recording happened without their consent.
Plaintiffs' attorneys know this. Washington has seen a steady stream of recording consent cases, often filed alongside TCPA claims. The combination attracts plaintiffs' lawyers because the statutory damages are fixed, the liability is relatively easy to establish (the recording exists), and the defendant pays attorneys' fees.
Typical discovery in these cases involves handing over call recordings, which become evidence against you. The defendant's own recordings often prove the plaintiff's case. That is one reason to make sure your disclosure lands at the very start of every call, so the recording itself shows the disclosure before the conversation.
Settlements in Washington recording cases vary widely. A single-plaintiff case involving a consumer might settle somewhere between $2,500 and $15,000 depending on the number of calls and how strong the disclosure evidence is. Class action exposure is a different scale entirely. No good public data exists on average Washington recording class settlements specifically, but analogous California privacy class actions have produced settlements in the millions for large contact center operations.
If you receive a demand letter claiming a Washington recording violation, do not ignore it and do not respond without legal counsel. An experienced TCPA and privacy defense attorney can assess whether your disclosure method actually satisfied the statute. Sometimes it did and the demand is opportunistic. Sometimes it did not, and early resolution is cheaper than litigation.
Does Washington have any additional telephone privacy laws beyond RCW 9.73.030?
Yes. Washington has a cluster of telephone privacy statutes under chapter 9.73 RCW that outbound callers should know.
RCW 9.73.010 covers eavesdropping more broadly. [11] RCW 9.73.020 prohibits intercepting telegraphic communications. RCW 9.73.070 extends protections to cellular and cordless phone communications explicitly. [6] That last one matters because some older case law distinguished between traditional landline calls and mobile calls. Washington removed that ambiguity.
Washington also has the Consumer Protection Act (RCW 19.86), which can be used to bring unfair or deceptive business practice claims tied to consumer communications. [7] A CPA claim can allow treble damages (up to three times actual damages) on top of everything else, though those claims require more proof than a straight recording statute violation.
Separately, Washington passed the My Health My Data Act (HB 1155, enacted 2023), which created significant new obligations for businesses collecting consumer health data. [8] Washington does not yet have a broad, GDPR-style consumer privacy law in full effect for all businesses, but the health data law is real and enforceable. If your calls touch on health topics, you have an added layer to understand.
For outbound callers focused on recording compliance, RCW 9.73.030, 9.73.060, and 9.73.080 are the statutes that matter most, and the ones a plaintiff's lawyer will cite.
Frequently asked questions
Is Washington a two-party consent state for phone call recording?
Yes. Washington requires all-party consent under RCW 9.73.030, which means every person on the call must agree to the recording before it begins. The phrase "two-party consent" is common shorthand, but Washington's statute uses "all parties," which covers calls with three or more participants equally. No exceptions apply to ordinary business calls.
Can I record a phone call in Washington without telling the other person?
No. Recording a private telephone conversation in Washington without notifying all parties is a class C felony under RCW 9.73.080 and triggers a $5,000 civil penalty per violation under RCW 9.73.060. No exception allows secret recording by a participant. Even if you are on the call yourself, you must disclose the recording to everyone else.
What is the penalty for recording a call without consent in Washington state?
Civil liability is $5,000 per recorded call plus attorneys' fees and actual damages under RCW 9.73.060. Criminal liability under RCW 9.73.080 is a class C felony, carrying up to five years in prison and up to a $10,000 fine. Both tracks can apply to the same conduct. Class action plaintiffs can aggregate the $5,000 per-call penalty across an entire campaign.
Does the one-party consent rule apply to calls into Washington?
No. Federal law (ECPA) sets a one-party consent floor, but Washington has enacted a stricter standard. When a Washington resident is a party to a call, Washington's all-party rule applies regardless of where the recording party is located. Most compliance attorneys recommend applying Washington's standard to any call where the called party might be in Washington.
How do I disclose call recording to comply with Washington law?
Verbally announce the recording at the very beginning of the call, before any substantive conversation. A clear statement like "This call is being recorded" is sufficient. Alternatively, RCW 9.73.030 allows a recurring beep tone every 15 seconds as a substitute for verbal notice. Written disclosures in terms of service, by themselves, are not reliable for calls where live verbal notice is practical.
Does Washington's call recording law apply to text messages?
Washington courts have not issued a definitive ruling on SMS, but RCW 9.73.030's broad language covering "other device" communications creates real uncertainty. Most Washington privacy attorneys advise treating text messages as covered. Regardless, outbound SMS campaigns face significant TCPA consent obligations at the federal level that are well-settled and more immediately enforceable.
Can a Washington employee record a call with a customer in another state?
Yes, and Washington's consent rule likely still applies. The statute covers communications between points "within or without the state," meaning the other party's location in a one-party consent state does not automatically eliminate Washington's all-party requirement. The safest practice is to disclose recording on every call regardless of where the customer is located.
Does Washington's call recording law apply to inbound calls to my business?
Yes. If a Washington resident calls your business and you record it, you still need their consent. A recorded greeting at the start of your inbound line that announces recording, followed by the caller continuing the call, satisfies the consent requirement. The key is that the announcement plays before any substantive conversation and before recording actually begins.
Are there exemptions to Washington's recording consent rules for law enforcement?
Yes, but they are not available to private businesses. RCW 9.73.030 and related statutes contain exemptions for law enforcement acting under court order, 911 emergency recording systems, and certain communications monitoring by corrections facilities. There is no business-use exemption that allows private companies to record without all-party consent.
What does "private communication" mean under RCW 9.73.030?
Washington courts interpret "private communication" broadly. A call is private if the parties have a reasonable expectation it is not being monitored. Ordinary business calls, sales calls, and customer service calls are all private. Public statements made to large audiences or calls conducted over an open radio frequency have less protection, but these situations rarely arise in outbound sales contexts.
Does Washington's recording law cover conference calls and multi-party calls?
Yes. RCW 9.73.030 covers communications between "two or more individuals." Every participant in a conference call must consent before recording begins. If you add a Washington-based participant to a recorded conference bridge without announcing the recording at the time they join, that participant has not consented and you have a violation.
Can I use a call recording disclosure in my sales contract instead of announcing it on calls?
Contractual disclosures do not reliably satisfy Washington's call recording consent requirement for telephone conversations. The statute requires consent before the recording, and courts expect that consent to be informed and specific to the call being recorded. A buried clause in a contract signed weeks before a call is not the same as a disclosure at the start of that specific recorded conversation.
How does Washington's law compare to California's call recording law?
Both states require all-party consent and both have $5,000 statutory damages per violation. California's Penal Code Section 632 is better litigated, with more published case law. Washington's felony classification (class C felony) is arguably more serious than California's criminal penalty structure. Teams calling into both states should use an identical all-party disclosure script, since the consent requirements are functionally the same.
Sources
- Washington State Legislature, RCW 9.73.030 (Intercepting, recording, or divulging private communication): Washington requires consent of all parties before recording a private telephone communication; recurring beep tone every 15 seconds is accepted as notice
- Washington State Legislature, RCW 9.73.080 (Violation as class C felony): Violating RCW 9.73.030 is a class C felony in Washington state
- Washington State Legislature, RCW 9.73.060 (Civil action for violation): Civil remedy includes $5,000 statutory penalty per violation plus actual damages and attorneys' fees
- U.S. Department of Justice, Electronic Communications Privacy Act (18 U.S.C. § 2511): Federal ECPA sets one-party consent as the baseline standard; states may enact stricter consent requirements
- Washington State Legislature, RCW 9.73.070 (Cellular and cordless telephone communications): Washington's recording consent requirements explicitly extend to cellular and cordless telephone communications
- Washington State Legislature, RCW 19.86 (Consumer Protection Act): Washington Consumer Protection Act allows treble damages for unfair or deceptive business practices related to consumer communications
- Washington State Legislature, HB 1155 (My Health My Data Act, 2023): Washington enacted the My Health My Data Act in 2023 creating new obligations for businesses collecting health-related consumer data
- Washington State Legislature, RCW 9A.20.021 (Class C felony maximum penalties): Class C felony in Washington carries maximum penalties of five years imprisonment and $10,000 fine
- Washington State Legislature, RCW 9.73.010 (Eavesdropping defined): RCW 9.73.010 broadly defines eavesdropping and interception of private communications in Washington state