It's a busy weekday morning and a parent is on hold, worried. Their child has a baby tooth that's "broken off and just a little piece is left," it's bothering the child, and the dentist mentioned it might need to come out. The parent wants to know how soon they can be seen. Your front desk is mid-check-in with a family at the counter, the second line is ringing, and the call slides to voicemail. A worried parent who can't reach anyone calls the next practice that picks up — and you lose both the appointment and the family. These are anxious, time-sensitive calls you can't afford to drop.
DentalReception AI answers every one of those calls in under two rings, 24/7 — capturing the symptom, the child's history, and the urgency the parent describes in their own words, and booking the visit live in your schedule in Dentrix, Open Dental, Eaglesoft, Curve Dental, or CareStack — while every clinical judgment routes to your team.
Informational only — not clinical, coding, or billing advice; confirm CDT definitions and coverage independently. This page describes call handling only. The AI captures and routes; it does not diagnose, assign codes, triage severity, or quote coverage.
What a D7111 call usually sounds like
D7111 is published as the CDT code for extraction of coronal remnants of a primary (baby) tooth. We state that only at the most conservative level and make no clinical claim; confirm the official CDT definition and any payer rules with your clinical and billing teams.
On the phone, no one mentions a code. A parent says "my son's baby tooth broke and there's a piece stuck," "the back of her tooth crumbled," or "the dentist said the rest needs to come out." The AI receptionist treats this as urgent, pain-adjacent intent and captures the parent's exact words, the child's history, and how soon they want to be seen — it never interprets what the description means clinically.
Capturing urgency without triaging severity
The rule holds across every extraction call: the AI listens and records, it never decides how serious the situation is. For a worried-parent call it gathers what your team needs:
- What the parent describes — the broken or remaining tooth, any pain, swelling, or bleeding, in their own words.
- Whether they call it urgent and how soon they want to be seen.
- Identity and record match — the child's chart, or new-patient intake, so the call lands in the right place.
It then offers an available slot or routes the call to your team. It never ranks how severe the problem is or tells a parent how urgent the case is. See emergency triage and how the AI handles toothache calls.
What gets routed to clinical staff
Anything that needs a clinical or scheduling judgment goes to a person:
- Whether the tooth needs removal and how soon — the agent relays the request; your clinician decides.
- Clinical questions — what the visit involves, aftercare, whether it will hurt the child. The AI never advises.
- Coverage and cost specifics — the agent collects carrier details and relays the question rather than quoting an answer.
| Captured on the call | Written to the PMS |
|---|---|
| Symptom and the parent's words | Notes attached to the appointment |
| Pain, swelling, or bleeding mentioned | Captured for your team |
| Child's identity / record match | Linked to existing or new chart |
| Requested timeframe | Slot booked or task flagged |
| Clinical or billing questions | Routed to your team |
Works alongside your scheduling workflows — see appointment scheduling and how the AI handles broken tooth calls.
Frequently asked questions
Does the AI decide whether the baby tooth needs to come out?
No. The agent never makes a clinical decision and never tells a parent whether a tooth should be removed. It captures what the parent describes — the broken or remaining tooth, any pain or swelling, and the child's history — matches it to a record or starts new-patient intake, and either books an available slot or routes the call to your team with full context. Whether a primary tooth needs extraction is decided by your clinician after examination. The reference to D7111 here is informational only — confirm the official CDT definition independently.
How does it handle a worried parent who says the child is in pain?
It answers in under two rings, stays calm and reassuring in tone, and captures exactly what the parent says — including any mention of pain, swelling, or bleeding — without judging how serious it is. It books the soonest slot you've configured or routes the call to your team with the symptom and the parent's words attached, so a person decides how urgently the child should be seen. The AI never triages severity, never tells the parent how urgent it is, and never gives clinical guidance.
Will it tell the parent what the visit involves or whether it will hurt?
No. What the appointment involves, aftercare, and whether the child will feel anything are clinical questions that go to your staff, never the agent. The AI captures the parent's account and routes the call with a clear summary so your team can respond with the right context. It relays the question; it does not provide clinical guidance or reassurance about the procedure itself.
Does the booking actually land in our schedule?
Yes. For Dentrix, Open Dental, Eaglesoft, Curve Dental, and CareStack, the appointment writes back into your live schedule in real time while the parent is on the call — no re-keying. For other systems, DentalReception AI connects via API or works alongside your existing tools. Every call still produces a summary and any task your team needs, including the symptoms and urgency captured on the line.