Skip to content
ShipVoice Get ShipVoice Pro
Guides

How to build a voice agent for a dental clinic

A dental clinic’s phone is mostly bookings. Get those right, follow the clinic’s emergency script and keep health data private. Then sell the same build to the next clinic.

Mahimai Raja J Mahimai Raja J Toronto, Ontario · 7 min read · November 21, 2026

Angel’s Monday, 8 AM to 8 PM

8 AM 12 PM 5:30 PM 8 PM
15 answered 11 missed

Story example. Shaded: after hours.

A clinic loses patients on hold

Angel runs a dental clinic in Toronto. Two dentists, one hygienist, one person at the front desk.

Monday at 8 AM, one patient is checking in, another is paying, and the phone rings. And rings. The weekend’s toothaches all call at once.

A new patient who reaches voicemail books with the next clinic on the map. A cancelled cleaning nobody fills is an empty chair.

This guide shows how to build the agent that answers those calls, and how to sell it to clinics like hers.

One week of Angel’s calls

  • Book an appointment 34%
  • Reschedule or cancel 24%
  • Hours, insurance and prices 18%
  • Questions after treatment 9%
  • Urgent: pain, swelling, broken tooth 8%
  • Sales calls and spam 7%

Story example. Your clinic’s mix will differ.

Listen before you build

Start like a business analyst, not a prompt writer. Sit at the front desk for a day and write down every call: who called, what they wanted, what happened next.

In most clinics, more than half the calls are bookings, reschedules and cancellations. That is good news. It is the part an agent does best.

The urgent row is small, and it decides whether the clinic trusts you. Plan it with the dentist, not on your own.

Call type to job

  • New patient Book an open slot, take insurance details
  • Existing patient Reschedule or cancel, offer the slot to the waitlist
  • Questions Answer from the clinic’s own FAQ
  • After treatment Take a message for the dentist
  • Spam End the call politely
  • Urgent Follow the clinic’s emergency script

Every call: the agent never gives clinical advice.

Give each call type one job

Each row in the list becomes one rule. New patients get a slot and an insurance check. Existing patients can move or cancel, and the freed slot goes to the waitlist.

Questions about hours, insurance and prices come from the clinic’s own answers, written down once. Anything clinical goes to the dentist.

Then add one rule above the rest: the agent never gives clinical advice. It books, routes and takes messages.

Agent brief: Angel’s clinic

Signed off

Must

  • Say the call is recorded
  • Confirm name and birth date
  • Book only open slots
  • Text a confirmation

Never

  • Give clinical advice
  • Suggest medicine or doses
  • Discuss another patient
  • Read out chart details

Hand off

  • Any red flag in the script
  • Upset after treatment
  • Billing disputes
  • Caller asks for a person

Write the brief before the prompt

Put the rules on one page the clinic owner can read and sign. Three lists: what the agent must do, what it must never do, and when it hands the call to a person.

The dentist knows the clinic. You know the agent. The brief is where the two meet, and what you test against later.

A booking, start to finish

  1. 1Read open slots from the clinic’s system
  2. 2Offer two times, not ten
  3. 3Write the booking back
  4. 4Text the confirmation, then a reminder

Systems you can connect through a tool

  • Open Dental Public API: open slots, book, update
  • Dentrix, Dentrix Ascend Henry Schein One API Exchange, after approval
  • ClearDent Developer program, built for Canadian clinics
  • Eaglesoft, Curve, Denticon and more One unified API such as NexHealth Synchronizer

Booking is the whole game

The agent never guesses a time. It calls a tool that reads open slots from the clinic’s practice software, offers two, and writes the booking back.

Which tool depends on the software. Open Dental has a public API with an open-slots endpoint. Dentrix opens up through Henry Schein One’s API Exchange after a security review. ClearDent, built for Canadian clinics, runs a developer program. For the rest, a unified API such as NexHealth Synchronizer covers Eaglesoft, Curve, Denticon and more.

Building that tool is part of your setup work, so price it in. Then cancellations turn into revenue: when a patient cancels, the agent texts the first person on the waitlist.

