AI Receptionist for Open Dental: Book Patients from Every Call

Yes. Open Dental has a documented API that dental offices enable themselves. Each integration uses two keys, a developer key and a customer key for your office, and remote access requires Open Dental's eConnector to be running. An AI receptionist can use it to look up patients and work with appointments, within the permissions your office grants.

What the AI receptionist does in Open Dental

Dental calls are mostly about time on the schedule, so the integration focuses there.

  • Finds existing patients by name, date of birth, and phone
  • Offers open times that match the visit type
  • Books new-patient, hygiene, and urgent visits
  • Adds a note about the reason for the visit and insurance details
  • Sends clinical questions and emergencies to your team

How the connection works

Every request to the Open Dental API carries two keys: a developer key that identifies the integration and a customer key unique to your office. Your office turns the API on in Open Dental's API setup, where keys can also be disabled.

  • Your office enables the API and can disable a key at any time
  • Remote access needs the eConnector running at your office
  • Open Dental also supports local and service API modes
  • Events can notify the receptionist when appointments change

HIPAA and patient privacy

Dental offices are usually HIPAA covered entities, so the AI receptionist vendor is a business associate.

  • A signed business associate agreement before any patient data flows
  • Identity checks before discussing appointments
  • Only the details each call needs
  • Encrypted recordings and transcripts with access controls

A typical call

An existing patient calls to book a cleaning. The receptionist confirms her name and date of birth, sees she is due for hygiene, and offers two openings with her usual hygienist.

  • Patient found in Open Dental
  • Hygiene time offered from the real schedule
  • Appointment created and confirmation texted
  • Insurance change noted for the front desk to verify

Limits to plan for

Schedules in dental offices carry a lot of unwritten rules, and the integration needs them written down.

  • Which operatories and providers take which visit types
  • How much time each procedure needs
  • Whether new patients book directly or request a time
  • Ask Open Dental and your integration partner about any API fees

Setup steps

An Open Dental integration usually takes four to eight weeks, mostly for schedule rules and testing.

  • Write booking rules by visit type, provider, and operatory
  • Sign the business associate agreement
  • Enable the API and eConnector, and add the customer key
  • Test bookings on real scenarios, then launch on overflow and after hours

Frequently asked questions

Does Open Dental have an API?

Yes. Open Dental documents an API that offices enable themselves. Requests use a developer key and a customer key for your office.

Does the API need the eConnector?

For remote access, yes: Open Dental states the office must have an eConnector running to use the Remote API.

Can the AI receptionist book new patients?

Yes, into the times and visit types you allow. Some offices prefer new-patient requests that the front desk confirms.

Is it HIPAA compliant?

It can be, with a signed business associate agreement, encryption, access controls, and minimum-necessary data collection. Your own policies matter too.

What about dental emergencies?

The receptionist follows the triage rules your dentist approves, offers urgent slots, and sends true emergencies to your on-call dentist or 911.

Sources