AI Disclosure Requirements for Dental Practices in 2026

AI disclosure requirements dental practice owners now have to track weren't on anyone's radar five years ago. They're arriving state by state, and they land squarely on the kind of voice AI that answers your phones. If your front desk runs on an AI dental receptionist to book appointments, triage emergencies, or handle after-hours calls, the real question isn't whether a patient might eventually notice. It's whether the law makes you tell them, and if so, when and exactly how.

The short answer is: it depends entirely on your state, but at least 11 states had passed some form of AI-consumer disclosure law by mid-2026. One of them treats licensed healthcare providers as a special case with stricter rules than ordinary businesses. This guide covers what the law actually requires state by state, what patients expect even where no law exists yet, where in the call the disclosure belongs, and whether saying it out loud actually costs you bookings.

Do Dental Practices Have to Tell Patients They're Talking to AI?

Yes, in a growing number of states a dental practice must tell patients they are talking to AI, and federal law adds a baseline duty even where no state statute applies yet. The requirement usually kicks in the moment a caller could reasonably mistake the voice for a human receptionist.

The Federal Baseline

There is no single federal AI disclosure law for phone systems. Instead, the Federal Trade Commission enforces disclosure through its existing authority over deceptive practices, and it has been actively watching this space. The FTC opened an inquiry into AI chatbot operators in 2025, ordering several companies to explain how they disclose AI involvement and monitor what their chatbots tell users, a sign that vague disclosure language draws federal attention even without a specific state law. On top of that federal floor, states have started layering their own rules, and most of them share a similar shape: disclose clearly, disclose early, and don't bury it in fine print nobody reads. It's the same patchwork pattern dental practices already navigate with outbound texting under TCPA compliance rules for dental practices, just applied to inbound voice instead.

Why Scope Varies So Much

What varies enormously is scope. Some states only regulate "companion" chatbots built to simulate emotional relationships. Others regulate any AI system that interacts with consumers, full stop. A dental office answering machine sits in an odd middle zone that depends entirely on which state the practice operates in.

Don't assume you're exempt just because your AI only books appointments. Check your state's specific statute language, not a general headline about "chatbot laws." The definition section of the bill usually decides whether your setup counts.

Which States Have AI Disclosure Requirements for a Dental Practice Phone System?

California, Colorado, Utah, Washington, Oregon, and at least six other states now require some form of AI disclosure to consumers, though the rules differ sharply in scope. A dental practice with locations in more than one state may face different obligations at each address.

California's SB 243: Narrower Than It Sounds

The National Conference of State Legislatures tracks dozens of AI-related bills moving through statehouses every year, and disclosure requirements are one of the fastest-growing categories. California's SB 243 is the law most people mean when they say "the AI disclosure law," but it specifically targets companion chatbots built to sustain an ongoing relationship, and it carves out bots used only for customer service or business operations. Read literally, a scheduling-focused dental receptionist may fall outside SB 243 entirely. According to a 2026 legislative tracker from Conferbot, at least 78 chatbot-related bills had been introduced across 27 states by early 2026, though only a fraction became enforceable law with real disclosure teeth.

Colorado's Broader Consumer-Facing Standard

Colorado takes a broader approach. Its AI Act requires disclosure for any AI system intended to interact with consumers, unless it would already be obvious to a reasonable person. A synthetic voice booking a cleaning probably needs to say so; a simple touch-tone menu probably doesn't.

State-by-State Snapshot

• List every state where your practice has a physical location or takes calls from.
• Pull the actual bill text for each one instead of relying on a news summary.
• Default to the strictest applicable rule if you operate across state lines.

Does Utah's AI Policy Act Apply to a Dental AI Receptionist?

Yes, and it applies more strictly than the average state chatbot law. Utah's Artificial Intelligence Policy Act treats healthcare providers as a "regulated occupation," which means a Utah dental practice must proactively disclose AI use before a patient even has to ask.

Two-Tier Disclosure Under Utah Law

Utah was the first state to pass a general AI disclosure law, enacting it in 2024, and it splits obligations into two tiers. Ordinary businesses only have to disclose AI use if a customer clearly asks. But under Utah's Artificial Intelligence Policy Act, anyone providing services in a state-licensed regulated occupation, which includes dentistry, must disclose AI involvement up front, verbally at the start of the call, without waiting for the patient to bring it up. Violating an enforcement order under this chapter can carry a civil penalty of up to $5,000 per violation.

Why Healthcare Gets a Higher Bar

The logic behind the stricter standard is straightforward. A patient calling a dental office is often making decisions tied to their health, not just browsing a product catalog, so lawmakers decided the bar for transparency should sit higher.

If you operate in Utah, or any state that later copies this "regulated occupation" model, build the disclosure into the very first line of the call script. Waiting for the patient to ask isn't a safe fallback there.

What Do Patients Expect When They Call, Regardless of the Law?

Most patients expect honesty about who or what they're talking to, even when no law requires it. In a healthcare setting especially, patients tend to tolerate AI just fine as long as they never feel deceived about it after the fact.

What Patients Actually Mind

Trust in dentistry runs on continuity, not novelty. A Dental Economics piece on building trust with dental AI makes a point worth sitting with: patients who avoid the dentist already do so partly out of anxiety, and AI can either ease that or deepen it depending entirely on how transparently it's introduced. Nobody minds a computer answering the phone at 9pm. What patients mind is realizing later, from a friend or a slip in the conversation, that they thought they'd spoken to a person.

