ELAYGENT does not claim to work with every Practice Management System. This page lists exactly which PMSs we support today, at what tier, and what each tier requires. If a PMS is not listed here, we will not claim support for it during evaluation or onboarding.
For PMSs in the "Not supported" section, the rest of ELAYGENT (voice receptionist, missed-call recovery, dashboards) still works — only PMS write-back is unavailable.
Open Dental
Direct API
Direct REST API integration for appointment create/update/cancel. Optional signed bridge available for customers who prefer to host the integration themselves.
What it requires
Open Dental customer key (per-tenant) and operatory number (per-location).
ELAYGENT-side `OPEN_DENTAL_DEVELOPER_KEY` configured by ELAYGENT staff.
What it does NOT do
Does not include eligibility verification — eligibility runs through the separate insurance pipeline.
Does not back-fill historical appointments; sync is forward-only from setup time.
NexHealth
Direct API
Direct API integration. NexHealth itself fronts many downstream PMS systems, so this is often the fastest path for clinics on a NexHealth-supported PMS.
What it requires
NexHealth subscriber API token (per-tenant) and location ID (per-location).
Patient ID either pre-provisioned in `pmsExternalPatientId` or supplied via `pmsProviderConfig.patientId`.
What it does NOT do
We do not resell NexHealth — the customer brings their NexHealth account.
Coverage of any specific downstream PMS is bounded by what NexHealth supports for that customer.
Dentrix Ascend
Blocked (partner approval pending)
Direct API client is implemented but gated. Dentrix Ascend requires approved Henry Schein One API Exchange partner access, which ELAYGENT has not yet been granted. Signed-bridge fallback is available today for customers willing to host the relay.
What it requires
Direct mode: blocked until Henry Schein One API Exchange partner approval and `DENTRIX_ASCEND_API_KEY` provisioning.
Bridge mode: customer-hosted relay reachable at a stable HTTPS URL; HMAC shared secret configured.
What it does NOT do
We do not currently claim Dentrix Ascend direct support in sales calls.
Bridge mode requires the customer (or their IT vendor) to operate the relay — we do not host it.
Dentrix (on-premise)
Signed bridge
Supported via signed-bridge webhook only. The customer hosts a relay that receives ELAYGENT events and writes into the on-premise Dentrix database.
What it requires
Customer-hosted bridge reachable at a stable HTTPS URL.
A shared HMAC signing secret configured on both sides.
What it does NOT do
No direct API integration. On-premise Dentrix does not expose a hosted API we can call.
Latency and reliability depend on the customer's bridge implementation.
Any other PMS (generic bridge)
Generic bridge
If a PMS is not named above, the customer can integrate it themselves through the generic signed-bridge webhook contract. ELAYGENT publishes the payload schema; the customer implements the receiver.
What it requires
Customer-hosted bridge implementing the documented webhook contract.
A shared HMAC signing secret configured on both sides.
What it does NOT do
ELAYGENT does not write or maintain the bridge for unsupported PMS systems.
We do not claim 'works with every PMS' — only that the bridge contract is open for customer-built integrations.
Eaglesoft
Not supported
Not currently supported. Patterson Dental Eaglesoft does not expose a hosted API and we do not ship a customer-hostable Eaglesoft adapter today.
What it does NOT do
Customers on Eaglesoft can still use the rest of ELAYGENT (voice receptionist, missed-call recovery, dashboards) — appointments simply will not auto-sync to the PMS.
Curve Dental
Not supported
Not currently supported. No direct integration and no Curve-specific bridge adapter ships today.
What it does NOT do
If a customer wants to wire Curve, they can do it themselves through the generic bridge — but we do not maintain the adapter.
Denticon
Not supported
Not currently supported. No direct integration and no Denticon-specific bridge adapter ships today.
What it does NOT do
Same as Curve: generic bridge is available for customer-built integration.