TLDR: "Integration" is the most overclaimed word in dental AI marketing. Every vendor says they integrate with your PMS. This article explains what that claim actually means — and what to test before you believe it. Real integration means the AI reads your schedule live, writes appointments directly into your PMS, matches callers to patient records, and syncs changes in both directions. Ira, the Savvy Agents AI receptionist, does all four with Open Dental, Dentrix, Eaglesoft, Denticon, and Curve. If your vendor can't demonstrate these capabilities in a live demo with your actual system, their "integration" is marketing copy.
The Integration Spectrum: From Marketing Claim to Real Connection
When a dental AI company says "we integrate with Open Dental," that claim can mean any of the following:
- Level 1 — Message passing: The AI takes a message from the caller and emails or texts it to your office. Someone on your team then manually enters the appointment. This is not integration. This is a transcription service.
- Level 2 — One-way read: The AI can see your schedule (often a cached copy updated periodically) but cannot write to it. It tells the patient "we have availability on Tuesday" but doesn't actually book the appointment. Your team still has to enter it. Better than Level 1, but still creates manual work.
- Level 3 — One-way write: The AI can create an appointment in your PMS, but works from a static schedule copy. It might book a patient at 2pm without knowing your front desk booked someone else at 2pm five minutes ago. This creates double-bookings and schedule conflicts.
- Level 4 — Real-time read/write: The AI reads your schedule live and writes appointments directly. If a slot is taken between when the AI offers it and when the patient confirms, the AI sees the conflict and offers a different time. This is real integration.
- Level 5 — Full two-way sync: Everything in Level 4 plus: changes made in the PMS (reschedules, cancellations by front desk) update the AI's reminder system, and patient responses to AI reminders (confirmations, cancellation requests) update the PMS. This is what Savvy Agents provides.
Most vendors are at Level 1 or Level 2 and call it "integration." Asking the right questions during evaluation will tell you which level you're getting.
How Ira Connects to Each PMS
Each practice management system has different technical characteristics. Here's how the Savvy Agents integration works with each supported PMS.
Open Dental
Open Dental is an open-source PMS with a well-documented API and direct database access options. This makes it one of the most integration-friendly systems in dental.
Ira's connection to Open Dental:
- Schedule read: Real-time API calls to the Open Dental server check provider availability, operatory assignments, and time blocks as the patient is on the phone
- Appointment write: New appointments are created through the API with the correct provider, operatory, appointment type, procedure codes, and time length
- Patient matching: Phone number lookup against the patient database identifies existing patients. New patient records are created with data collected during the call (name, DOB, phone, insurance carrier)
- Two-way sync: Appointments created or modified by front desk staff in Open Dental update the reminder system. Patient confirmations and cancellation requests from reminders update the appointment status in Open Dental
The integration uses Open Dental's native API — there's no middleware translation layer. Appointments created by Ira are indistinguishable from appointments entered manually by staff.
Dentrix
Dentrix is the most widely used dental PMS in the United States. Its integration options have expanded in recent years through Henry Schein's API program.
Ira's connection to Dentrix:
- Schedule read: API-based access to provider schedules, including appointment blocks, operatory assignments, and existing appointments
- Appointment write: Appointments created through the Dentrix API appear in the Appointment Book with correct provider, time, and appointment type
- Patient matching: Existing patient lookup by phone number. New patient record creation with intake data
- Two-way sync: Schedule changes in Dentrix reflect in the reminder system. Patient responses to reminders update Dentrix appointment status
Eaglesoft
Eaglesoft, by Patterson Dental, uses a local database architecture. Integration approaches differ from cloud-based or API-first systems.
Ira's connection to Eaglesoft:
- Schedule read: Direct connection to the Eaglesoft database reads provider schedules in real time
- Appointment write: Appointments are written to the database following Eaglesoft's data structure, appearing in the Schedule view
- Patient matching: Phone number lookup against the patient table. New patient records created with proper field mapping
- Two-way sync: Database monitoring detects schedule changes made by front desk. Reminder responses trigger database updates
Denticon
Denticon is a cloud-based PMS designed for multi-location groups and DSOs. Its API is built for enterprise-scale operations.
Ira's connection to Denticon:
- Schedule read: Cloud API provides real-time schedule access across multiple locations
- Appointment write: API-based appointment creation with support for multi-location routing
- Patient matching: Cross-location patient search capability
- Two-way sync: Cloud-native sync with real-time updates in both directions
Curve Dental
Curve is a cloud-based PMS that has gained adoption particularly among newer and growing practices.
Ira's connection to Curve:
- Schedule read: Cloud API access to provider schedules and availability
- Appointment write: Direct appointment creation through Curve's API
- Patient matching: Phone number-based patient lookup and new patient creation
- Two-way sync: Cloud-based sync with real-time bidirectional updates
What Real-Time Actually Means
The term "real-time" gets thrown around loosely. Here's what it means in the context of schedule integration during a phone call.
A patient calls at 10:00:03 AM and asks for a Thursday afternoon appointment with Dr. Chen. Ira queries the PMS at 10:00:04 AM and sees that Thursday 2pm, 3pm, and 4pm are open. Ira offers these times to the patient.
At 10:00:15 AM, while the patient is considering, the front desk books a walk-in patient into Dr. Chen's Thursday 2pm slot.
At 10:00:25 AM, the patient says "I'll take the 2pm." Ira attempts to book. The system detects the conflict (2pm is now taken). Ira responds: "I'm sorry, that 2pm slot was just taken. Dr. Chen still has availability at 3pm and 4pm on Thursday. Would either of those work?"
This scenario happens regularly in busy practices. The speed of the schedule check — happening in the moment of the conversation, not from a cached copy — is what prevents double-bookings and the patient frustration that comes with callback corrections.
Systems that sync on a 5-minute, 15-minute, or overnight batch cycle cannot handle this scenario. By the time their cached schedule updates, the conflict is already baked in.
What Shows Up in Your PMS After Ira Books
When Ira books an appointment, here's exactly what appears in your PMS:
- Patient name (existing patient matched or new patient created)
- Appointment date and time
- Provider assigned
- Operatory assigned (based on your practice's rules)
- Appointment type (cleaning, exam, emergency, etc.)
- Procedure codes (mapped to the appointment type)
- Appointment length (based on your practice's block settings for that procedure type)
- Appointment status: confirmed
- Note: "Booked by Ira [AI receptionist]" (so your team knows the source)
For new patients, a new patient record is created with:
- Patient name
- Date of birth
- Phone number
- Insurance carrier (if provided)
- Preferred provider (if stated)
- Source: AI phone receptionist
Your team doesn't need to re-enter any data. The appointment and patient record are in the system as if a front desk team member had typed them in.
Two-Way Sync in Practice
Two-way sync is where most "integrations" break down. One-way is relatively simple: AI writes to PMS. Two-way means the PMS also communicates back to the AI system. Here's why this matters:
Scenario 1: Front desk reschedules an AI-booked appointment
A patient calls the office directly and asks to move their Thursday 2pm to Friday 10am. The front desk makes the change in the PMS. The AI reminder system sees the change and updates the reminder sequence — the patient now gets a reminder for Friday 10am, not Thursday 2pm.
Without two-way sync, the patient gets a reminder for the wrong day. They either show up Thursday (wrong day), miss Friday (no-show), or call confused (wasting staff time to sort it out).
Scenario 2: Patient confirms via text reply
Ira sends a two-day reminder: "Hi Sarah, this is a reminder of your appointment with Dr. Chen on Thursday at 2pm. Reply CONFIRM to confirm or RESCHEDULE to change." Sarah replies CONFIRM. The appointment status in the PMS changes to "confirmed." The front desk sees it on their schedule view without making a phone call.
Scenario 3: Patient cancels via text reply
Sarah replies CANCEL instead. The appointment status in the PMS changes to cancelled. The time slot is freed. The waitlist system activates — patients who wanted an earlier appointment receive a text offering the newly open slot. First patient to reply YES gets the appointment booked into the PMS.
This entire sequence — cancellation, waitlist activation, outreach, patient response, rebooking — happens without human intervention. Two-way sync makes it possible.
Questions to Ask During a Vendor Demo
These questions will reveal whether a vendor's integration claim is Level 1 or Level 5:
- "Can you show me a live demo where you book an appointment into my PMS while I watch?" Not a screenshot. Not a recording. A live booking into a demo or sandbox instance of your PMS.
- "What happens if someone books an appointment in the PMS while your AI is offering that same time slot to a patient on the phone?" If they can't answer this specifically, their integration isn't real-time.
- "If my front desk reschedules an appointment your AI booked, does your reminder system automatically update?" If the answer is no, they don't have two-way sync.
- "Can your AI create new patient records in my PMS, or does my team have to enter them manually?" Manual entry = Level 1 or 2.
- "What connection method do you use — API, local database, or screen scraping?" Screen scraping (taking screenshots of the PMS and using image recognition) is fragile and slow. API or direct database access is what you want.
- "Is there a middleware layer between your system and my PMS?" Middleware adds latency, translation errors, and a point of failure. Direct connections are more reliable.
- "How does the integration handle multi-provider practices? Can it respect different schedule rules per provider?" A system that treats all providers identically doesn't understand dental scheduling.
The Real Data
Congress Dental deployed Ira across multiple locations with PMS integration. Over 90 days: 1,700 calls handled, 180 appointments booked directly into the PMS, $247K in recovered production. A single-location practice: 417 calls in the first month, 32 appointments booked, $38,400 recovered, average 25-second response time.
These numbers represent appointments that landed in the PMS automatically — no manual entry, no callback, no message-taking. The patient called, spoke to Ira, and hung up with their appointment on the schedule. That's what real integration delivers.
Setup Timeline
PMS integration setup typically takes 5 to 10 business days. The process:
- Connection established to your PMS (API credentials, database access, or cloud connection depending on the system)
- Schedule rules configured: provider schedules, appointment types, operatory assignments, time block preferences
- Patient matching logic configured: phone number lookup, new patient record creation fields
- Test calls run: verify appointments land correctly with right provider, operatory, time, and procedure codes
- Reminder system connected: two-way sync verified between PMS changes and reminder sequences
- Go live: typically starts with overflow and after-hours routing
No hardware installation is required. The connection runs through your existing network (for local PMS systems) or cloud (for cloud-based PMS systems).
Frequently Asked Questions
What if we switch PMS systems?
If your practice migrates from one PMS to another (e.g., Dentrix to Open Dental), the Savvy Agents integration is reconfigured for the new system. Historical call and appointment data is retained on the Savvy Agents side. The reconfiguration process typically takes 3-5 business days.
Can the AI handle different scheduling rules for different providers?
Yes. Each provider can have unique settings: which appointment types they see, available days and hours, preferred operatory, new patient vs. existing patient blocks, and minimum/maximum appointment lengths. Ira respects all of these rules when offering times to patients.
Does the integration affect PMS performance?
For cloud-based PMS systems (Denticon, Curve), the API calls are handled by the cloud infrastructure and have no impact on your local systems. For locally-hosted PMS systems (Open Dental, Eaglesoft), the integration is designed to minimize resource usage. API calls are lightweight and occur only during active phone calls, not as background polling. Practices report no noticeable impact on PMS speed.
