AI phone assistant for dental practices
Toothache will not wait and recalls do not book themselves. Tel-Agent answers both and keeps every recording on your own machine.
- Which tooth
- Swelling to transfer
- Recall calls
Why a dental practice misses calls it cannot afford to miss
Two kinds of call arrive on a dental practice phone and they need opposite handling. Somebody in pain needs a person, fast. A recall - the check-up due in six months - is never urgent enough to make, so it quietly does not get booked. Both land while the surgery is occupied and the person who could answer is chairside, which is why an AI phone assistant for a dental practice is a scheduling problem before it is a technology one.
How the AI receptionist handles a toothache call
It answers on the first or second ring, in the language the caller is speaking, while the surgery carries on.
It asks which tooth, since when, and whether there is swelling - the three answers a dentist needs before deciding anything.
If an answer matches a rule the practice set as urgent, the call is transferred to a person immediately rather than handled.
If it is not urgent, it offers the next open slots and takes a callback number.
The whole call is written down - who rang, when, what they said and what was agreed - in one searchable archive on your own server.
What the agent is told to ask
Written by you, in your own words, as the assistant’s instructions.
What a dental phone assistant should and should not decide
What it does
- Answers every call during surgery hours, at lunch and after closing
- Captures the tooth, the duration and the swelling in the patient's own words
- Transfers immediately on any answer the practice marked urgent
- Offers open appointment slots and takes recall callbacks
- Keeps the recording and the transcript on the practice's own machine
What it never does
- Decide clinically whether a patient needs to be seen
- Quote a price that is not in the practice's own catalogue
- Estimate the cost of a treatment it has not been given
- Give advice about pain relief or medication
- Copy a recording to any server outside the practice
Questions
What should an AI phone assistant ask a dental patient in pain?
Which tooth or which side, how long it has hurt, whether the face is swollen, and whether they can come in today. Swelling is the one that decides whether this is a call to schedule or a call to put straight through, so the practice sets it as a transfer trigger rather than leaving it to the model.
Can it handle dental recall appointments?
A recall is the easiest call a practice makes and the one that most often does not get made. The assistant takes the callback, offers the next open slots and notes the preference, and the practice confirms. It proposes; it does not write into a live calendar.
Do dental patients accept talking to an AI receptionist?
The ones calling about pain want to be heard and passed on quickly, which is exactly what a transfer trigger does. The ones calling to move an appointment mostly want it done without waiting on hold.
Is a call about toothache health data under the GDPR?
Yes. A symptom described on the phone is data about health, which Article 9 of the GDPR treats as a special category. That is the argument for keeping the recording and the transcript on a machine the practice controls rather than in a vendor's cloud.
Can a dental phone assistant quote a price for a treatment?
Only if the practice gave it one. The safe instruction, and the one shipped in the example prompt, is to never quote a price that is not in the catalogue and never estimate - a colleague rings back instead.
Does it work with our practice management software?
The agent reaches other systems through a generic HTTP tool and webhooks, so dental software with an API can be wired to it. Tel-Agent is pre-alpha and none of this is installable yet.
Does the EU AI Act allow an AI to answer a toothache call?
Yes, under Article 50 of Regulation 2024/1689, which asks that the caller be told they are speaking to a machine - that line belongs in the greeting you configure. Annex III names emergency healthcare triage, so anything that ranked callers by how ill they sound would be a high-risk system. The distinction the Act draws is between assisting and deciding, and this agent assists: it never judges how urgent a symptom is. Austria's KI-Servicestelle at RTR publishes the same reading of the transparency duty.
Who is the data controller for what a caller to a dental practice says on the phone?
You are. A toothache call is health data, which Article 9 treats as a special category, and Tel-Agent is self-hosted with your own model keys, so the recording, the transcript and the record it writes stay on your server and never reach Dpro GmbH. There is no processor agreement to sign with us because we never receive the data, and the source is AGPL-3.0, so you can check that rather than take our word for it.
Can a dental practice run this in the United States?
There is no single federal AI statute to comply with, but a phone line carries older rules. A US practice is under HIPAA, and HIPAA is where self-hosting pays: there is no business associate agreement to sign with us, because no call reaches us. Consent to record is set state by state, and California and Illinois among others want every party to agree. Running the software yourself makes you the caller of record, so the disclosure and the recording switch are yours to set.
Not usable yet. The day it answers a real call will be a release, not a newsletter.
Watch the repository
