Open Dental, Dentrix, Eaglesoft: how AI receptionists integrate with each PMS

Practice management system integration is the dividing line between AI receptionists that look impressive in a demo and AI receptionists that actually work in your office. The depth of the integration determines whether the AI can read a patient's history, write back appointment changes, see schedule conflicts in real time, and avoid double-booking. Each major PMS — Open Dental, Dentrix, Eaglesoft — exposes a different surface to integrators, and each has its own quirks. This guide is the engineering-honest version of what to expect.

Why integration depth matters

Three behaviors separate a deeply integrated AI receptionist from a shallow one:

1. Read on demand: when a patient calls, the AI can pull up their record — last visit, balance, hygienist, treatment plan status — and discuss any of it without asking the caller to repeat what they already told you in 2023.
2. Write in real time: when the AI books or reschedules, the change shows up in your PMS calendar within seconds. The front desk sees it on their morning huddle without manual data entry.
3. Conflict detection: the AI sees the schedule as it actually is — including the operatory the front desk just blocked off for an emergency — and doesn't book over it.

Shallow integrations skip one or more of these. The most common shallow pattern is "we'll email your office manager a CSV every night with bookings to enter manually." That's not integration. That's a fax with extra steps.

Open Dental: the easiest to integrate well

Open Dental is the friendliest of the three for AI integration, by a meaningful margin. It exposes a well-documented HTTP API (the Open Dental API), supports OAuth-style developer keys, and has a database structure that's been mature and well-documented for years. Many vendors built their first PMS integration on Open Dental specifically because the on-ramp is gentlest.

What this means for your practice: if you're on Open Dental, integration with virtually any AI receptionist is straightforward. Real-time read AND write should be table stakes. Real-time eligibility verification, schedule changes, patient record pulls — all of it should work natively.

The one gotcha: some Open Dental setups are self-hosted on a server in the practice rather than cloud. For those, the AI needs a small bridge service running locally to talk to the database. Most vendors handle this transparently, but ask how if it's relevant to you.

Dentrix: doable, but more work

Dentrix integration is more involved. Henry Schein has historically been protective of the Dentrix API, and the most reliable integration paths go through one of two channels: the Dentrix Developer Program (DDP), which requires the vendor to be certified, or DXone — Dentrix's own API platform that supports a defined set of operations.

What this means for your practice: AI receptionists that have done the certification work integrate with Dentrix well — read appointments, write back bookings, pull patient records, eligibility. Vendors that haven't done the certification work end up doing screen-scraping or scheduled CSV exports, which is fragile and breaks when Dentrix updates.

Ask any vendor: "Are you a Dentrix-certified integration partner?" If the answer is no, ask exactly how the integration works. If it's screen-scraping, expect breakage twice a year when Dentrix updates.

Aria is integrated through the certified path; our verification work pulls live eligibility and writes appointments back in real time on Dentrix.

Eaglesoft: the hardest of the three

Eaglesoft (Patterson Dental) has the smallest third-party integration ecosystem of the three majors. The integration surface is more limited, and Patterson's developer program is harder to get into than Henry Schein's. Several major dental AI vendors don't support Eaglesoft at all, or support it via a thin file-based sync rather than real-time.

What this means for your practice: if you're on Eaglesoft, narrow your shortlist to vendors that explicitly say they support Eaglesoft natively, and ask them to demo the integration on Eaglesoft specifically — not on Open Dental as a stand-in. The quality varies meaningfully.

Aria supports Eaglesoft with real-time read and write. Some competing vendors do; some only support it via overnight sync, which means a booking made by AI at 2 PM doesn't show up in your office until the next morning. That's a meaningful operational difference.

What the data flow actually looks like

The data flow for a deeply integrated dental AI receptionist on a typical inbound call:

• Call comes inThe phone rings. AI picks up. Caller ID and IVR routing determine which practice the call is for (relevant for multi-location).
• Caller identificationAI asks for the caller's name. If the name matches a record in your PMS, the AI pulls the patient profile — last visit, balance, primary provider, treatment plan, recall status.
• Reason for visitAI gathers the reason. If clinical urgency is detected, the AI checks the escalation rules and either books or routes to the on-call doctor.
• Eligibility verificationIf new patient or plan year rollover, AI hits the eligibility API in real time. Returns benefits, deductibles, frequency limits in seconds.
• Schedule readingAI queries the PMS for open slots that match the appointment type, the patient's preferred provider, and the operatory requirements. Returns 2-3 options.
• BookingPatient picks a slot. AI writes the appointment back to the PMS — provider, operatory, type, length, reason for visit, eligibility result.
• ConfirmationSMS confirmation goes out. PMS reminder schedule kicks in for the standard cadence.
• Front-desk notificationOffice manager sees the booking in the morning huddle, with full context.

The whole flow is 3-7 minutes from "phone rings" to "patient confirmed." Every PMS read and write is real-time.

Common gotchas

Things to watch for:

• Provider preference rules. Some patients always want the same hygienist. The AI needs to read that preference from the PMS and respect it. Ask whether the vendor has tested this.
• Operatory routing. Different appointment types need different operatories. The integration has to honor your operatory rules; otherwise it'll book sedation patients into the wrong room.
• Plan year rollovers. Patient eligibility flips on January 1 (or whenever the employer's plan year resets). The AI should re-verify on the first call after rollover, not assume the prior plan still works.
• Concurrent writes. If the AI is booking and a front-desk person is booking the same slot manually, you have a race condition. Robust integrations handle this with row-level locks. Shallow integrations end up with double-bookings.
• Multi-location patients. Patients who've been seen at multiple locations within a DSO need their record stitched correctly. This is hard and most vendors do it poorly. Ask specifically.

Questions to ask any vendor

Before signing, get yes/no answers to these PMS questions:

1. Are you a certified integration partner with [my PMS]? Show me the certification.
2. Is the integration real-time, or scheduled? If scheduled, on what cadence?
3. Can the AI read patient records during a call? Show me on a real call.
4. Can the AI write back appointments in real time? Show me a booking that lands in the schedule in under 30 seconds.
5. How are concurrent writes handled? What happens if two parties book the same slot?
6. What fields are mapped (provider, operatory, type, length, reason, notes)?
7. What happens when the PMS goes down? Does the AI keep working and queue the writes?
8. Can I see a customer reference using your integration on [my PMS]?

The right vendor will answer these directly. The wrong vendor will hedge.

How Aria does each

Aria's PMS integrations:

• Open Dental: direct API integration, real-time read and write, supports both cloud and self-hosted deployments. Live in 1-2 days.
• Dentrix: certified integration partner, real-time read and write, eligibility verification flows back. Live in 3-5 days.
• Eaglesoft: native integration with real-time read and write. Live in 5-7 days due to additional configuration.

If you're on a different PMS — Curve, Tab32, Carestream — we don't currently have native integration but can sometimes work via a hybrid approach. Ask us about your specific PMS and we'll be straight about what works and what doesn't.

Related reading