Dentrix AI Receptionist: What Works, What Doesn't, What to Ask

Dentrix is one of the most widely used practice management systems in North America. Henry Schein One, the company behind Dentrix and Dentrix Ascend, says more than 48,000 DSO, group and private practices work with it. If you run a general practice built in the last 20 years, odds are good you are on Dentrix or Dentrix Ascend. That also means the "does this AI receptionist actually work with Dentrix?" question gets asked more often than almost any other integration question in the category.

Here is the straight answer: what a Dentrix AI receptionist actually does, where the integration happens, and what to ask before you sign anything.

Dentrix integration is middleware-based, and that is fine

Dentrix does not publish a direct public API the way Open Dental does, so a Dentrix API integration for an AI receptionist runs through partnerships and certified middleware instead. For AI receptionists, that middleware is usually NexHealth, the same layer that powers dental scheduling across Dentrix, Dentrix Ascend, Eaglesoft, Denticon, CareStack, and Cloud 9. For the mechanics of how that handoff actually works, see how NexHealth powers AI dental booking.

For the practice, this is mostly invisible. You authorize the middleware once during setup. From that moment on, every call the AI books writes into your Dentrix schedule grid in real time. Your team does not log into the middleware. They do not change any Dentrix workflow. They just see new appointments appear.

The middleware layer also gives you some useful flexibility. If you ever migrate off Dentrix to Dentrix Ascend, or onto Denticon or CareStack in a DSO rollup, the AI moves with you. The integration is with the middleware, not tied to your specific Dentrix install.

What the AI actually does on a Dentrix schedule

The call flow on Dentrix is the same as on any other supported PMS, and it runs as a true Dentrix 24/7 phone line that never rolls to voicemail.

Ring, pickup. AI answers in your practice's voice on the first ring.

Intake. Name, date of birth, phone number. Spelling confirmed on the name.

Patient lookup. The AI queries your Dentrix patient database through the middleware. If the caller exists, their record is pulled. If not, a new patient record is created as part of the booking.

Reason for visit. AI asks what the patient is calling about and maps it to the correct Dentrix appointment type with the correct duration.

Availability read. The AI reads the Dentrix schedule in real time. It respects your provider-specific rules, operatory constraints, and appointment-type durations. If you have configured a Saturday-only hygiene block, the AI honors it. If Dr. Patel does not take new patients, Dr. Patel never gets offered.

Offer and confirmation. AI proposes two or three slots. Patient picks one. AI reads back the details.

Write. Appointment is written into your Dentrix schedule grid. Your team sees it the moment they refresh.

Wrap. Confirmation SMS goes out. Any last questions get answered. Call ends.

Two to four minutes. Zero staff involvement.

Dentrix-specific things worth knowing

A few Dentrix particulars shape the integration experience.

Appointment classes and duration units. Dentrix uses "units" of 10 or 15 minutes (configurable) for appointment durations. The AI converts its internal duration logic to match whatever unit size you have configured. A 60-minute new-patient exam becomes 4 or 6 units depending on your setup.

Operatory mapping. Dentrix operatories can be provider-restricted, appointment-type-restricted, or open. The AI respects all three. A new-patient exam will not book into an operatory that is restricted to hygiene only.

Multi-provider appointments. New patient exams that require both a hygienist for the initial clean and a doctor for the exam can be booked as a linked appointment. The AI handles the read and write for both providers simultaneously.

Recall integration. Dentrix recall workflows are exposed through the middleware. The AI can see whether a caller is due for a recall and offer to book it while they are on the line. That is Dentrix automation at its most practical: nobody has to run a recall report for it to happen.

Dentrix Ascend (the cloud version) differences

Dentrix Ascend is Henry Schein One's cloud-native platform. Integration with an AI receptionist is similar but not identical.

• Setup is simpler. No local server to authorize.
• Multi-location DSOs on Ascend. Well supported. The AI routes across your entire practice network.
• Cloud-to-cloud latency. Availability reads on Ascend are slightly faster in practice because the AI, the middleware, and Ascend are all cloud-hosted.

What about Dentrix Enterprise?

Dentrix Enterprise (the enterprise DSO product, distinct from standard Dentrix) is also supported through the same middleware. Large group practices and DSOs using Dentrix Enterprise can deploy a Dentrix AI receptionist across all locations with a single integration.

Questions worth asking any Dentrix vendor

Any AI receptionist Dentrix buyers are evaluating should survive these five questions from a skeptical office manager.

1. Show me a live booking hit my Dentrix schedule grid right now, in a sandbox or my own practice. If they cannot demonstrate a live write to Dentrix, they do not have working Dentrix integration.
2. Is the middleware certified and maintained? The answer should be yes, with documentation.
3. What happens if the middleware is unreachable? Look for graceful degradation. The call should stay live, capture the patient, and book a soft request that surfaces when the middleware comes back.
4. Do you support my Dentrix Ascend / Dentrix Enterprise / multi-location setup specifically? Get a yes or no with specifics, not a "yes we support Dentrix generally."
5. What BAAs do I need to sign, and who are the sub-processors? A full list, in writing, before you sign.

The HIPAA chain on a Dentrix AI receptionist

• The AI vendor signs a BAA with your practice.
• The middleware signs a BAA with the AI vendor.
• The voice platform signs a BAA with the AI vendor.
• Recording and transcript storage is encrypted and BAA-covered.
• Dentrix itself, when installed correctly, is HIPAA-compliant.

Any missing link breaks the whole chain. Ask for the sub-processor list. A vendor that hesitates is a vendor to pass on.

What this costs on Dentrix vs other PMSes

Pricing does not change materially by PMS. Enamly starts at $399 per month, for a solo practice regardless of whether you run Open Dental, Dentrix, Eaglesoft, or a cloud PMS. Multi-location and high-volume setups move up from there. The setup fee covers integration configuration, conversation-flow tuning, and the initial voice setup.

There is no per-call billing. Every plan includes 600 minutes of talk time, sized for a typical practice, and most practices never come close to it. For the full breakdown, see what an AI dental receptionist actually costs.

See Enamly on Dentrix

If you run Dentrix, Dentrix Ascend, or Dentrix Enterprise, book a 15-minute demo. I'll walk you through a live booking into a sandbox and show you the full patient experience end to end.

If you want to see what a year of missed-call recovery is worth to your practice first, the missed-call revenue calculator takes 60 seconds.

You can also read about the broader picture in how AI receptionists actually book patients into your dental PMS or start from the integrations overview.

---

Dr. Bethel Ozumba, known as Dr. B-Bay, is the Founder and CEO of Enamly. He is a practicing dentist who sold his private practice in April 2025 to build Enamly full time. He writes about dental AI and front-desk operations at enamly.ai/blog.