Covers the hours the server is dark
On-premise means after-hours callers reach voicemail against a book nobody can see.
Yes. Dentrix supports third-party integration through the Dentrix Developer Program, but unlike a cloud system it is an on-premise integration: Henry Schein One states plainly that Dentrix is an on-premise application and the Dentrix API is designed for on-premise integrations, so a cloud service must run something locally in each office.
Dentrix runs on a server in your office, which is why every evening and weekend call lands in voicemail. GetHelpdesk.AI answers those calls, checks real availability against your operatories and Perfect Day blocks, and gets the appointment on the book.
Dentrix is Henry Schein One's long-standing practice management system and the desktop original of the family — a Windows, server-based application that has been the default in private practice since the late 1980s. This page is about that product.
The Appointment Book is excellent when someone is sitting in front of it. The problem is the hours and the moments when nobody is.
On-premise means after-hours callers reach voicemail against a book nobody can see.
Dentrix users report appointment blocks visually covering neighbouring ones, so a rushed booking overwrites a slot nobody noticed.
Booking outside a block only raises an overridable warning. Under time pressure that warning gets clicked away.
Recare lives in Continuing Care on the Family File.
Dentrix updates are a recurring complaint — long installs and disruption.
Reviewers describe long waits on Dentrix's own support line.
An on-premise integration, because that is what Dentrix is. Deployed once, then left alone.
Start setupDesktop Dentrix on a local server is this page.
Because Dentrix is on-premise, the connection runs from within your office rather than from the cloud.
Operatories, providers, appointment types, Perfect Day blocks and your Continuing Care intervals.
Overflow, after-hours or the whole line. Your number does not change and your team keeps working in Dentrix exactly as they do now.
Exactly what is read, written and escalated. Anything marked partial is confirmed during setup against your own Dentrix configuration.
| Action | Supported | Notes |
|---|---|---|
| Answer every call 24/7 | Yes | Independent of your server, so it covers the hours Dentrix is unreachable. |
| Check availability before offering a time | Yes | Read as data rather than from the visual grid, so a hidden appointment cannot be overwritten. |
| Book into the Appointment Book | Yes | Against the correct operatory and provider, honouring Perfect Day blocks. |
| Respect Perfect Day blocks | Yes | Treated as a rule, not as an overridable warning. |
| Work the ASAP and Unscheduled lists | Yes | Outbound calls to fill short-notice openings, with confirmed bookings returned to the book. |
| Emergency triage and escalation | Yes | On your protocol — on-call forwarding, urgent SMS, or your instructions read to the caller. |
| Run entirely from the cloud with no local component | No | Not possible on desktop Dentrix. Henry Schein One requires a local component for cloud applications. |
| Clinical charting, imaging or claims | No | Out of scope. Nothing about your clinical workflow changes. |
Availability is read as records, so overlapping blocks in the grid cannot hide a booked slot.
The block structure you designed is enforced rather than warned about.
Recare and short-notice lists worked by voice, with results written back.
Answering continues while Dentrix is mid-install.
A written record without anyone taking notes during the conversation.
No menu and no transfer.
Deployed the way Henry Schein One requires, not pretending to be cloud.
Availability read as data, not from the grid.
Three different products, three different integrations.
A grid problem that becomes a scheduling problem
A coordinator books over an existing appointment because the block covering it made it invisible at a glance. Two patients arrive for one operatory.
You do not find out until both of them are standing at the desk.
Perfect Day blocks under time pressure
Someone books a long procedure into hygiene block time, gets the warning, and clicks through it because the patient is on the phone and the day is nearly over.
We designed the perfect day and then overrode it about four times a week.
The on-premise gap
A patient with a lost filling calls on Saturday. The server is off, the book is unreachable, and voicemail is all there is.
Every practice on a server has the same hole, and most of us just accepted it.
Still not sure how it would work on your schedule? We will walk through your own Dentrix setup on the call.
Ask us directlyDentrix does not include a native AI receptionist. GetHelpdesk.AI adds one to your Dentrix practice, answering patient calls 24/7 and booking into your Appointment Book while respecting operatories, providers and Perfect Day blocks.
Installed on your workstations against an in-office server: desktop Dentrix, this page. Browser login with no server on site: Dentrix Ascend. Many sites on one central database: Dentrix Enterprise. Separate products, separate integrations.
Not purely. Henry Schein One states that Dentrix is an on-premise application and its API is designed for on-premise integrations, and that a cloud-based application must install a local component to communicate with it.
No. A known frustration in Dentrix is that appointment blocks can visually cover neighbouring ones, so a rushed booking overwrites a slot nobody saw.
Yes. GetHelpdesk.AI encrypts protected health information in transit and at rest, restricts access through role-based controls, and signs a Business Associate Agreement with your practice before the first live call.
Your practice number forwards to GetHelpdesk.AI, either all the time or only when your team does not pick up. The AI answers, identifies the caller, and queries your Dentrix Appointment Book through a local component installed in your office, because Dentrix is on-premise and its API is built for on-premise integrations. Real availability comes back, the AI offers it, and the booking is written to the Appointment Book. There is no new phone system to buy and no handset to replace.
Desktop Dentrix on a server in your office, a number you can forward, and about a week. Setup runs through the Dentrix Developer Program, installs the local component, and maps your operatories, providers, appointment types and Perfect Day blocks so bookings land where a person would have put them. Most practices are live within 5-7 days.
GetHelpdesk.AI is $399 per month flat, and the Dentrix integration is included at no extra cost. There is no per-minute billing and no after-hours surcharge.
Hear the AI answer a call on your own Dentrix schedule. Fifteen minutes, no phone-system change, no commitment.