NexHealth AI Booking for Dental: How the API Actually Works

When a patient calls your practice at 9:18 on a Wednesday night, she does not want a voicemail. She wants an appointment.

The question is whether your phone system can give her one.

An AI receptionist connected through NexHealth dental AI booking can. It answers in the first ring, asks the right intake questions, reads your live Open Dental or Dentrix schedule through the NexHealth API, offers two or three openings, and writes the confirmed appointment before the patient hangs up. No callback promise. No front-desk involvement. No lead lost to the practice that answered her next call.

I built Enamly around this architecture because I lived through the alternative. When I was running my dental practice, after-hours calls went to voicemail. My front desk followed up the next morning. The patients we reached first booked. The ones we reached an hour later had moved on. That is not a staffing problem. It is a systems problem. NexHealth, combined with an AI voice layer, is what solves it.

Here is exactly how it works.

Why dental PMS systems need a bridge

Open Dental, Dentrix, Eaglesoft, Denticon, CareStack, Cloud 9: each of these practice management systems was built on a different technical foundation.

Open Dental runs on a local MySQL database. Dentrix lives on Windows file servers in most offices. Eaglesoft has its own proprietary data model. Dentrix Ascend is a cloud application with a REST API. Denticon was built for DSOs and runs a different cloud architecture entirely. Cloud 9 was designed around orthodontic workflows with its own scheduling model.

There is no single interface that talks to all of them natively. An AI receptionist that wanted to read live availability and write appointments across every major dental PMS would need to build and maintain a separate integration for each one. That is not a software problem you solve once. It is a software problem you solve twelve or fifteen times, and then again every time a PMS vendor changes their API version.

NexHealth solves this by acting as the translation layer. One API connection from an AI receptionist to NexHealth is functionally equivalent to direct integrations with every PMS on NexHealth's list. NexHealth handles the translation between its unified response format and whatever each underlying PMS requires on the other end.

According to NexHealth's published integration documentation, their platform currently supports over 60 healthcare practice management systems. The dental-specific roster covers every major PMS used in US practices today, from the most common independent-practice systems to the cloud-native DSO platforms.

What NexHealth actually exposes

The NexHealth API gives an AI receptionist four core capabilities that matter for dental booking.

Real-time availability reads. Enamly queries NexHealth for open slots by provider, appointment type, duration, and date range. The response reflects your live schedule at that moment. If your hygienist has a 60-minute new-patient block open at 10:15 Thursday, the AI sees it and can offer it. If your front desk booked that slot two minutes ago from another line, it is already gone and the AI offers the next available time. No stale data reaches the patient.

Patient lookups. Before the AI routes any call, Enamly queries NexHealth with the inbound phone number. If the patient already exists in Open Dental or Dentrix, their record returns: associated provider, last visit date, appointment history. That lookup determines whether the call follows the new-patient intake path or the existing-patient path, and which provider the AI should route to. Existing patients go to their usual hygienist or doctor. New callers go through full intake.

Appointment writes. This is the capability that separates genuine booking from a better voicemail system. Enamly sends the confirmed appointment through NexHealth, which writes it directly into the PMS while the patient is still on the phone. When your front desk opens their schedule the next morning, the appointment is already there. It was booked at 9:18 PM. No one touched it between then and now.

Reschedule and cancel handling. When an existing patient calls to move an appointment, Enamly retrieves their upcoming visits through NexHealth, confirms the details with the caller, and pushes the change back to the PMS. The front desk sees the updated calendar without handling the call.

All four capabilities running together on a single call are what separate a booking system from a message-taking system.

Why not all NexHealth integrations are equal

When you hear that an AI receptionist "integrates with NexHealth," it is worth asking specifically what they mean.

Some vendors use NexHealth for availability reads only. They can tell the patient which slots exist, but when the patient says yes, the AI sends a branded scheduling link by SMS. The patient clicks through, picks a time again, fills out a form, and submits. The appointment lands in the PMS after the patient completes the online flow, which takes anywhere from five minutes to never.

Two things break in that model. First, the slot the patient agreed to on the phone may be booked by someone else before she finishes the online form. Second, patients who are driving, interrupted, or just lazy do not complete the link. You captured a lead but not an appointment.

A NexHealth-native integration reads availability, holds the slot, and writes the appointment during the call. The patient hears the AI confirm the date, time, and provider. The slot is reserved before she hangs up. That distinction directly affects your schedule fill rate and your no-show rate, because patients who book through a confirmed phone interaction show up at a higher rate than those who self-scheduled through an online form they found after a follow-up text.

Enamly completes the write during the call. The patient does not need to do anything else.

What a live NexHealth-powered call looks like

Here is how a new-patient call flows when Enamly is connected to Open Dental through NexHealth.

