Every vendor claims integration. Almost none define it.
Look at any dental AI receptionist's website and you'll find a logo wall: Dentrix, Open Dental, Eaglesoft, Curve, Denticon. The implication is obvious — plug it in and it works with what you already run.
The word doing all the work there is integrates. It has no agreed definition. I've seen it used for a system that reads your open slots and can't write anything, and for a system that writes appointments in real time and reconciles changes both directions. Same word. Wildly different daily experience for your front desk.
This matters more than pricing, more than voice quality, and more than the feature list. A shallow integration doesn't fail loudly. It fails by quietly creating work for the person you were trying to help.
The four levels, from shallowest to deepest
Level 1: Read-only lookup
The AI can see your availability but can't write to it. A patient calls, the AI finds an open slot, and then — depending on the vendor — either takes a message, sends your front desk a task, or emails someone a summary.
What this feels like in practice: every booking still passes through a human. The AI has moved the work, not removed it. Your front desk now processes a queue instead of answering a phone. For after-hours coverage that's still an improvement. For daytime overflow it often isn't.
How to spot it: ask what happens between the patient hanging up and the appointment existing in the PMS. If the answer includes a person, it's Level 1.
Level 2: One-way write
The AI writes appointments into your PMS. Good — that's the main thing. But changes made in the PMS don't come back.
Where this breaks: your hygienist calls in sick and you clear her Tuesday column in Dentrix. The AI doesn't know. It keeps booking into slots that no longer exist. You find out when three patients arrive for appointments nobody can see.
That specific failure — double-booking after a schedule change — is the most common complaint about mid-tier integrations, and it's structural. One-way sync cannot solve it.
How to spot it: ask directly. "If I block off a column in my PMS right now, how long until the AI stops offering those slots?" A vendor with one-way sync will talk about refresh intervals, manual re-syncs, or tell you to update settings in their dashboard too.
Level 3: True bidirectional sync
Appointments written by the AI appear in your PMS. Changes made in your PMS — blocks, cancellations, provider schedule edits, new appointments booked at the front desk — flow back to the AI.
This is what most practices assume they're buying when they read "integrates with."
How to spot it: the same question as above. A vendor with real bidirectional sync will answer with a timeframe measured in seconds, and they'll usually offer to demonstrate it live.
Level 4: Scheduled file import
Some systems exchange data via a nightly export/import, or a file drop, or a bridge application that batches changes. Technically accurate to call it integration. Functionally, your AI is working from yesterday's schedule.
How to spot it: ask how often data moves. If the answer is "nightly" or "every few hours," you're at Level 4.
Why so many integrations are shallow
This isn't vendors being dishonest. It's that dental PMS integration is genuinely hard.
Dentrix, Open Dental, Eaglesoft, and Curve are architecturally different products, some decades old. Several are server-installed rather than cloud-based, meaning integration requires software running inside the practice's own network. Some have documented APIs. Some have partner programs with waiting lists. Some have neither, and integration means working with the database directly.
Building genuine bidirectional sync against one of them is months of work. Doing it across a dozen means either a very large engineering team, or an abstraction layer that handles the differences once.
Most AI receptionist companies are small and moving fast. The rational choice is often to integrate deeply with one or two popular systems and support the rest shallowly. That's a reasonable business decision — it just isn't visible from the logo wall.
The five questions that reveal the truth
Ask these in a demo. Ask them exactly like this. Vendors with deep integration answer immediately and specifically. Vendors without will pivot to talking about something else.
1. "If a patient books through your AI, when does that appointment appear in my PMS?"
Good answer: a number of seconds, and an offer to show you.
Weak answer: "It syncs regularly" / "Our dashboard shows it instantly."
2. "If I block off a column in my PMS right now, how long until your AI stops offering those slots?"
Good answer: seconds to a minute.
Weak answer: anything involving a manual step, or updating settings in two places.
3. "Which of my providers and operatories does the AI know about, and how does it learn about a new one?"
Good answer: it reads them from your PMS, new ones appear automatically.
Weak answer: you configure them in their system separately.
4. "What happens when the connection to my PMS drops?"
Good answer: a specific behavior — queues writes and retries, or declines to book and transfers to your desk. Either is defensible. What matters is that they've thought about it.
Weak answer: visible surprise at the question.
5. "Can I see it write to a live PMS on this call?"
Good answer: yes, in a sandbox or a demo instance.
Weak answer: a recorded video, or "we can arrange that later."
That last question separates more vendors than the other four combined.
What depth is actually worth
Not every practice needs Level 3.
If you want after-hours coverage only and your front desk processes messages each morning, Level 1 might be genuinely fine. You're buying a better voicemail, and that's a real product.
If you want daytime overflow handled — calls during lunch, during huddles, when the second line rings — you need at least Level 2, and you'll feel the absence of Level 3 the first time someone changes the schedule.
If you're multi-location, or your schedule changes frequently, Level 3 isn't a nice-to-have. Reconciliation work scales with locations, and it lands on the person who has the least time.
One more thing worth asking about
While you're asking integration questions, ask about the Business Associate Agreement.
Any vendor whose system touches patient information needs a current BAA, and they should be able to name their subcontractors — the voice provider, the telephony provider, the integration layer — and confirm those have BAAs too. A vendor who hasn't thought about the chain below them hasn't thought carefully about compliance.
Hesitation here tells you something.
Where Aria sits
Aria uses a dedicated integration layer covering 28 practice management systems, with bidirectional sync — appointments written by Aria appear in the PMS, and schedule changes made in the PMS flow back.
We'd rather you ask us the five questions above than take our word for it.
See how it works · Try the demo line
Ask us the five questions.
Call the live demo line — no signup, no download. Book an appointment and ask what just happened in the PMS.
Try the Demo →