The schedule is locked in the building
On-premise means after-hours callers hit voicemail against a calendar nobody can see.
PracticeWorks
Never Miss a Patient Call on PracticeWorks
Yes. PracticeWorks has no native AI receptionist and, as a server-based system that Sensei no longer sells to new customers, it is unlikely to gain one.
PracticeWorks runs on a server that switches off with the lights, so every evening and weekend call goes to voicemail. GetHelpdesk.AI answers those calls, captures a complete booking, and hands your team a summary before the door opens.
- HIPAA compliant & BAA-backed
- Live in about a week
- No new phone system
- 24/7 Answering that does not stop when the server does
- No migration Nothing about your PracticeWorks setup has to change
- Under 1s Answer time, with no hold queue and no IVR menu
About PracticeWorks
PracticeWorks is a general dentistry practice management system from Carestream Dental, now marketed under the Sensei brand alongside SoftDent, OrthoTrac and WinOMS. It is server-based and on-premise, relying on local hardware rather than cloud infrastructure.
- Vendor
- Carestream Dental, marketed as "PracticeWorks, a Sensei product"
- Deployment
- Server-based on-premise, with hosted deployments historically offered
- Best for
- Established general practices with long PracticeWorks tenure and no near-term migration plan
- How we connect
- Secure connection configured per practice against your environment during onboarding
Key benefits
Why PracticeWorks practices add GetHelpdesk.AI
The features are not coming, and the migration is not urgent. This is the gap you can close without touching either question.
Somebody finally says yes
Weave, Arini and NexHealth all publish PMS lists that skip PracticeWorks.
No native reminders to wait for
PracticeWorks users have long reported the absence of built-in text and email reminders.
Migration-agnostic
It works on PracticeWorks now and follows you to whatever you move to later.
Nothing changes inside PracticeWorks
No new module, no version upgrade, no retraining. Your team keeps working exactly as they do today.
HIPAA compliant, BAA backed
PHI encrypted in transit and at rest under role-based access, with a Business Associate Agreement signed before the first live call.
Setup
Setting up alongside PracticeWorks
The phone side is a forwarding change. The schedule side is scoped honestly against a server-based system.
Start setup- 01
Forward the line
Overflow, after-hours or the whole number, changed by your phone admin. Nothing inside PracticeWorks is modified and no version upgrade is needed.
- 02
Capture your booking rules
Appointment types and durations, provider hours, block-outs, your emergency protocol, and the questions you always ask a new patient.
- 03
Scope the schedule connection
PracticeWorks publishes no API, so we establish what is achievable in your specific environment rather than promising real-time sync we have not verified.
- 04
Go live and review
Start with evenings and weekends — the hours you are definitely losing — read the transcripts, then decide how much more of the line to hand over.
Support matrix
What the AI can do inside PracticeWorks
Exactly what is read, written and escalated. Anything marked partial is confirmed during setup against your own PracticeWorks configuration.
| Action | Supported | Notes |
|---|---|---|
| Answer every call 24/7 | Yes | Entirely independent of your server, so it covers exactly the hours PracticeWorks cannot. |
| Capture a complete booking request | Yes | Appointment type, patient details and preferred timing, structured for entry rather than a voicemail to decipher. |
| New patient intake and qualification | Yes | Your own intake questions, asked consistently on every enquiry. |
| Emergency triage and escalation | Yes | Follows your protocol — on-call forwarding, urgent SMS, or your instructions read to the caller. |
| Outbound recall and reminder calls | Yes | Fills the gap left by the absence of native reminders in PracticeWorks. |
| Read live schedule availability | Scoped at setup | Depends on your environment. Established with you before you commit. |
| Write an appointment into PracticeWorks | Scoped at setup | No public API exists. We will not promise automatic write-back we have not verified for your setup. |
| Clinical records or claims | No | Out of scope. Nothing about your clinical workflow changes. |
Core features
Built for PracticeWorks front desks
-
Covers the hours the server is off
Evenings, weekends and holidays — the block where a server-based practice loses everything.
-
Ready-to-enter bookings
Where automatic write-back is not available, your team gets a complete structured booking, not a callback list.
-
Outbound reminders
The native capability PracticeWorks never gained, handled by voice rather than another bolt-on.
-
Consistent new-patient intake
The same qualifying questions every time, captured in writing.
-
Transcript and summary on every call
A written record without anyone having to make notes mid-conversation.
-
25+ languages, detected automatically
No menu and no transfer.
-
Works when the server does not
The after-hours block, finally covered.
-
You are not excluded
Supported alongside the mainstream systems.
-
Comes with you
Migration-agnostic, whenever you move.
In practice
Calls PracticeWorks practices stop losing
01
Friday evening, server off, phone ringing
The structural gap in an on-premise practice
A patient with a lost crown calls at 6:30pm. The building is empty, the server is off, and the schedule is physically unreachable.
Everything we lose, we lose between six at night and eight in the morning.
02
The recall list nobody reminded
No native reminders, ever
Without built-in text or email reminders, recall depends on somebody finding time to call.
We have paid for three separate add-ons to do things the software should just do.
03
Told again that your software is not supported
Ecosystem exclusion
An owner evaluating front-desk tooling checks three vendors and finds PracticeWorks on none of their lists.
After the third vendor said no, we assumed that was just how it was.
FAQ
PracticeWorks questions, answered
Still not sure how it would work on your schedule? We will walk through your own PracticeWorks setup on the call.
Ask us directlyIs PracticeWorks still supported?
Yes. Sensei, the Carestream Dental brand that now owns it, states PracticeWorks is no longer sold to new customers while continuing to support existing users by phone, chat and email.
Does PracticeWorks have an AI receptionist?
No. PracticeWorks ships no native AI phone agent, and as a server-based product in maintenance mode it is unlikely to get one.
Is PracticeWorks cloud-based or server-based?
Sensei describes PracticeWorks as a server-based, on-premise practice management system relying on in-office hardware rather than cloud infrastructure, with hosted deployments historically offered as an option.
Should I move to Sensei Cloud first?
That is entirely your call. Sensei says there is no requirement to move and positions Sensei Cloud as the modern successor, and many practices sensibly defer the migration for years.
What AI phone system works with PracticeWorks?
Very few. Most dental AI receptionists publish support for Dentrix, Eaglesoft, Open Dental and Curve but leave PracticeWorks off the list, and the major patient-communication platforms omit it too.
Can it send appointment reminders?
Yes, and this is a common reason PracticeWorks practices start. The absence of native text and email reminders is one of the longest-standing complaints about the software.
Cover the hours your server cannot
Hear the AI answer a call on your own PracticeWorks schedule. Fifteen minutes, no phone-system change, no commitment.