Ring and pickup. Enamly answers in the first ring using your practice name and the voice you chose during onboarding. The patient hears a consistent, branded experience whether they call at 10 AM or 10 PM.

Reason for visit. The AI asks what brings them in. The patient says new patient exam. Enamly maps this to the correct appointment type in your PMS: 60-minute block, requires the doctor, flags for new-patient intake paperwork.

Intake. Because no record matched the incoming number, the AI collects name, date of birth, and a callback number. For patient records that flow into insurance claims, spelling matters. Enamly reads back what it captured before moving on.

Availability read. Enamly queries NexHealth for new-patient exam slots with your scheduled providers over the next three weeks. NexHealth returns the live Open Dental availability at that moment.

Offer. The AI presents two or three openings. "I have Tuesday the 17th at 10:15, Thursday the 19th at 2:30, or Monday the 23rd at 9:00. Which works best for you?"

Confirmation. The patient picks Thursday at 2:30. Enamly reads back the time, provider name, and office address.

Write. Enamly sends the confirmed details to NexHealth. NexHealth writes the appointment into Open Dental. The slot is gone from available inventory before the call ends.

Wrap. Enamly confirms the SMS confirmation is on its way and closes the call warmly. Total call time: two to three minutes on average. Zero front-desk involvement.

Your front desk sees the appointment when they open the schedule. They did not take the call. They did not follow up with a lead. The patient was a stranger at 9:18 PM and is a confirmed appointment by 9:21 PM.

Which PMS systems this covers today

Enamly connects NexHealth AI booking for every system on NexHealth's dental roster. That currently includes Open Dental, Dentrix, Dentrix Ascend, Dentrix Enterprise, Eaglesoft, Denticon, CareStack, Cloud 9, Curve Dental, Fuse, Dolphin, CS OrthoTrac, and CS WinOMS.

For practices on systems outside the NexHealth list, Enamly runs in unintegrated mode. The AI still answers every call, collects complete patient intake, and sends a branded scheduling link by SMS and email. Your front desk gets the captured lead in their queue. Nothing falls through to voicemail.

For Oryx practices, Enamly uses Oryx's own direct public API rather than the NexHealth path. The booking outcome is the same: confirmed appointment before the call ends, via a different infrastructure route.

The full current list is on the Enamly integrations page. The NexHealth integration details page covers the specific connection setup for practices already on NexHealth's platform.

HIPAA and the compliance chain

Any AI receptionist that reads from or writes to your PMS touches protected health information. That means every piece of the technical stack needs to be covered by Business Associate Agreements and HIPAA-aligned infrastructure.

NexHealth operates a HIPAA-compliant API layer and signs BAAs with healthcare vendors that connect to it. Enamly signs a BAA with every practice before any patient data enters the integration. Call recordings and transcripts are stored encrypted on AWS S3 with KMS key management. PII redaction runs across the voice pipeline so patient names and dates of birth do not persist in plain-text log files.

If you are evaluating any AI receptionist that touches NexHealth or any other PMS middleware, ask for the full sub-processor list and confirm each component is covered. Voice provider, transcript storage, recording storage, middleware layer. A single uncovered link is a HIPAA exposure.

The ADA Health Policy Institute recommends that practices audit their full technology stack annually for HIPAA compliance, including all third-party integrations. That recommendation applies directly to AI-powered front-desk tools and the booking infrastructure behind them.

Key takeaways

• NexHealth is a unified dental scheduling API that bridges AI receptionists to Open Dental, Dentrix, Eaglesoft, and 60+ other PMS systems without requiring separate integrations for each.
• A NexHealth-native AI receptionist reads availability and writes confirmed appointments during the phone call, not through a follow-up scheduling link.
• Scheduling links are not equivalent to real-time PMS writes. Patients who complete links show up less reliably than patients who heard a confirmed time on the phone.
• Enamly uses NexHealth for booking across all supported dental PMS systems, with a direct Oryx API path for Oryx practices.
• The full HIPAA compliance chain requires BAAs at the voice provider, middleware, recording storage, and vendor level.

Want to see it work on your schedule?

If your practice runs on Open Dental, Dentrix, Eaglesoft, or another supported PMS, book a 15-minute demo and watch Enamly write a confirmed appointment into a sandbox schedule while you are on the call. Starting at $299/month.

---

Dr. Bethel Ozumba, known as Dr. B-Bay, is the Founder and CEO of Enamly. Before Enamly, he was a practicing dentist who scaled his private practice to $1.3M in revenue in its first year before selling in April 2025 to build the AI receptionist he wished he had behind his own front desk. Read more about his background at enamly.ai/about/dr-bbay or follow his work at enamly.ai/blog.