It's late afternoon and a parent calls because their child has been pointing at one back tooth and won't eat dinner. Or an adult patient says a tooth has been "throbbing since last night" and they want to be seen today. These are not calm recall calls — the person on the line is worried, sometimes in pain, and they need to know they can get in. When that call rings through to voicemail at lunch or after close, the patient doesn't wait. They call the next practice, or they end up in an urgent-care chair that was never yours. Pain-driven calls are the ones you least want to miss.
DentalReception AI answers every one of those calls in under two rings, 24/7 — capturing the symptom and urgency the patient describes and booking the visit live in your schedule in Dentrix, Open Dental, Eaglesoft, Curve Dental, or CareStack — while routing every clinical judgment 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 D3220 call usually sounds like
D3220 is published as the CDT code for a therapeutic pulpotomy — a procedure on the pulp of a tooth, often associated with primary teeth or with relieving pain before further treatment. 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 patient asks for a "pulpotomy." They describe what they feel: a child crying about a tooth, throbbing pain, swelling, sensitivity to hot or cold, or a dentist elsewhere who "said it needs a root canal or something." The AI receptionist treats every one of these as an urgent intent — it captures the words the patient uses without interpreting what they mean clinically.
Capturing urgency without triaging severity
The line is firm: the AI listens and records, it never decides how serious a problem is. For a pain-driven call it gathers what your team needs to prioritize:
- What the patient is feeling, in their own words — pain, swelling, when it started, whether it's getting worse.
- Whether they say it's an emergency, and how soon they want to be seen.
- Identity and record match, so the call lands on the right chart.
It then books an available urgent slot or routes the call to your team. It does not rank the severity of symptoms or tell a patient how urgent their situation is. See emergency triage and the related handling of toothache calls.
What gets routed to clinical staff
Anything that requires a clinical or scheduling judgment goes to a person:
- Severity decisions — whether the patient needs to be seen today, sent elsewhere, or directed to an ER. The agent relays the symptom; your team decides.
- Clinical questions — what the procedure involves, whether a tooth can be saved, pain management. 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 urgency in patient's words | Notes attached to the appointment |
| Identity / record match | Linked to existing or new chart |
| Requested timeframe ("today", "ASAP") | Urgent slot booked or task flagged |
| Anything clinical | Routed to your team for review |
Works alongside your urgent-care workflows — see how the AI handles root canal calls and appointment scheduling.
Frequently asked questions
Does the AI decide whether a pulpotomy is needed?
No. The agent never makes a clinical decision and never tells a patient what procedure they need. It captures the symptoms the patient describes, matches them to a record, and either books an available urgent slot or routes the call to your team with full context. Whether a tooth needs a pulpotomy, a root canal, or any other treatment is decided by your dentist at the point of care. The reference to D3220 here is informational only — confirm the official CDT definition independently.
How does it handle a patient who is clearly in pain?
It treats the call as urgent and captures exactly what the patient says — where it hurts, when it started, whether there's swelling — without judging how serious it is. It then books the soonest appropriate slot you've configured or routes the call straight to your front desk or triage workflow with the symptom notes attached. The AI never tells a patient how urgent their situation is or whether to go to an emergency room. A person on your team always makes that call.
Will it tell a parent whether their child's tooth can be saved?
No. Questions about whether a tooth can be saved, what the treatment involves, or how to manage a child's pain are clinical and go to your staff, never the agent. The AI captures the parent's description and the urgency, books or routes the visit, and writes a clear summary so your team is ready. It relays concern; it does not give clinical guidance or reassurance about outcomes.
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 urgent call still produces a summary and any task your team needs, so nothing about a pain-driven call gets lost.