Open Dental publishes an open-slots endpoint and an ASAP list. Most phone systems never touch either.
Open Dental is the practice management system a large share of independent dental practices run on, and unlike most software in this category it documents a genuinely complete public API, including endpoints for open appointment slots and the short-call list. That combination is unusual, and it is what makes a phone agent for a dental practice a different proposition than it is almost anywhere else.
What is Open Dental, and who runs on it?
Open Dental is dental practice management software: the scheduler, chart, ledger and recall system a practice runs its day from. It is most common among independent and small-group practices rather than large corporate DSOs, and it is typically installed on the practice's own server rather than rented as a hosted service.
That last detail matters more than it sounds. Because a practice usually owns its Open Dental database, the practice controls what connects to it, which is why Open Dental has an unusually open and well-documented API compared to the hosted booking platforms that dominate other verticals. Where a salon platform may expose read-only availability, Open Dental documents appointment creation, open-slot search and the ASAP list.
The practical consequence is that a dental practice has more room to build a real phone workflow than almost any other kind of clinic we work with. The constraint is rarely the software. It is usually that nobody has connected the phone to it.
What gap does Open Dental leave?
It runs the schedule beautifully and answers no calls. Open Dental knows exactly which operatory is free on Thursday and which patients are waiting for a short-call slot, but that knowledge only reaches a caller if a person at the front desk looks it up while the phone is ringing.
Dental reception is one of the most interrupted jobs in healthcare. The same person is checking a patient in, taking a payment, handling an insurance question and answering a line that rings through all of it. When two calls arrive at once, one goes to voicemail, and a caller with a broken tooth does not leave a voicemail, they call the next practice.
The cancellation problem is sharper still. A practice with a 3pm gap tomorrow has a list of patients who said they would come in on short notice, and filling that gap is worth the whole hour of chair time. Doing it means somebody has time to work the list, and the moment a practice is busy enough to have gaps worth filling is the moment nobody has time to fill them.
None of this is a criticism of Open Dental. It is practice management software and it manages the practice. It was never supposed to answer the phone.
What does Open Dental's API actually allow?
Creating appointments, reading open slots, and reading the ASAP list: all three are named endpoints in Open Dental's own published specification. That is a genuinely two-way ceiling and it is rarer than the marketing in this category suggests.
Verified against the vendor's own API reference
| Capability | In Open Dental’s API | Endpoint |
|---|---|---|
| Create an appointment | Yes | POST /appointments |
| Read open slots | Yes | GET /appointments/Slots |
| Read the ASAP / short-call list | Yes | GET /appointments/ASAP |
| Read existing appointments | Yes | GET /appointments |
| Add a note to an appointment | Yes | PUT /appointments/{AptNum}/Note |
| Confirm an appointment | Yes | PUT /appointments/{AptNum}/Confirm |
| Web-scheduling slot logic | Yes | GET /appointments/SlotsWebSched |
Read from Open Dental API specification: Appointments on August 10, 2026. APIs change; this is what the index listed that day.
What that means for your build
This table is the ceiling, not a description of every build. What a given practice's agent actually uses is a scope decision made during onboarding: some practices want the agent to book directly into the schedule, others want it to capture the request and leave the booking to a person who knows the chart. Both are legitimate, and the second is the right default for a practice where appointment length depends on clinical judgment. We will tell you which we are building before we build it, and we will not describe a capability your build does not include.
What it will not do
- Decide how long an appointment should be. Chair time depends on the procedure and often on the chart, and a phone agent guessing at duration creates a schedule the practice has to unpick.
- Answer clinical questions. Whether a symptom is urgent, whether a crown can wait, whether a medication is a problem: those route to the practice, always.
- Quote what a treatment will cost under a specific insurance plan. Coverage depends on the plan, the remaining maximum and the code, and none of that is a phone answer.
- Access anything the practice has not granted. Open Dental is usually the practice's own server, so what the agent can reach is set by the practice, not by us.
What does a call to a dental practice actually sound like?
Usually a mix of a scheduling request and a question the phone must not answer. The useful thing an agent does here is separate the two cleanly, rather than trying to be helpful about the wrong half.
An example call: composite, not a recording
A patient calls on a Tuesday afternoon with a broken filling. This is the most common shape of urgent dental call: a real problem, a scheduling need, and a clinical question the caller wants answered on the phone.
- Caller
I think a filling came out - the tooth is sharp and it's catching on my tongue. Can I get in this week?
- Agent
I can get you booked. Before I do, are you in pain right now, or is it mainly the sharp edge?
Triage, not diagnosis. The distinction between discomfort and acute pain changes urgency, and asking is not the same as assessing. - Caller
Not really painful. Just annoying.
- Agent
Understood. I have Thursday at 2:40 and Friday at 11:10 with Dr. Nguyen. I'll also put you on the short-call list - if something opens sooner we'll call you.
Open slots and the ASAP list are both readable via the API. The short-call offer costs nothing to make and is how the practice fills tomorrow's cancellation. - Caller
Thursday works. Will my insurance cover it?
- Agent
That depends on your plan and what's left on your annual maximum, so I won't guess at it - I've flagged it and the office will confirm your coverage before Thursday.
The refusal is the point. A coverage figure invented on the phone becomes a dispute at the desk, and a practice that has to walk a quote back has lost more than the call was worth.
Booked, on the short-call list, and the insurance question routed to someone who can actually answer it, with the whole exchange handled at 4:50pm while the front desk was checking out the last patient of the day.
Every dental practice keeps a short-call list to fill tomorrow's cancellation, and Open Dental publishes an endpoint for it - the list is not the hard part, having someone free to work it is.
The fastest way to know whether this fits is to say what your front desk misses on a busy afternoon. If it's the short-call list, that is a solvable problem.
Start free pilotQuestions Open Dental practices ask
Open Dental's API documents POST /appointments for creating an appointment and GET /appointments/Slots for open slots, verified against their published specification on August 10, 2026, so the capability exists. Whether a particular build writes into the schedule or captures the request for a person to book is a scope decision made during onboarding, and for practices where appointment length depends on the chart we often recommend the second. We will tell you which yours does.
Open Dental publishes GET /appointments/ASAP, which exposes the ASAP list. That makes working the short-call list something software can do rather than something that only happens when the front desk has a quiet ten minutes. It is the single most under-used endpoint in dental practice management, and filling one chair-hour usually pays for more than the phone costs.
Open Dental typically runs on the practice's own server, so what any integration can reach is set by the practice rather than by us. On our side: SOC 2 Type I and Type II, HIPAA compliance under a business associate agreement, call retention configurable from one day to two years, and personally identifiable information excludable per agent. Our data is stored in the United States, stated up front; for an Alberta practice with obligations under the Health Information Act, that is a conversation to have explicitly rather than a box to tick.
That is a common and entirely reasonable answer, particularly in practices where the hygienist's column and the doctor's column have different rules. The agent then answers, triages, captures the request with everything the front desk needs, and leaves the booking to a person. You get the after-hours coverage and the concurrency without handing the schedule to software.
Hear it handle a broken filling at 4:50pm
The free pilot is about fourteen days to a working line with no call limit, and you keep it or you walk away. Call it yourself, describe a problem, then ask it what your insurance covers and listen to where it stops.
Start free pilotLast updated .