It's a busy Monday and a caller is holding, uneasy. A wisdom tooth in the back is "stuck and only partly through," it's been aching, and a dentist already told them it'll need surgery to remove. They want a date, they're nervous about the procedure, and they have questions. Your front desk is mid-check-in with a line at the counter, the second line is lit, and the call rolls to voicemail. A patient who's been referred for surgery and is in some pain doesn't wait — they call the next office that answers and book there. These are sensitive, high-intent calls you can't afford to miss.
DentalReception AI answers every one of those calls in under two rings, 24/7 — capturing the symptom, history, referral, and urgency the patient 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 and surgical 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 D7230 call usually sounds like
D7230 is published as the CDT code for removal of a partially bony impacted 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 surgical teams.
On the phone, patients describe symptoms and often a referral, not a code: "my wisdom tooth is partly stuck in the bone," "it's been aching and won't come in right," or "my dentist said it needs surgery to take out." The AI receptionist treats this as urgent intent and captures the patient's exact words, history, and any referral — it never interprets what the description means clinically or decides how the tooth is impacted.
Capturing urgency without triaging severity
The rule holds: the AI listens and records, it never decides how serious the problem is. For a partial-bony impaction call it gathers what your team needs:
- What the patient is feeling — aching, swelling, the stuck tooth, in their own words.
- Any referral details — who referred them and for what.
- Whether they call it urgent and the soonest they can come in, plus identity and record match.
It then offers an available consult or surgical slot or routes the call to your team. It never ranks how severe the case is or tells a patient how urgent it is. See emergency triage and how the AI handles toothache calls.
What gets routed to clinical staff
Anything that needs a clinical, surgical, or scheduling judgment goes to a person:
- Surgical and severity decisions — whether removal is needed and how soon. The agent relays; your team decides.
- Clinical questions — what the procedure involves, sedation, risks, recovery. 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, aching, and the patient's words | Notes attached to the appointment |
| Referral details | Captured for your team |
| 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 surgical-scheduling workflows — see appointment scheduling and how the AI handles broken tooth calls.
Frequently asked questions
Does the AI decide whether the impacted tooth needs surgery?
No. The agent never makes a clinical or surgical decision and never tells a patient whether a tooth should be removed or what the procedure requires. It captures what the patient describes — the stuck, partly erupted tooth, the aching, and any referral — 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 partially-bony impacted tooth is removed and how is decided by your clinician after examination. The reference to D7230 here is informational only — confirm the official CDT definition independently.
How does it handle a patient nervous about the procedure?
It answers in under two rings, stays calm and respectful, and captures exactly what the patient says — including the pain, the referral, and the worry they express — without judging how serious it is. It books the soonest consult or surgical slot you've configured or routes the call to your team with the symptoms and referral attached, so a person decides how urgently they should be seen. The AI never triages severity, never tells the patient how urgent it is, and never gives clinical or surgical guidance.
Will it explain what the surgery involves, sedation, or recovery?
No. What the removal involves, sedation options, risks, and recovery are clinical and surgical questions that go to your staff, never the agent. The AI captures the patient's account and any referral 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 or surgical guidance.
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 patient 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, referral, and urgency captured on the line.