AI Receptionist for Dental Practices: What to Hand Back to the Front Desk.

An AI receptionist for dental practices is sold to answer, book and remind around the clock. Here is what it should hand back to your front desk.

What an AI receptionist does at a dental office

Vendors describe the same core job: the tool answers calls, texts and web chat around the clock. It books, reschedules and confirms appointments in your practice-management software, sends reminders and recall messages, collects new-patient intake, and answers questions about hours and policies (Keragon). RevenueWell announced a standalone product of this kind in April 2026. RevenueWell says practices can choose between staff review before a booking is final and instant booking.

Every one of those descriptions comes from a company that sells one of these tools. None of it is independent testing. That doesn't make it wrong. It does make it marketing, so treat it as a list of things to ask about.

How many calls go unanswered

Vendor marketing is packed with missed-call numbers. The published ones run from about one in five to nearly four in ten, and they don't measure the same thing.

  • A 2020 DentistryIQ article says the average practice misses 20% of new-patient calls. It names no study, and its author is a marketing manager at Patient News, a vendor.
  • A Peerlogic case study reports 38% of inbound calls unanswered across 4,280 calls at 26 practices in one month, February 2026. Peerlogic sells the AI tool it reports on, and the page does not define "unanswered."

One counts new-patient calls only. The other counts every inbound call at one group of offices for one month. Neither is an independent study. Treat both as rough. Both also put a dollar figure on the loss. Those are vendor estimates.

Work out your number instead. Take the new-patient calls you missed last month, then multiply by the share that would have booked, then by what a new patient is worth to you. Use your call log for the first number.

What stays with the front desk

The vendors agree on where a person should step in. That is vendor guidance, not a regulator's.

  • Emergencies. Severe pain, swelling, trauma and bleeding should go to a team member or the on-call dentist, under rules you set. Keragon calls emergency routing the safety-critical feature and says to test it before going live. RevenueWell's buyer guide says the tool should gather details, assess urgency, escalate, and never give clinical advice.
  • Clinical questions. Anything that sounds like diagnosis or treatment advice belongs to your clinical staff, and RevenueWell lists clinical questions among its handoff triggers.
  • Complex insurance and billing. Vendors say the software can handle basic coverage questions and intake. RevenueWell lists complex billing issues as a handoff.
  • Sensitive or upset callers. Keragon says practices typically keep sensitive conversations with a person.
  • Anything the tool is unsure about. RevenueWell's guide says a well-designed system should transfer to staff when unsure instead of guessing.

Ask how the tool recognizes an emergency, and run test calls before it goes live. Live transfer to staff gets one line in RevenueWell's launch announcement, with nothing on hours, what happens if nobody picks up, or what context passes along. Ask about all three before you sign.

Does it connect to your practice-management software

The vendors' guides stress the same thing: two-way integration. The tool should read your live availability and write the appointment itself. A tool that cannot write to the schedule, Keragon says, "just creates a second inbox." RevenueWell's guide calls manual appointment relay instead of direct booking a dealbreaker.

For Dentrix and Dentrix Ascend, Henry Schein One runs an API Exchange. A vendor applies, passes a security assessment, is set up and tested, and is then listed. If a vendor says it works with Dentrix or Ascend, check Henry Schein One's approved vendor page, and ask why if it isn't there.

One more test: ask the vendor to reschedule an existing patient live in your system. It tests how the tool handles an existing patient record, not just a new booking. And ask what happens when your software can't be reached.

HIPAA and the business associate agreement

What follows is a reading of the regulation text, and it isn't legal advice. Have your counsel or compliance advisor confirm it.

Under 45 CFR 160.103, a business associate is a person who, acting on behalf of a covered entity, other than as an employee or other workforce member, creates, receives, maintains or transmits protected health information. Under that definition, a vendor that hears your patients' calls, names and appointment details is almost certainly one, so it should sign a business associate agreement (BAA) before patient data flows. The contract rules in 45 CFR 164.504(e) include:

  • permitted uses of the data
  • safeguards for electronic health information
  • a duty to report uses or disclosures the contract does not allow
  • the same restrictions for subcontractors
  • return or destruction of the data when the contract ends, if feasible
  • your right to terminate for a material violation

Put these to any vendor, and get the answers in writing:

  • Will you sign a BAA before any patient data flows, and can I read it first?
  • Who are your sub-processors, such as the voice, speech-to-text and language-model providers, and does the agreement bar using our patients' data to train models?
  • How long are recordings, transcripts and logs kept, who can see them, and how do we get them deleted?
  • How is the caller told the call is recorded and answered by AI, and has your counsel approved that script?
  • Do you hold a SOC 2 Type II report? Keragon calls it a strong additional signal. HIPAA does not require it.

A "HIPAA compliant" badge on a vendor page is a claim, not a certification. RevenueWell's launch announcement does not mention HIPAA or a BAA, though its separate buyer guide says a BAA should be standard.

Reminder texts have rules too

If the tool sends appointment reminders, the FCC exempts certain healthcare messages to mobile numbers from the prior-consent rule. The exemption only holds when conditions are met (47 CFR 64.1200(a)(9)(iv)). They include:

  • the message goes only to the number the patient provided
  • it names the provider and gives contact details
  • it is a permitted purpose such as an appointment confirmation or reminder, with no advertising or telemarketing
  • voice calls run about a minute or less and texts 160 characters or less
  • no more than one message a day and three a week
  • the provider complies with HIPAA privacy rules
  • no billing or other financial content
  • free to the patient
  • the patient can opt out easily, and the opt-out is honored immediately

Add a promotion or a balance reminder to a message and it falls outside that exemption.

Where these tools fall short

Published accounts of how these tools fail come from vendors or from commentators, not from independent measurement. One example is Nick Fotache of RevUp Dental, in a March 2025 post on Dentaltown titled "AI Dental Receptionists - The Latest Grift." It is commentary, not data.

What it costs

Vendors price per call, per minute or flat. RevenueWell's guide lists per-call pricing that scales unpredictably as a dealbreaker. Get the pricing method in writing. Ask what a busy month would cost.

Where this leaves your front desk

Judge an AI receptionist by what it hands back to you. A good one books and reminds reliably, writes to your schedule, signs a BAA, and sends anything clinical, urgent or upsetting to a person fast, with the details attached.

Tarsus Growth Company builds missed-call follow-up and other systems for dental and healthcare practices. If you want to talk through which calls and messages are worth automating, get in touch.

Keep reading.

All posts