No AI receptionist, scribe or insurance checker is built into Open Dental, so every one is a third-party add-on. Phone tools usually connect through the API or a bridge to read and book appointments, insurance tools through a program link or the API, and many scribes only paste notes. Proof is a live test.
That last word matters more than any feature list. Vendor pages for Open Dental add-ons say "integrates with Open Dental" for very different things: a tool that books into your schedule in real time, a tool that reads a nightly copy, and a tool that sits beside the software and leaves your team to copy and paste. Ask which of the three you are buying before the demo starts, then make the vendor prove it on your own schedule.
What Open Dental itself ships, and what it does not
Open Dental's published fee list is the quickest way to see what the software supplies. As of November 2026 the page lists the support licence ($199 a month per location for the first 12 months, then $149 a month, covering up to three providers), per-provider fees above three providers ($20 a month each, hygienists not counted), a set of eServices such as eConfirmations, eClipboard and Web Sched, integrated texting, e-prescribing, and a single AI line: AI Image Analysis from BetterDiagnostics at $149 a month per location. That product reads dental images. It is not a phone agent, a note-taker or an eligibility checker.
So when a vendor says "AI for Open Dental", it means a separate company's product that talks to Open Dental. Three of the eServices are worth knowing because they overlap with what AI phone tools sell: eConfirmations ($25 a month per location), Web Sched New/Existing Patient ($75 a month per location) and Web Sched ASAP ($20 a month, free with Web Sched Recall). If your problem is "patients cannot book online", those may fix it without any AI at all. If the problem is "nobody answers the phone at 12:40 when the team is at lunch", they will not.
The fees page lists no API charge to the practice. Open Dental's API permissions page explains why: developers pay, per location, on four tiers that run from free (read-only, one request every five seconds) through $15 and $30 to $35 a month for almost every permission. A phone tool that books appointments needs more than the free read tier, so its price usually carries that cost. Ask in writing whether any Open Dental charge will reach you. And if a page tells you Open Dental itself is free, check which customers it means: the official fee page reserves free use for dental schools and a short list of markets, while a standard practice pays the per-location support licence.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowFour ways an add-on can "connect", and what each means for you
Open Dental's API is a REST interface (a standard way for software to ask another program for data and send changes back) that works with patients, appointments, claims and other records. The API documentation names three modes: Local, Service and Remote. It also says developers should have a Business Associate Agreement with the practices they serve and that developer support runs mainly through a forum, with phone support very limited. That last point is worth remembering: when something breaks between your vendor and Open Dental, your vendor is the one waiting in a forum queue.
| How it connects | What it can do | Typical failure | What to ask |
|---|---|---|---|
| API (read and write) | Look up a patient, find open slots, book, move or cancel, add a comms-log entry | Wrong operatory or provider on a booking; a service that must stay running goes down | Which appointment fields do you write? Show me a test booking in my schedule |
| Program link inside Open Dental | Opens the vendor tool from the patient chart; may pass patient details across | Data goes one way only; staff still re-key results | Which fields come back into the chart, and are they in the correct boxes? |
| Copy or export of the schedule | Read availability, send reminders, build lists | Stale data; double-booked slots | How often is it refreshed? What happens when a slot taken in the office is still offered? |
| No connection | Works beside Open Dental; staff paste notes or type bookings | Nothing, until someone forgets to paste | Is the price honest about the manual step? |
The modes matter for outages. Open Dental's API modes page says Local runs only while Open Dental is open on that workstation, Service runs continuously on the office's database server (which needs the eConnector), and Remote requests travel through Open Dental's cloud but still reach your database via the eConnector in the office. So for most add-ons, if the server is turned off for updates or a power cut, the integration stops. If someone hosts Open Dental for you, ask them who watches the eConnector. Either way, put a name on who gets the alert: the vendor, your IT provider or your office manager.
Phones: what an AI receptionist can honestly do inside Open Dental
AI phone tools vary most on write-back. Open Dental's own API documentation shows what a well-built one can do: a Slots method returns open time filtered by provider and operatory, creating an appointment needs the patient, the time and an operatory, and a separate method adds an entry to the patient's communication log (commlog). One detail catches tools out: if a booking arrives without a provider, Open Dental assigns the patient's primary provider, or the office default when there is none. So "good" looks like this: the tool reads providers and operatories (so it never invents a chair), writes the appointment with both set, and leaves a commlog note so your team can see what happened.
Weave, a dental phone and messaging platform, sells an AI Receptionist. Its product page says the receptionist books and reschedules straight into the calendar "for qualified Dental PMS only"; for everyone else it captures requests for the team to schedule. Neither that page nor Weave's integrations page names which practice systems qualify or what gets written back, so treat Open Dental support as a question, not a conclusion: ask Weave for its Open Dental integration documentation and a demo booking made in your own schedule. Our comparison of Weave, Zo and generic agents covers the phone products themselves.
For a smaller practice with no front-desk cover at lunch, the realistic wins are narrow ones: new-patient bookings into a fixed new-patient slot type, rescheduling that follows your rules, and a message to the office for anything else. Emergencies, pain and swelling go to a person; see after-hours dental answering and AI for that line. The contract terms (minutes, BAA, exit) are covered in AI voice agent contract terms for dentists.
A phone-booking test that exposes weak connections
Ask the vendor to run these five calls on your live system, with you watching Open Dental, not their dashboard:
- A new patient asks for the first Thursday after next, any dentist. Check the appointment type, provider and operatory the tool chose.
- An existing patient with a hyphenated surname asks to move a hygiene visit. Check it found the right person.
- A caller wants a time that is already taken in the office by a booking made two minutes ago. Check it is not offered.
- A parent books for two children back to back. Check both appear with the right guarantor.
- A caller says their face is swollen. Check it passes the call to staff with no advice and logs a note.
A sixth check costs nothing: after the calls, open the patient's comms log and the appointment history. You want to see who or what made each change and when. If the tool leaves no trace, your team cannot answer a patient who says "I never booked that", and you cannot investigate a complaint. Ask the vendor to add the note before you go live, not after the first dispute.
Fail any of the five and you have found a gap before a patient did. Write down which one failed and ask the vendor for the fix date in the contract notes.
Notes and scribes: usually paste, rarely write-back
Most AI scribes produce a draft note that a clinician pastes into the chart. Write-back, where the tool fills the right fields in Open Dental itself, is rarer. Progress notes in a dental chart are largely free text, which makes "paste into the correct box" the main integration most dentists get. Ask three things. Does the note land in the progress-notes area of the right patient automatically, or does the dentist copy it? Does the tool store audio, and for how long? Does the vendor sign a BAA? The longer treatment is in AI scribe for dentists: will it write back to your software?
A fair rule: if a scribe saves a dentist two minutes per patient but forces a copy-and-paste step on every note, it is still worth buying, as long as nobody pretends it is an integration. If it claims write-back, make it prove which fields.
Insurance checks: the add-ons that read portals and fill the chart
Insurance verification is where Open Dental add-ons are most concrete, because the job is mechanical: log in to a payer portal, read benefits, write them somewhere. Two examples with public pages:
- Foji calls itself an authorised Open Dental integration partner that connects through the official API. Its Open Dental page says it reads the subscriber ID, group number, carrier and plan from the chart, logs in to 120 or more payer portals, and writes results into the coverage grid, the plan notes and a benefit summary PDF in the imaging folder. Its setup documentation adds that checks start eight days before each appointment by default, a Foji button in the Open Dental toolbar runs one by hand, and the practice needs its own portal login for every payer it accepts. It quotes one flat monthly rate with no per-check fee but publishes no figure.
- Verifixed describes automated verification "using an API integration with Open Dental" in a post bylined Verifixed and filed as guest content on an Open Dental-branded news site. Because Verifixed wrote it, read it as a vendor claim.
Weave lists Insurance Verification among its products, but none of the Weave pages I could open names the practice systems it supports, so confirm Open Dental support directly. Our guide to dental insurance verification tools compares them on write-back.
Foji's documentation also names the commonest failure: a name mismatch, a wrong group number or a wrong address on the plan stops the check, and someone has to correct the chart and run it again. Other portal-reading tools are likely to trip on the same data problems, which is why you test with your own payers and your own messiest charts, not the vendor's demo patients.
Scoring three add-ons for a three-dentist practice
Illustration only. Say a private practice with three dentists, two hygienists and a front desk of two wants to stop missing calls at lunch and speed up verification. Open Dental's fee page does not count hygienists, so the three dentists sit inside the standard support licence: $199 a month per location in the first year, then $149. A fourth dentist would add $20 a month, making $169. Your own quote settles it.
The office scores two phone candidates and one eligibility tool out of 5 on the facts it has proved, not the ones it was told:
| Test (illustrative) | Phone tool A | Phone tool B | Eligibility tool |
|---|---|---|---|
| Writes the booking to the right operatory | 5 | 2 | n/a |
| Does not offer a taken slot | 5 | 3 | n/a |
| Writes a note the team can see | 4 | 1 | 4 |
| Fills benefits in the correct fields | n/a | n/a | 3 |
| Fails safely when a login breaks | 3 | 2 | 2 |
| Exit terms and BAA signed | 5 | 5 | 4 |
| Total | 22 of 25 | 13 of 25 | 13 of 20 |
Tool B looked cheaper and had a nicer demo, but failed the taken-slot test and left no note. Tool A is the pick. The eligibility tool scores well enough to trial for 30 days on ten patients a day, with a rule that a person checks any benefit the tool marks as unclear.
Now the sum that decides whether to proceed. If the front desk spends six minutes verifying each of 25 patients a day, that is 150 minutes. If the tool correctly fills 18 of those 25 and flags 7, the desk spends about 42 minutes on the flagged ones, saving 108 minutes a day. At 21 working days that is roughly 38 hours a month, and you compare that against the tool's monthly price, which you will have from the vendor. Replace my numbers with yours before trusting the result.
The email that gets a straight answer from a vendor
Vendors answer vague questions with brochures. Send this instead, filled in:
Subject: Open Dental connection: written answers before we sign
Hello [first name],
We run Open Dental [on our own server / hosted for us] with [number] providers.
Please answer in writing:
1. Does your product connect through the Open Dental API, a program link, a
copy of our data, or nothing? Name the method for each feature.
2. Which fields do you READ and which do you WRITE (appointments, patients,
insurance, comms log, progress notes)?
3. Do you need a service or the eConnector running in our office? Who monitors it?
4. Will Open Dental or anyone else charge us for API access?
5. Do you sign a BAA, and where is data stored?
6. Can you run a live test on our system with us watching?
7. What happens to our data and phone number if we leave?
Thank you,
[your name]Treat a reply that avoids question 2 as a "no connection" until proven otherwise. A reply to question 4 that says "free" for a tool that books appointments deserves a follow-up, since the free API tier is read-only.
A realistic mistake: the AI that booked into the wrong chair
Illustrative scenario. A practice trials a phone agent that books new patients. For two weeks every booking looks fine in the vendor dashboard. Then the hygienist notices three new patients booked into an operatory that is only used for surgery. The tool had read operatory names but not which provider each one belonged to, and the team had never tested more than a simple booking. The fix was a rule restricting the tool to two named appointment types and two operatories. The lesson: dashboards show what the tool believes it did; only the Open Dental schedule shows what happened. Check the schedule daily for the first fortnight.
Reading vendor pages without being fooled
Search results for "open dental ai software" are mostly vendor and developer pages. Some mislead by omission. Use this short filter.
- "Easy integration" with no field names means unverified.
- A table of what is read and written is a good sign but is still the vendor's own table.
- A named Open Dental connection method (API, program link) is better than a logo.
- A listing on a third-party review site is not an Open Dental endorsement.
- If two vendor pages contradict each other on what the API allows (one says claims are open to AI, another says they are not), ask Open Dental's support or the API forum rather than guessing.
When the choice is between several tools in the same category, the broader dental automation comparison will help you set a shortlist, and the AI guide lists the rest of the series.
Before-and-after for a lunchtime phone gap
Before: a two-person front desk breaks for lunch from 12:30 to 13:30; calls go to voicemail; the office calls back at 14:00; some callers have booked elsewhere. After: an AI agent answers for that hour, books new-patient exams into one slot type, and sends a message to the office for everything else. The office judges success on three numbers it can pull itself: calls answered in the lunch hour, new-patient bookings made by the agent that still show in Open Dental a week later, and the number of messages needing a callback. If bookings that "stick" are under 80 percent after a month, the connection is the suspect, not the callers. The 80 percent is a starting threshold for your own review, not a benchmark.
Three practices, three different answers
A one-dentist practice with a part-time receptionist often needs the least: Open Dental's own texting and Web Sched tools plus a scribe that pastes notes. The fees page lists those at $5 to $75 a month per location each, plus a few cents per text message, and none needs an API contract. A three-dentist practice with a busy phone gets most from a phone agent that writes bookings, because missed calls are where new patients are lost. A group of several offices needs the strictest test, because one wrongly mapped operatory name repeats across every site; test each location's schedule, not just the first, and keep one named owner for the vendor relationship.
The common thread is that the cheapest-looking tool is rarely the cheapest once a person has to fix its output. Count that person's minutes in the price.
Deciding with a one-page rule
Buy only when a vendor has passed these, in this order: the written answers above, the five-call test, a signed BAA, a named person for outages, and a monthly cancellation right during the first three months. If a tool fails the test but you still like it, buy it as a "beside the software" tool and cost in the manual step. If you would rather map this with someone, that is what my AI implementation consultation covers.
Open Dental AI questions practices ask before signing
Does Open Dental have its own AI receptionist or scribe?
Not on its published fee list. The only AI line item on Open Dental's fees page in November 2026 is AI Image Analysis from BetterDiagnostics, which reads radiographs. Phone answering, note-taking and insurance checks all come from third-party vendors that connect through bridges or the API.
Does an AI add-on need the Open Dental API?
Not always. Some tools use a program link inside Open Dental, some use the API, and some only read a copy of the schedule or work beside the software with no connection at all. Ask the vendor which of these it uses, then ask for a live test booking that appears in your schedule.
Who pays for API access when an AI vendor connects?
Open Dental's API permissions page lists four developer tiers, from a free read-only tier to $35 a month per location, and says the developer pays. A tool that books appointments needs more than the free tier, so vendors usually fold that cost into their own price. Ask in writing whether any Open Dental charge will land on your invoice.
Can an AI tool check insurance and write benefits into the chart?
Some can. Foji's Open Dental page says it reads plan details from the chart, checks 120 or more payer portals and writes benefits into the coverage grid and plan notes. Ask for the fields it fills, which of your carriers it covers and what happens when a portal login fails, then test with ten of your real patients.
What if my practice runs Open Dental on a local server?
Open Dental's API documentation says the Service mode runs continuously on the office's database server, which needs the eConnector, and Remote requests also reach the office through the eConnector. If that server is off, tools that rely on it stop working, so ask who monitors it and who is called when it fails.
Further reads
- Which Dental Front Desk Tasks Can AI Take Over? — Sorts front-desk jobs into what AI can and cannot take.
- AI Tools for Dentists With No IT Team: Six to Try in the First Month — Six tools to try when nobody on staff does IT.
- AI for Dental Billing: Claim Checks, Statements and Follow-Up — Claim checks and statements once your tools connect.
- AI Notes for Dentists: Hygiene, Restorative and Emergency Visit Templates — Note templates by visit type for scribe output.
- AI Chatbot for Dentists: Fee, Emergency and Booking Rules to Set — Fee, emergency and booking rules to set for a chatbot.
- Healthcare AI Call Centre: When a Group Practice Should Centralise Calls — When several sites should share one call team.
- AI Automation Agency for Dentists: What to Check Before You Hire — Questions to ask if an agency builds the connection.
- What to Ask Before Buying Any AI Tool for a Medical Practice — General questions for any AI tool a practice buys.
- Dental Sterilisation Log: A Daily Template and AI Reminder Routine — A daily sterilisation log template for a dental practice, plus an AI reminder routine that chases sign-offs but never approves a cycle.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Open Dental fees page, API specification, API permissions, API modes and Appointments and Commlogs API pages; Foji Open Dental page and setup documentation; Verifixed guest post on an Open Dental-branded news site; Weave home, AI Receptionist and integrations pages (checked 4 November 2026). Vendor claims were treated as claims, not proof.