Georgia's AI Chatbot Bill Is Headed to the Governor — What Professional Services Firms Need to Do Before May 12

The timing requirements are specific:

• At the start of every conversation — disclosure must appear before the chatbot responds to the first substantive message
• Every three hours during an extended conversation — for any exchange that continues beyond an initial session
• Every hour when the user is a minor

This is not a "disclose once in the terms of service" approach. It's a recurring, in-conversation disclosure requirement designed to ensure users never forget they're talking to AI.

The bill does not prescribe exact language. It requires clear notification, not a specific phrase. But the standard is unambiguous: the user must be informed, proactively, that they are communicating with an AI system.

---

Why Professional Services Firms Need to Pay Attention

The reflex reaction to state AI legislation is often "that's for big tech, not my 15-person accounting firm." For SB 540, that reaction would be wrong.

Professional services firms deploy AI in client-facing tools more often than most owners realize. Walk through your firm's client experience and ask where these apply:

Intake chatbots. Many law firms, accounting firms, and consulting practices use chatbot tools embedded in their websites to qualify leads, schedule consultations, and gather intake information before a first meeting. If that chatbot is AI-powered — and many are — it falls under SB 540's scope when serving Georgia users.

FAQ assistants. Client portal tools that answer common questions about billing, document requirements, or case status. If the responses are generated or routed by AI rather than a human, this is covered.

Scheduling and onboarding flows. AI-powered scheduling tools that handle back-and-forth with clients to find appointment times and gather pre-meeting information.

Document request portals. Tools that use conversational AI to walk clients through document collection, especially common in accounting and financial advisory.

The key distinction: SB 540 applies to tools that communicate with clients or prospects, not tools used internally by your firm. An AI drafting assistant your associate uses to prepare briefs or reports is not covered. An AI tool your client interacts with to ask questions, submit documents, or schedule services is.

---

Georgia Is Not Alone — But It Is One of the Strictest

By the time Kemp signs or vetoes SB 540, Georgia will have joined a significant wave of state-level AI chatbot regulation.

State	Status	Requirement
California	Signed, in effect	Disclosure at start of interaction
Washington (SB 3368)	Signed April 1, 2026	Chatbot Response Liability Act — disclosure + accuracy obligations
Oregon (SB 1546)	Signed March 31, 2026	AI chatbot disclosure requirements
Georgia (SB 540)	Awaiting Kemp signature	Disclosure every 3 hours; every hour for minors

Georgia's every-three-hours requirement is the most specific recurring disclosure obligation in any chatbot law to date. It reflects a concern that users of extended AI interactions — ongoing client portal conversations, multi-session onboarding processes — may forget they're talking to AI if the disclosure only appears at session start.

For a professional services firm serving clients across multiple states: you're not managing one compliance regime. You're managing a patchwork that will only get more complex. As of April 2026, 78 chatbot-related bills are active across 27 states.

---

The Three-Question Disclosure Audit

Before May 12, run this audit on every AI tool your firm uses in client-facing workflows:

Question 1: Does this tool communicate directly with clients or prospects? If a client or prospect receives output from this tool — in any format — it's client-facing. If it only operates inside your firm's workflow (drafting, research, internal summaries), it's not covered.

Question 2: Does the tool currently disclose its AI nature at the start of each interaction? Check the opening message or interface. Does it explicitly state that the user is communicating with an AI? Not "this chat may be monitored" or "our virtual assistant." The user needs to know they're talking to AI.

Question 3: Does the tool have a mechanism for recurring disclosure during extended conversations? If a client uses your intake tool across multiple messages over an hour, does the disclosure reappear? For Georgia compliance, it needs to. Check with your tool vendor whether this is configurable.

Most small professional services firms will complete this audit in 20-30 minutes. For each tool that fails questions 2 or 3, the immediate action is to contact the vendor and ask whether disclosure frequency is configurable, or to add a visible static disclosure banner to the tool's interface.

---

What to Do Right Now

This week — whether Kemp signs or not:

Identify every client-facing AI tool your firm deploys. Write the list down. This is your disclosure audit baseline.

For each tool, ask the vendor directly: "Does your tool disclose its AI nature at session start? Can disclosure be configured to repeat at intervals?" Get the answers in writing.

If Kemp signs before May 12:

Any client-facing AI tool serving Georgia-based users needs to have disclosure built in before the law takes effect. The implementation lead time for configuring an existing tool is typically days to two weeks. You have more time than you think — but less than if you wait until the signature hits the news.

Building new client-facing AI tools:

Disclose from the start. The compliance cost of adding disclosure to a new tool is zero. The compliance cost of retrofitting it is friction, vendor coordination, and — in states with enforcement infrastructure — potential liability. Build it in.

---

The Broader Signal

Georgia's legislature passed SB 540 with no significant opposition. Washington signed two AI bills on April 1. Oregon signed on March 31. The professional services AI disclosure wave is not theoretical or distant — it is happening, bill by bill, state by state, with specific requirements and specific timelines.

The professional services firms that will handle this wave without disruption are the ones that treat client-facing AI disclosure as infrastructure rather than compliance. One disclosure capability, configured properly, handles any state requirement as it passes.

The firms that treat it as a one-time state-specific compliance task will be doing this again in 90 days for the next bill on the list.

Build the capability once. Use it everywhere.