The Gap Between Legal Minimum and Patient Comfort

That gap between the law's minimum bar and a patient's actual comfort level is where most of the risk sits. A practice can technically comply with every statute and still create an awkward moment that costs it a returning patient.

• Say it plainly: "I'm an AI assistant" beats a vague "digital assistant" euphemism.
• Never let the AI imply it's a specific staff member by name.
• Make the human handoff option obvious within the first exchange.

Where in the Call Should the AI Disclosure Happen?

The AI disclosure belongs in the opening seconds of the call, before it collects any information or asks a scheduling question. Every state law with a timing requirement points the same direction: disclose first, then proceed.

Why Timing Matters

Burying the disclosure at the end of a long greeting defeats the purpose. If a patient has already given a birthdate or described a toothache before hearing "you're speaking with an AI assistant," the disclosure arrived too late to inform their decision to keep talking. Regulators consistently describe the standard as "clear and conspicuous," which rules out a fast, mumbled disclaimer squeezed between hold music and a menu of options.

A Script Pattern That Works

A workable script pattern looks like: identify the practice, identify the assistant as AI, then move into the reason for the call. Something like, "Thanks for calling Example Dental, this is our AI scheduling assistant. I can help you book, reschedule, or connect you with our team." That's roughly the shape most state guidance rewards.

• Place the disclosure in the first sentence, not buried mid-greeting.
• Repeat it if the call transfers back to AI after a human handoff.
• Keep the wording consistent across every location and every script version.

Does Disclosing AI Use Actually Lower Booking Rates?

No, disclosing AI use does not reliably lower booking rates when the disclosure is brief and the call flow works well. The bigger driver of lost bookings is a clunky, confusing AI experience, not the disclosure sentence itself.

Why the Fear Feels Real

It's a reasonable fear. A practice owner hears "disclosure requirement" and pictures patients hanging up the second they hear the word "AI." In practice, callers who want an appointment mostly care about getting one quickly, at a time that works, without repeating themselves three times. A brief, confident disclosure followed by fast, accurate scheduling tends to read as competence rather than a red flag.

What Actually Moves the Needle

Where booking rates actually drop is when the AI stumbles after the disclosure: mishearing a name, looping on the same question, or offering no clear way to reach a human. The disclosure itself is a two-second sentence. The scheduling experience that follows it is what patients remember.

Test your script both ways with a handful of real calls if you're nervous about it, then compare completion rates. Chances are the disclosure sentence isn't the variable worth worrying about.

What Happens if a Dental Practice Skips the AI Disclosure?

Skipping a required AI disclosure can trigger state penalties reaching thousands of dollars per violation, plus FTC exposure under deceptive practices law regardless of state. Some newer state laws even create a private right of action, meaning a patient could sue directly.

Penalty Exposure by the Numbers

Penalty structures vary, but they're not trivial. Utah's civil penalty for a Chapter 77 violation can run up to $5,000 per instance. Oregon's newer chatbot law goes further, allowing patients to recover $1,000 per violation through a private right of action, according to a 2026 legal analysis from Orrick, and other states set similar flat per-violation damages that add up fast across hundreds of calls a month. And because the FTC's authority doesn't depend on a specific state statute existing, a practice in a state with no chatbot law yet still isn't fully in the clear if its AI misleads callers about what they're talking to.

The Cost You Won't See on a Fine Schedule

There's also a reputational cost that never shows up on a penalty schedule. A local news story or an angry review about a dental office that "tricked" patients with a hidden AI receptionist does more lasting damage than most fines.

Treat the disclosure line as non-negotiable in every script version, including any custom scripts built for individual providers or locations. One clean, consistent sentence removes almost all of this risk.

How Should a Dental Practice Document Its AI Disclosure Compliance?

Document your AI disclosure compliance by saving the exact script text, the date each version went live, and which states or locations it applies to. If a regulator or patient ever raises a question, a paper trail beats a memory of what the AI "probably" said.

Why Documentation Settles Disputes

Most enforcement disputes over disclosure come down to a "did it say that or not" argument. A vendor changelog showing exactly when a script was updated, combined with a saved copy of the wording itself, resolves that argument before it starts. This matters more for a multi-location practice, where one office might be running an older script version than another without anyone noticing.

Aligning Scripts to the Law That Drives Them

It's also worth keeping a short internal note on which law drove each wording choice. If Utah requires proactive disclosure and Colorado's exception hinges on "obvious to a reasonable person," your documentation should show you actually considered the difference rather than using one script everywhere and hoping.

1. Keep a dated version history of every disclosure script.
2. Map each script version to the states or offices it covers.
3. Review the mapping any time a new state law passes.

AI disclosure requirements for dental practices will keep multiplying state by state, but the underlying principle rarely changes: say it early, say it plainly, and don't make a patient guess. Practices that treat the disclosure as a compliance checkbox tend to bury it. Practices that treat it as part of good patient communication tend to get it right without even checking a statute.

Start by pulling up your current AI receptionist script today and reading the first fifteen seconds out loud. If it doesn't clearly say "AI" before it asks for any personal information, that's the fix to make this week, not the next time a law changes.