Prepare an Open Dental Practice for an AI Receptionist

Open Dental AI receptionist setup is a practice workflow decision as well as a connection task. The assistant needs a clearly supported appointment type, a reliable way to match an existing patient and a staff-owned path for requests outside that scope.

Burki's current Open Dental work covers existing-patient general appointments with a selected primary dentist and non-hygiene operatory. It is a bounded integration, not a promise to automate every appointment on the practice schedule.

Establish the access prerequisites

Authorized practice staff must arrange the appropriate API access and keep the eConnector operating. Developer access and a practice's production access are separate matters. Open Dental describes its setup process in the official API developer guide.

Burki's implementation and public setup material exist, but actual practice acceptance and vendor prerequisites remain separate readiness gates. A saved key or healthy connection screen does not establish that an appointment was created correctly in the intended practice.

Use the Open Dental setup guide to review the account requirements. Do not put a practice key in the assistant's prompt or use a public demonstration key as a shortcut to production access.

Choose one scheduling scope

Select the approved primary dentist, eligible non-hygiene operatory, appointment duration and practice timezone. These choices should reflect a real administrative workflow staff understand.

The first question is not “Can the assistant book something?” It is “Which exact appointment may this assistant book for which existing patients?” A narrow answer gives the team a concrete outcome to verify.

New-patient registration, hygienist workflows, clinical procedures, cancellations and rescheduling are outside this release's scope. The assistant should route those requests to practice staff rather than translating them into a superficially similar general appointment.

A hypothetical returning-patient enquiry

Imagine an existing patient asking for a general appointment. The assistant collects the confirmed first name, last name and date of birth needed for the supported match. Once one patient is identified, it checks eligible times and asks the patient to confirm the chosen appointment.

If the caller asks for a hygiene visit instead, the workflow changes. The assistant should explain that staff need to handle that request. It should not book the primary dentist's general slot and hope the practice can correct it later.

This is a hypothetical example for planning. It is not evidence that Burki has completed a live booking in your practice or that the caller has been authenticated for access to private clinical records.

Prepare staff-owned exception paths

Write down what happens when the patient is not found, several possible matches exist, no suitable slot is returned or the booking result is uncertain. Each outcome needs an honest explanation and an actual staff process.

A patient who cannot be uniquely matched should not become a new patient automatically. An uncertain booking should be inspected before another appointment is requested. A clinical question should reach the practice's established process, not an improvised answer from the scheduling assistant.

Keep the minimum necessary information in the handoff. Staff need to know what prevented completion, without receiving an uncontrolled copy of patient information in unrelated tools.

Verify the practice result before patient use

Browser practice uses simulated patients and appointments. It can help assess the conversation, but it does not query the practice or create a real booking. Plan authorized acceptance in an appropriate test practice before relying on the workflow with patients.

Inspect the matched patient, selected dentist, operatory, duration, date and timezone. Have practice staff confirm that the resulting appointment fits their actual scheduling rules. Include an out-of-scope request so the refusal path receives attention too.

The dental voice-assistant page provides the broader administrative context. It should not be interpreted as clinical validation or a blanket compliance guarantee.

Start by asking the practice manager to approve one appointment definition and its exception owner. That single decision makes the connection, instructions and acceptance review much more precise.