Voice agents connected to Open Dental — cloud or on-premise.
WFW connects to Open Dental Cloud API or your self-hosted Web Service. Appointment reminders, recall outreach, and post-treatment follow-up — all driven by live data from your actual Open Dental database.
Open Dental's open architecture means WFW can read and write custom patient fields your practice defined — not just standard PMS fields. HIPAA BAA included.
Live Data Flow — Recall Outreach Call
HIPAA Business Associate Agreement included
PHI never stored in WFW. All patient data handled via Open Dental API only.
Capabilities
What this integration enables.
Three concrete capabilities unlocked by connecting WFW to Open Dental. The open architecture unlocks custom field support no closed PMS can match.
Live Data
Cloud and On-Premise Support
WFW connects to Open Dental Cloud API for hosted practices, or to Open Dental's self-hosted Web Service for on-premise deployments. Either way, the agent reads live patient data — appointment status, recall-due dates, and treatment history — in real time.
Live Data
Custom Field Extraction and Sync
Open Dental's open architecture lets practices define custom patient fields. WFW can extract those fields during calls and write back custom field values — giving practices running unique workflows a voice layer that understands their actual data model.
Live Data
Recall Outreach from Open Dental Records
WFW queries Open Dental for patients who are past their recall threshold and initiates outbound calls automatically. Each call references the patient's last hygiene date and specific provider — pulled live from Open Dental.
Data Flow
How it works.
From patient identification to appointment write-back — what moves between WFW and Open Dental.
Patient record resolved via Open Dental API
On inbound calls, caller ID or spoken identity is matched to a patient record in Open Dental. The agent has appointment history, recall status, insurance, and any custom fields your practice uses in its active context.
Agent answers with live practice data
Appointment time, provider, treatment status, and balance are pulled from the live Open Dental record — not a static cache. Custom fields surface in the agent's context when relevant to the patient's inquiry.
Actions write back to Open Dental
Appointment confirmed? Status updates in Open Dental. Recall accepted? New appointment created via the API. Custom field values updated from the call? Written back to the patient record. No manual data entry.
Extraction data delivered to your review queue
GET /v2/calls/{id}/extractions returns confirmed appointment data, patient intent, and any extracted fields — including custom Open Dental fields — ready for staff review or downstream workflow triggers.
Use Cases
Before and after.
Real dental workflows transformed by the Open Dental + WFW integration.
Before
Staff calling the next day's Open Dental schedule each morning — 30–45 minutes of phone work that mostly produces voicemails. Cancellations surface day-of.
After
WFW calls every patient 48 hours out with their actual appointment time from Open Dental. Cancellations surface early. Waitlist fills the slot.
Before
Recall list in Open Dental worked manually — inconsistent timing, incomplete follow-through, staff cycling through it between other tasks.
After
WFW monitors recall-due dates in Open Dental and calls when patients are due. The list works itself — staff are notified only when patients request callbacks.
Before
Post-treatment check-ins handled inconsistently. Patients with questions after an extraction or root canal don't always reach someone in time.
After
WFW calls 24 hours post-treatment using Open Dental procedure codes to know what was done. Satisfied patients are directed to leave a review. Concerns are escalated to the provider.
Technical Details
Integration specifications.
Cloud vs. on-premise connection, auth, custom field support, and HIPAA posture.
| Connection method — cloud | Open Dental Cloud API — REST over HTTPS |
| Connection method — on-premise | Open Dental Web Service — self-hosted REST; WFW connects via configured internal/VPN endpoint |
| Auth method | Open Dental API key + Customer Key stored encrypted in WFW vault |
| Custom fields | WFW supports extraction and write-back for Open Dental custom patient fields — configurable per practice |
| Data pulled | Patient name, DOB, appointment date/time, provider, recall-due date, insurance, treatment history, custom fields |
| PHI handling | Never stored in WFW. Held in memory for call duration only. HIPAA BAA required. |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once Open Dental is connected — whether cloud or on-premise. Trigger recall calls, pull extraction data, and monitor agent health via the WFW REST API.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger outbound recall or follow-up call using Open Dental patient data
/v2/calls/{id}/extractionsRetrieve appointment confirmation and custom field data extracted from the call
/v2/agents/{id}Check agent health and Open Dental connection status
Setup
Connect Open Dental in three steps.
Cloud or on-premise. Credentials entered once, BAA signed, integration live.
Add Open Dental credentials
Enter your Open Dental API key and Customer Key in WFW admin. For on-premise, provide your Web Service endpoint URL. Credentials are encrypted in the WFW vault.
Sign the HIPAA BAA
WFW generates a Business Associate Agreement covering PHI handling for this integration. E-sign in the admin portal in under 2 minutes.
Enable on your agent
Toggle Open Dental active on your agent's settings. Map any custom fields you want the agent to read or write. Integration goes live immediately.
Get Started
Connect Open Dental to your voice agents.
Cloud or on-premise. Custom fields supported. Recall, reminders, and post-treatment follow-up automated. HIPAA BAA included.
Connect Open DentalQuestions? Talk to our team →