AI Voice Agents for Dental Reminders and Confirmations

AI voice agents for dental reminders and confirmations call patients who already have a visit booked, verify them, and confirm or move the visit in the same call. Each answer is written back to the practice management system, so a cancelled chair reaches the practice's short-notice list that day. Overdue recall patients get a separate call.

Key Takeaways

• Confirmation calls are for booked patients, and recall is a separate call.
• Nothing about the visit is said until the patient passes a check.
• A cancellation written back during the call can refill the chair today.

A cancellation that reaches the front desk too late leaves a chair empty. We read tomorrow's schedule from the practice system, verify then confirm or move each visit, free the chair the same day, and set voicemail, consent and retries in Dograh. It is part of our guide to appointment reminders and confirmations.

Confirmation is not recall

A confirmation call goes to a patient who already has a time in the book. Recall goes to patients who are overdue and have no time at all, so it is a booking call with its own list and script. AI Voice Agents for Dental Recall and Recare Outreach covers that one.

The confirmation call's job is to catch "I can't make it" early enough to fill the chair. Most practices already send reminders. In MGMA's 2026 poll of medical groups, 32% saw rising no-shows even though they already made confirmation calls. Patients in Tebra's 2026 no-show survey blamed work conflicts more often than a lapse of memory. That poll covers medical groups rather than dental offices, but the lesson carries. A louder reminder won't help a patient whose shift changed. A call that moves the visit will.

Read tomorrow's schedule from the PMS

The call starts from your practice management system (PMS), which holds the real schedule. Each afternoon, export the next day's appointments as a CSV with a phone_number column. Columns such as the appointment time, provider, location and procedure length become variables the agent uses after the check passes. The file runs as one of Dograh's Campaigns. If your PMS can call a web address, it can instead start one call per appointment through the API Trigger.

During the call, the agent reads and writes the schedule through an HTTP API tool pointed at your PMS's API. For many practices that means a small service your team runs in front of the PMS, which keeps the agent's view to the fields a confirmation needs.

Schedules change after the export. Pre-Call Data Fetch, set to Outbound calls only, re-reads the appointment once the patient answers, so the agent never confirms a time the front desk has already moved.

The call: verify, then confirm or move

The Greeting Text names the practice and gives a callback number. If a spouse or a teenager answers, they hear only that, and the agent asks when the patient is easiest to reach. Nothing about the visit is said to anyone else.

The calling number pulls up a chart, yet the voice on the line could belong to anyone in the household. The agent asks for the patient's date of birth before it names the time or the treatment. A crown preparation or an extraction is health information, and a dental schedule is full of it.

Then the agent names the visit and asks whether it still works. A yes is written back. A no leads to live slots, read from the PMS during the call, and the patient picks one. Add a Preset Parameter named workflow_run_id with the value {{initial_context.workflow_run_id}} to the booking request, so a repeated request never books twice. The agent reads back the new time before the call ends.

Many practices confirm in Spanish as well. Greeting Text plays before the agent can hear the patient's language, so write it in both, for example "Hola, hello". Our post on Spanish AI voice agents for healthcare covers where an interpreter takes over.

Open Source Alternative to Vapi / Retell

Self-hosted voice agent platform — no per-minute fees

dograh-hq/dograh

Star on GitHub

Free the chair the same day

A cancellation is only useful if the front desk learns about it in time. So the agent writes it to the PMS during the call, and the chair shows as open while there's still a day to fill it. Who gets that chair is your practice's decision, made from its own short-notice list.

After every call, a Webhook node sends the outcome to your system: confirmed, moved, cancelled or unreachable, with links to the transcript and recording. The front desk starts the morning knowing which chairs are firm. A temporary failure on your side is retried automatically, so the list doesn't go missing because a server blinked.

If you're deciding which dental call to hand over first, our post on AI voice agents for dental clinics ranks them.

Voicemail, consent and retries

Many confirmation calls reach voicemail, and anyone in the house can play it back. Voicemail handling is off by default. Turn it on in the agent's Settings, set "When voicemail is detected" to "Leave a message", and keep the message to a first name, the practice's name and a callback number.

Most confirmation calls to mobiles rest on the FCC's healthcare calling exemption, under the Telephone Consumer Protection Act (TCPA). It allows one call or text a day to each patient and three a week, generally a minute or less, with the provider's name and contact number. Allow Greeting Interruption is on by default on the Start Call node, so switch it off to make sure that notice plays in full. Any retry lands on the same day, so set Max Retries to 0 and use Redial Campaign the next morning for patients who didn't answer.

A call that moves a visit can run past a minute, so consent on file, collected when the patient booked, is generally the safer basis. A confirmation about the patient's own visit is a treatment communication, outside HIPAA's definition of marketing. Mention a whitening special and that changes, so keep offers off the call. Confirm your own setup with counsel.

A patient who mentions pain or swelling is handed to the front desk through Transfer Call, available on Twilio, Telnyx, Plivo, Cloudonix and Asterisk ARI. The practice's line rings first, and the patient is joined only once a team member picks up. A medical emergency gets a fixed line on its own pathway: "If this is a medical emergency, please call 911 now."

Where dental call data sits

Dental confirmation calls carry patient names and procedures, so decide where they live before launch. You can run Dograh on the practice's own servers or on Dograh Cloud. On your own servers, the platform itself never receives a patient's details or calls, which is why the platform needs no business associate agreement (BAA).

The speech and language providers you call with your own keys still hear each patient's voice, so each one needs a BAA of its own, unless open-weight models run on the practice's servers as well. Whether the phone carrier needs one depends on what it stores, and a cloud host running those servers needs one too. Before the first patient call, set ENABLE_TELEMETRY=false and remove POSTHOG_API_KEY, since a self-hosted install otherwise sends anonymous usage telemetry. A self-hosted practice pays no per-minute platform fee, though servers, model keys and phone minutes still cost money, while Dograh Cloud adds a 1¢-a-minute platform fee.

Before launch, add procedure names and your providers' names to the Dictionary in the agent's Settings, and run the call on a real phone line. Most phone calls reach the agent as 8 kHz audio, while a browser test runs at 16 kHz, so "prophylaxis" can sound different on a mobile than in the editor.