What the law actually says
The short version, as of mid 2026: around a dozen US states have enacted chatbot disclosure laws, with roughly twice that many pursuing them. California's has been enforceable since January 2026, Colorado's and Washington's arrive mid year, and underneath all fifty states sits the FTC Act, which treats a bot passing as a person as potentially deceptive. Europe went further still: from August 2026 the EU AI Act requires disclosure for any EU customer.
We are not your lawyers, and this landscape moves monthly. But the direction is not subtle. If your website has software talking to your customers, the era of letting them wonder is closing fast.
What the industry does about it
We scanned eleven AI receptionist and chat vendors this August. One of them scripts its greeting to say it is AI. One. The largest chat platform in the field has switched disclosure off by default and moved the liability to you, the business owner, in its terms.
Think about what that means when a customer finds out. Not if. When.
Why we disclose before anyone asks
Every living front office opens the same way, and the words are load bearing:
"I'm Dave's assistant. I'm an AI, and I work for Dave. Everything you write here, he reads himself, and he answers."
Two halves. The first half costs something: some visitors do relax more with a human, and we give that up on purpose. The second half is what most vendors never thought to build. Being told you are talking to software feels like a downgrade. Being told a named person reads every word of it is an upgrade. Most people write more honestly once they know that.
That is rule one of the Living Front Office Standard, which we publish so you can hold us to it. The AI label sits on the assistant's face, on screen, the whole time. Not in a footer. Not on page nine of a policy.
The question behind the question
Business owners who ask about disclosure are usually asking something warmer: will this thing embarrass me in front of my customers?
Fair question. Ours answers it with rules, not reassurance. It never diagnoses your customer's problem from a screen. It never quotes a price. It never promises on your behalf. It asks before it tells. And when the conversation ends, it ends with a booked next step, because a conversation left to go cold is its own kind of dishonesty.
A receptionist who lies about her name on the first phone call would not last the morning. Software should be held to the same bar.
What to do with this
If you already have a chat widget: open your own website tonight and ask it what it is. If it dodges, your customers have watched it dodge too. Then check whose name your state's new law puts on the fine.
If you are choosing one: make disclosure a buying criterion, not a hope. Ask the vendor to show you the exact opening line your customers will read, and who carries the liability if it stays silent.
And if you want the version that was built this way from the first line, the Standard is published, the desks are live, and you can walk up to one tonight and ask it yourself.