Do You Have to Tell Callers They're Talking to AI? HIPAA, BAAs & the Florida Rules for SW Florida Medical Practices
It's a Tuesday in season and the front desk at a Naples med spa is drowning. Two patients checking out, one line on hold, and the phone lighting up with a new lead who found you near Fifth Avenue South. You already know an AI receptionist could catch those calls at 7pm and on Sundays. But you're in healthcare, so the first thought isn't "great," it's "wait, is that even allowed?" Good instinct. Let's walk through the rules the way one Southwest Florida operator would explain them to another.
Quick disclaimer before anything else. I build these systems, I'm not a lawyer, and this is not legal advice. Run anything that matters past your own counsel or compliance person. What follows is the plain-English version of the questions medical and med-spa owners in Fort Myers, Cape Coral, and Naples actually ask me before they put an AI on their phones.
Do you have to tell callers they're talking to AI?
The honest answer to do I have to tell callers they are talking to AI in Florida is: there's no single federal law that forces a "you are now speaking with a bot" script on an inbound service call. If a patient calls your office and an AI assistant answers to book them, no statute today mandates a specific disclosure line for that interaction.
That said, disclosure is the right practice, and it's the direction regulators are moving. The FTC has been cracking down on deceptive AI, and the FCC has already ruled that AI-generated voices count as "artificial" under the TCPA for outbound calls. A handful of states, California and Utah among them, have passed bot-disclosure rules. The trend line is obvious, and hiding the ball erodes patient trust anyway.
So we don't hide it. Our AI phone assistant, Leo, is designed to identify itself as an AI assistant on a recorded line, right at hello. Patients almost never mind. What they mind is calling at 6pm and getting voicemail. You can hear exactly how that intro sounds by calling Leo at 239-323-1887 or trying the 30-second demo.
Florida records calls under two-party consent
This is the one that trips people up. Florida is a two-party, really all-party, consent state for recording. Under Fla. Stat. 934.03, you generally can't record a call where the other person has a reasonable expectation of privacy unless everyone on the line consents. This isn't legal advice, so confirm the specifics with your own counsel.
AI receptionists usually record and transcribe calls, because that's how they book accurately and update your CRM. The recording is generally fine as long as you disclose it up front. The standard practice is a short recorded-line notice at the start of the call, the same "this call may be recorded" line you've heard a thousand times. Leo bundles the AI disclosure and the recording notice into one clean opening sentence, so both are addressed in the first few seconds. That one sentence is designed to handle both bases before the conversation starts.
HIPAA, BAAs, and keeping PHI out of texts
If a vendor is going to handle patient information, HIPAA treats them as a "business associate," and they have to sign a Business Associate Agreement (BAA) with your practice. No BAA, no patient data. That's the bright line. Any AI vendor that shrugs at the word BAA should not be anywhere near your phones.
Texting is where a lot of well-meaning offices slip. Protected health information does not belong in an SMS body. We use a doorbell pattern: the text nudges the patient to call back or tap a secure link, it never states why they're being contacted or anything clinical. The message is the doorbell, not the conversation. Our texting vendor signs a BAA, and the clinical detail stays inside the systems built to hold it.
What should you ask any AI vendor before you hand over your front line? Four things:
- Will you sign a BAA? If the answer is no or "what's that," walk.
- Where does patient data live, and who can see it? Ask about storage, access controls, and encryption.
- Does anything clinical ever go out in a text? It shouldn't, ever.
- Is this built into my system or a separate silo? Two-way sync with your calendar and PMS beats one more disconnected tool.
FTSA and TCPA: replying to a caller is not a cold blast
Florida has its own mini-TCPA, the Florida Telephone Solicitation Act (FTSA), stacked on top of the federal TCPA. Both govern automated sales calls and texts. The distinction most owners miss is the gap between blasting a marketing text to a purchased list and texting back a patient who just called your office.
A reply to someone who initiated contact is customer-initiated communication, not an unsolicited sales solicitation. Confirming an appointment, sending a callback nudge, or answering a question they just asked is service, and it's a different legal animal from a cold promo. Marketing texts, the "book your Botox special" kind, are where you need prior written consent, and every message honors STOP the instant someone sends it. We set the system up so service and marketing stay in their own lanes.
None of this is legal advice, and Florida's rules have been amended more than once. The design principle stays simple though: reply to people who contacted you, get written consent before you promote, honor opt-outs immediately.
This is the part a national app leaves you to figure out alone
Every point above is exactly what a self-serve AI answering app hands you a login for and wishes you luck. The BAA, the recorded-line script, the FTSA lanes, the two-way sync into your calendar, you're on your own to wire it up correctly. Miss one and the "cheap" tool gets expensive fast.
A local done-for-you setup handles it for you. We built this for Gulfside Living, a Southwest Florida nurse registry, and their AI front office took hours of weekly phone tag and manual scheduling off their front desk. You can read the Gulfside case study or see how we tailor it for skin and injectable practices on the med spa page.
Want us to check your own setup first? Grab a free audit, try the 30-second instant demo, or just call Leo at 239-323-1887 and hear a compliant AI receptionist answer the way yours could. Built into your system, in English and Spanish, catching the calls your front desk can't.
Never lose another lead.
See your own AI front office answer, follow up, and book — live in about a week.
Get a free audit →Frequently asked questions
Do I legally have to tell callers they're talking to an AI in Florida?
No single federal law requires a specific "you're speaking with a bot" disclosure on an inbound service call today, and Florida hasn't passed a general one either. But disclosure is best practice and where the FTC and FCC are heading. We design our AI receptionist, Leo, to identify itself as an AI assistant at the start of every call. This isn't legal advice, so check with your own counsel.
Can an AI receptionist record calls if Florida is a two-party consent state?
Generally yes, as long as everyone is notified. Under Fla. Stat. 934.03, Florida requires all-party consent to record a call where there's a reasonable expectation of privacy. The standard practice is a short recorded-line notice at the very start of the call. Leo bundles the AI disclosure and the "this call may be recorded" line into one opening sentence, so both are addressed in the first few seconds. This is general information, not legal advice.
Does an AI phone vendor need to sign a HIPAA BAA?
If the vendor handles patient information, HIPAA treats them as a business associate, and they must sign a Business Associate Agreement (BAA) with your practice. No BAA means no patient data, period. Ask any vendor directly whether they'll sign one, where data is stored, and who can access it. Our texting vendor signs a BAA, and we keep clinical detail out of SMS bodies entirely.
Is texting a patient back a violation of Florida's FTSA?
Replying to someone who just called you is customer-initiated service, not an unsolicited sales solicitation, so it's generally treated differently under the FTSA and federal TCPA. Marketing blasts, like promoting a Botox special, are where prior written consent matters most. Every message honors STOP immediately. We set the system so service texts and marketing texts stay in separate lanes. This is general information, not legal advice.
How is a done-for-you AI front office different from a self-serve app for compliance?
A national app hands you a login and leaves the BAA, recorded-line script, FTSA lanes, and calendar sync for you to wire up alone. We set all of it up and build it into your own GoHighLevel or PMS with true two-way sync. Most Southwest Florida practices go live in about a week, with texting builds taking one to three depending on carrier registration. Call Leo at 239-323-1887 or grab a free audit to start.
Keep going
Free tool: calculate what missed calls cost your practice · all guides. AI receptionist by city: Naples · Fort Myers · Cape Coral · Bonita Springs · Estero