Open Dental offices get the inquiry as a request, not a mystery voicemail
GreetKeeper answers the call and hands your team a complete request. This page shows exactly where it goes and how your desk books it.
Caller
“My daughter's retainer cracked and she's got a wedding in two weeks. Are you open Monday? I'd rather not go back to the last place.”
What happened next
- Logged the caller as a new-patient inquiry with the reason in plain words
- Confirmed the practice is open Monday and took her preferred morning window
- Emailed the request so Monday's opener sees it first thing
How GreetKeeper connects to Open Dental
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Open Dental | Email or webhook |
What Open Dental is, and how requests reach it
Open Dental is practice management software with an open database, which is unusual in dentistry. Practices pick it partly because their data is reachable and partly because they can hire a developer to extend it.
It runs on a server in the practice, or on a host the practice chose. Its API is available to practices that enable it, so an Open Dental office typically has more wiring options than a comparable Dentrix office.
GreetKeeper hands your desk the request by email or webhook, and the chart stays exactly where it is.
Where the call actually lands
GreetKeeper finishes the call and sends the request to a place your team already checks.
Most practices use the call email and stop there. It carries the caller's name, number, reason for calling and the time they asked for. Whoever opens on Monday reads it and books the chair in Open Dental.
Would you rather work from a queue than an inbox? A Zap can catch our webhook and turn each finished call into a row in a Google Sheet or a task in your team's list, and both of those have real Zapier apps. A practice with the Open Dental API enabled and a developer on hand can go further, and have their own code accept the record from a webhook.
Your team confirms the time in Open Dental itself. GreetKeeper gives the caller a window and a promise that someone will call back to lock it.
The transcript and the summary live in GreetKeeper regardless. That matters on a Saturday, when nobody is at the desk and the call is the only record you have.
Getting it running
About twenty minutes, and nothing here touches your server.
Write down your three most common call reasons
New patient, emergency, and existing patient rescheduling covers most Saturdays. GreetKeeper asks different follow-up questions per reason, and that reason travels with the request.
Send the call email to your front-desk inbox
Every completed call sends one. The fields arrive named and separate, so the caller's mobile does not end up buried inside a paragraph of transcript.
Add a sheet or a task list if an inbox is not enough
This step needs a paid Zapier plan of your own (Professional or above), because catching our webhook runs on that tier. Send inquiry and scheduling data only. Anything clinical stays out of Zapier and stays in Open Dental.
Switch the AI announcement on and test it
Utah requires regulated occupations, including dentistry, to say verbally at the start of the call that a caller is speaking to AI. Turn that setting on, call your own number, and watch the request land.
Running the Open Dental handoff each morning
Scope calls to the caller's name, number, reason and appointment request. Treatment notes and history live in Open Dental itself.
GreetKeeper does not make a HIPAA claim.
Name one person at the desk to confirm requests in the Open Dental schedule each morning. Patients then hear back fast.
A caller describing pain hears your own words and gets an urgent flag on the record, ready for the first callback.
Questions about Open Dental and GreetKeeper
Does GreetKeeper integrate with Open Dental?
It works alongside it. The request reaches your team by email, sheet or task, and a person books it in Open Dental.
We have the Open Dental API enabled. Does that change anything?
It gives your developer more room. GreetKeeper can send the finished call to a webhook, and your own code can accept it and act on it. The signed payload tells your code the call came from us.
Can it take payment or insurance details on the call?
Keep those off the call. GreetKeeper is scoped to inquiry and scheduling data here, and insurance verification is work for your front desk inside Open Dental.
Test it on a Saturday call
Use your own emergency script. Two minutes, no card.