What does Oregon SB 1546 do?

Oregon SB 1546 is a chatbot safety bill that passed the Oregon Legislature in March 2026 and is awaiting Governor Tina Kotek's signature. The bill is designed to regulate AI companions and chatbots — primarily targeting consumer-facing AI that mimics human relationships and could cause 'harmful conduct.' However, legal analysts have noted that the bill's language defining 'chatbot' and 'harmful conduct' is ambiguous and undefined in ways that could sweep broader than the Legislature intended. Professional services firms using client-facing AI tools for intake, FAQ assistance, or client portal guidance may fall within the bill's scope depending on how those definitions are implemented in regulation.

Does Oregon SB 1546 apply to law firms and accounting firms?

It depends on the scope of final regulation, which isn't yet determined. The bill's primary target is consumer-facing AI companions that simulate human relationships. But the definition of 'chatbot' in the bill is broad enough that legal analysts say it could cover any interactive AI system that responds to user queries — including law firm intake chatbots, accounting firm client portals with AI FAQ assistance, and consulting firm lead qualification bots. Firms in Oregon or serving Oregon-based clients should inventory any client-facing AI tools that involve dialogue, response, or guidance, and have their attorney review whether those tools qualify once the Governor acts on the bill.

How is Oregon SB 1546 different from Oregon HB 4154?

Oregon HB 4154 (already enacted) specifically addresses AI chatbot deception — it prohibits AI systems from claiming to be human and creates a private right of action for violations. Oregon SB 1546 goes further with a general chatbot safety framework targeting 'harmful conduct' by AI companions and conversational systems. Where HB 4154 is about disclosure (tell users they're talking to AI), SB 1546 is about conduct standards for the AI itself. Both are now Oregon law (SB 1546 pending signature) — and both could apply to client-facing AI tools at professional services firms.

What should a professional services firm in Oregon do right now about SB 1546?

Three steps before the bill is signed: (1) Inventory every client-facing tool that involves any form of conversational AI response — intake chatbots, client portals with AI assistance, FAQ bots, scheduling tools with natural-language interfaces. Any tool that 'responds' to client queries could be in scope. (2) Review the bill's current text with your attorney for how the 'chatbot' and 'harmful conduct' definitions apply to your specific tools. (3) Watch for Governor Kotek's action — if she signs the bill, implementation regulations will define the practical scope. If she sends it back for amendments, scope clarification may be incorporated. Keep the inventory you've built regardless — it will be useful for Oregon HB 4154 compliance as well.

Oregon SB 1546: Chatbot Compliance Guide

Q: Is this just an Oregon problem, or is this a broader regulatory pattern?

It's a pattern. Oregon SB 1546 is the latest in a wave of state chatbot and AI accountability bills with broad scope definitions. New York A 3411 (recently passed the legislature, awaiting Governor Hochul's signature) requires AI systems to warn users their outputs may be inaccurate. Oregon HB 4154 prohibits chatbot impersonation. New Hampshire SB 640 prohibits AI from performing licensed professional services without 'meaningful oversight.' Each bill targets a different harm, but together they form a regulatory architecture for AI in client-facing professional work. Professional services firms in multiple states should treat each new bill as a signal — the compliance infrastructure you build now (disclosure language, tool inventory, governance policy) applies across this entire wave, not just one state.

Oregon's SB 1546 chatbot safety bill passed the Oregon Legislature in March 2026 and is on Governor Tina Kotek's desk.

The bill is designed to regulate AI companions and chatbots — the kind that simulate human relationships or produce "harmful conduct." But the definitions matter, and legal analysts reviewing the bill's language have flagged a scope problem: the bill's definition of "chatbot" is ambiguous enough to cover far more than social AI companions.

If you're a professional services firm using any client-facing AI in Oregon — intake tools, client portal FAQ assistance, scheduling bots, any interactive AI response system — you need to know what this bill does and whether your tools fall within its scope.

Summary

Oregon SB 1546 passed the Legislature and awaits Governor Kotek's signature. The bill targets chatbots capable of causing "harmful conduct" — primarily consumer AI companions — but its scope language is broadly written in ways analysts say could apply to professional services client-facing AI tools. Oregon HB 4154 (already enacted) prohibits chatbot impersonation with a private right of action. SB 1546 adds a general conduct standard on top. Professional services firms in Oregon should inventory client-facing AI tools and review the bill's definitions with their attorney before the Governor acts.

What the Bill Does

