An AI receptionist logs a transcript of every call it takes, by design — a human receptionist scribbling a phone message never did. That makes call-recording consent law relevant to almost any business adopting one, and the rules genuinely differ by state: Montana only requires that one party announce the recording (no reply needed), Washington's statute works the same way, Oregon treats phone calls as one-party consent but in-person conversations as all-party, and California requires actual consent from everyone on the line. Businesses answering calls from more than one of these states should build to the strictest rule that applies.
Why this question is suddenly everyone's problem
A front-desk employee who takes a message and hangs up isn't recording anything — there's nothing to consent to. An AI receptionist works differently by default: it transcribes the call so the owner can review it in a dashboard, feed it into a CRM, or check what a caller actually asked for. That's the core feature, not an add-on. It also means a two-person plumbing outfit that adopts an AI phone system becomes a business that records calls on day one, whether or not anyone thought of it that way — and every U.S. state and Canadian province has its own answer to who has to know about it.
The rule is not the same in Montana, Washington, Oregon, and California
Four jurisdictions in Skyline's own service footprint land in three different legal categories. Montana's privacy-in-communications law, read directly off the state legislature's own site, only bars recording by a "hidden" device when not all parties know about it — and one party announcing the recording, with no reply required from the other side, removes the violation entirely (MCA 45-8-213, mca.legmt.gov). Washington's statute uses almost the identical mechanic: consent "shall be considered obtained" the moment one party announces the call is about to be recorded, as long as that announcement is itself recorded (RCW 9.73.030, app.leg.wa.gov). Oregon splits the rule down the middle by communication type — phone and radio communications need consent from only one participant, while in-person conversations require every participant to be specifically informed (ORS 165.540(1)(a) and (1)(c), oregon.public.law). California is the strict outlier: its statute requires actual consent of all parties to a confidential communication, full stop, with no built-in announcement mechanism in the text itself (Penal Code §632, leginfo.legislature.ca.gov).
| State | Phone-call consent rule | What satisfies it | Statute |
|---|---|---|---|
| Montana | One party must know; a warning from either side removes the violation | An automated "this call may be recorded" message at the start of the call | MCA 45-8-213(2)(a)(iii) |
| Washington | All parties, but consent is "deemed obtained" by one party's announcement | Same recorded disclosure, played before substantive conversation starts | RCW 9.73.030(3) |
| Oregon | One participant's consent for phone/telecom calls | No announcement legally required for a phone call (in-person conversations are a separate, stricter rule) | ORS 165.540(1)(a) |
| California | Actual consent of all parties to a confidential communication | No statutory announcement shortcut — get real consent, don't just play a disclosure and hope | Penal Code §632 |
Montana's rule keeps getting flattened into "two-party consent"
Search "call recording laws for AI agents by state" and you'll find roundups — including one published on a competing AI-answering-service's own blog — that group Montana into a flat list of roughly a dozen "all-party consent" states alongside Washington and California, with no separate explanation of how Montana's rule actually operates. That's not wrong exactly, but it's misleading in a way that matters operationally: Montana doesn't require the other party to say yes, or to do anything at all. One party announces the recording; the statute's hidden-device element is gone the moment that happens (MCA 45-8-213(2)(a)(iii)). A Kalispell business configuring its AI receptionist to play a recording disclosure at the top of every call has fully satisfied Montana law before the caller says a word back. Lumping that in with California's actual-consent standard overstates what a Montana business needs to do.
The practical difference: an announcement vs. real consent
For a business running one AI phone number, the fix is the same regardless of which rule technically applies: play a short, clear disclosure — "this call may be recorded and transcribed" — before the conversation gets substantive, and keep that disclosure as part of the recorded call itself. That single habit satisfies Montana and Washington outright, exceeds what Oregon requires for phone calls, and gets closest to what California expects, even though California's statute doesn't spell out an announcement-equals-consent shortcut the way Washington's does. A business that takes calls from customers across state lines — a Spokane HVAC company fielding calls from Washington and Idaho, a Portland service business with California customers on vacation in Oregon — should build to the strictest rule in its actual call mix, not just the rule where its office sits.
- Configure the disclosure to play automatically at the start of every call, not just calls that sound sensitive — you don't know which rule applies until you know where the caller is.
- Make sure the disclosure itself gets captured in the recording or transcript, not just spoken and discarded — Washington's statute specifically requires the announcement to be part of what's recorded.
- If your customer base includes California callers, don't rely on the disclosure alone — its statute has no built-in announcement shortcut, so treat a caller who keeps talking after the disclosure as the practical (not guaranteed) standard, and avoid recording anything you'd call genuinely confidential without clearer consent.
- Canadian callers sit under a different, one-party-consent federal rule: the recipient of a call — your business — can consent on its own behalf under the Criminal Code's interception exception, without needing the caller's agreement (Criminal Code s.184(2)(a), laws-lois.justice.gc.ca).