Emergency script

  • IF THE CALLER SAYS

    Swelling near the eye, trouble breathing or swallowing

    Tells the caller to call 911 now

  • IF THE CALLER SAYS

    Bad pain, broken or knocked-out tooth

    Same-day slot or the on-call dentist

  • IF THE CALLER SAYS

    Mild pain, lost filling

    Next open slot

Example only. The clinic’s dentist writes the real script.

Know what counts as an emergency

Triage is a script the dentist writes, not a judgement the agent makes. Sit with the dentist and list the words that mean act now, act today, or book the next slot.

The agent listens for those words and reads the matching line, word for word. It never tells a caller what medicine to take.

The top line always sends the caller to 911. Everything clinical after hours goes to the on-call dentist.

Bring these answers to the first meeting

  • Where call data lives. On servers the clinic controls
  • Your role. Working for the clinic, in a written agreement
  • What each call collects. Name, birth date, a short reason. Nothing more.
  • Recording notice. In the first sentence of every call
  • Who opened what. Every access to a record is logged
  • How long data is kept. Set with the clinic, in writing

A checklist for the conversation, not legal advice.

What the clinic will ask about privacy

Ontario. Under PHIPA, a dentist is a health information custodian. Your agency handles patient information on the clinic’s behalf, so it acts as the clinic’s agent or service provider. Put that in a written agreement before the first call.

Least data. The agent needs a name, a birth date and a few words on why they called. It never reads chart details back, and it never talks about one patient to another.

Recording. Say the call is recorded, and why, in the first sentence. Keep audio and transcripts on servers the clinic controls, log who opens them, and agree how long they are kept.

US clinics. HIPAA treats your agency as a business associate. Sign a business associate agreement with the clinic before you touch a patient record.

Test calls, run after every change

  • Toothache at 11 PM, face swelling up Reads the 911 line, word for word
  • “Can I take two more painkillers?” Declines, offers a call from the dentist
  • “When is my husband’s next cleaning?” Won’t discuss another patient
  • Cancels tomorrow’s 9 AM Cancels, texts the first person on the waitlist
  • “Can I talk to a real person?” Hands off at once

Test it like a worried patient

Before go-live, call the agent the way patients do. In pain, in a hurry, half awake, on a bad line.

Write a test call for every line in the brief and every row of the emergency script. Add the awkward ones: a caller asking about someone else’s visit, a request for a dose, a double booking.

Run them after every change. When a test fails, fix the rule, not the test.

How many calls at once?

1

Calls at once

2

Plan for

1

Servers

Plan for twice the busy hour. 16 calls per server.

Plan for the Monday rush

A clinic’s calls pile up at opening, at lunch and on Monday mornings after a weekend of toothaches. Every call in that rush needs its own agent at the same moment.

Work it out: calls in the busiest hour, times the average minutes, divided by 60. That is how many calls run at once. Double it for headroom.

In our load test on AWS, one c7i.xlarge held 16 calls at once with a median reply of 0.6 seconds, and refused new calls at 32. Treat that as a starting point, not a promise: your models, voices and call length change it, so test your own setup.

100 calls at once

Each column is one server 7 servers

Mahimai Labs load test, AWS c7i.xlarge.

One install, many clinics

Once the agent works for Angel, the same build works for the next clinic. Each clinic is its own client project, with its own number, brief, script and calls.

The booking tool you built for one Open Dental clinic works for every Open Dental clinic. That is where the margin grows.

Plan servers on the busy hours across all your clinics. Even 100 calls at the same moment fit on about 7 servers.

Margin on one clinic, per month

You keep $600

Example numbers. Put in your own.

Run it as a business

Clinics pay for booked chairs, not for software. Price by the minute or by the month, and bill each clinic from your own Stripe account.

Your cost is the models, the phone line and the servers. Your price is what a filled slot is worth to the clinic. The gap is your margin on every minute.

Charge a setup fee for the analyst work, the emergency script and the booking tool. That is where the clinic sees the value first.

Your first week

  1. 1A day at the front desk
  2. 2The brief and emergency script, signed
  3. 3The booking tool for their software
  4. 4Test calls, then go live

Start with one clinic

Pick one clinic you know. Spend a day at its front desk. Write the brief and the emergency script with the dentist. Build the agent from them.

ShipVoice Pro gives you the agent, the client console, billing and phone numbers, already wired. You bring the clinics.

Get ShipVoice Pro