SB 1546 establishes conduct requirements for AI chatbots — systems that engage users in dialogue, respond to queries, or provide guidance. The bill's primary concern is AI companions that form parasocial relationships with users and may lead to "harmful conduct." Think: AI systems marketed as relationship substitutes or mental health substitutes that may encourage self-harm.

The scope problem: Oregon's definition of "chatbot" in SB 1546 doesn't limit itself to social AI. It's written broadly, and legal analysts tracking state AI legislation — including the Transparency Coalition AI's March 2026 legislative update — have noted the definitional ambiguity.

Under the bill as written, any interactive AI system that responds to user queries could potentially qualify. Which means the analysis for professional services firms isn't "this doesn't apply to us" — it's "let's verify whether our specific tools fall within scope."

Oregon's AI Regulatory Landscape Is Expanding

SB 1546 isn't Oregon's first AI law affecting professional services firms. Oregon HB 4154, which is already enacted, addresses AI chatbot deception directly: it prohibits AI systems from claiming to be human and creates a private right of action for violations that produce damages.

That's a meaningful liability exposure for any firm whose client-facing AI tool doesn't clearly identify itself as AI. A law firm intake chatbot that uses a human name without disclosing it's AI could create a HB 4154 claim if a client suffers harm.

SB 1546 adds a layer on top of HB 4154. Where HB 4154 is about disclosure — tell users they're talking to AI — SB 1546 is about conduct standards for the AI system itself. The two bills together form a regulatory framework for client-facing conversational AI in Oregon.

What "Client-Facing AI" Actually Means Here

If you're a professional services firm, the tools to inventory before the Governor acts:

Law firms: Any intake chatbot on your website. Any client portal tool that answers questions via natural language (matter status, document requests, scheduling). Any AI FAQ assistant embedded in your site or client portal.

Accounting firms: Any client portal with AI-assisted responses. Any chatbot that answers tax-related questions before engagement. Any scheduling or intake bot that engages clients in dialogue before a human takes over.

Consulting and staffing firms: Lead qualification bots. Automated first-response systems that interact with prospective clients or candidates through dialogue. Any natural-language response tool in your intake or onboarding process.

Marketing agency owners: Any client-facing AI tool that manages communication workflows.

The test is simple: does the tool respond to a user query in natural language? If yes, it may qualify as a chatbot under SB 1546's broad definition.

Three Steps Before the Bill Is Signed

1. Build the inventory.

Pull a list of every AI tool your firm uses that involves client-facing dialogue, response, or guidance. Include tools embedded in your website, in client portals, in scheduling systems, and in any intake workflow. You need this list for SB 1546 compliance analysis. You'll also need it for Oregon HB 4154, for the broader chatbot disclosure requirements appearing in other states, and for your own AI governance policy.

2. Review the definitions with your attorney.

SB 1546's key undefined terms — "chatbot," "harmful conduct" — are the compliance questions your attorney needs to analyze against your specific tools. The bill is on the Governor's desk as of this writing. If she signs it, implementation regulations will define the practical scope. If she sends it back with scope clarification, you'll want to revisit the analysis. Either way, the inventory you built in step one is the foundation.

3. Check your existing AI disclosure language.

If you're already complying with Oregon HB 4154 (chatbot identification), review whether that same disclosure language satisfies the potential requirements under SB 1546. The two bills have different requirements — HB 4154 is about AI identity disclosure, SB 1546 is about conduct — but the implementation infrastructure (disclosure language, user-facing notifications, internal governance) overlaps.

The Broader Pattern Worth Watching

Oregon SB 1546 is the latest bill in a wave that is building a piecemeal regulatory architecture for AI in client-facing work.

New York A 3411 — recently passed the legislature, awaiting Governor Hochul's signature — requires AI systems to warn users their outputs may be inaccurate. New Hampshire SB 640 prohibits AI from performing licensed professional services without "meaningful oversight." Washington HB 1170 requires chatbot disclosure in consumer-facing AI systems. Each bill targets a different harm. Each has ambiguous scope language that may reach professional services firms.

The firms that are building compliance infrastructure piece by piece — tool inventory, governance policy, disclosure language, engagement letter AI clause — are not doing redundant work. They're building the same foundation each new state bill will require.

The firms that are waiting for a single clear federal framework won't get one before 2027 at the earliest. In the meantime, the state-by-state architecture keeps arriving.

Sources: Transparency Coalition AI, "AI Legislative Update — Oregon SB 1546" (March 2026); Oregon SB 1546 legislative text; Troutman Privacy Blog, "Proposed State AI Law Update, March 9, 2026".

Oregon Just Passed a Chatbot Safety Law That Could Apply to Your Client Intake Process