It's mid-morning and the caller is rattled — their implant crown "came off" or "fell out," and they're holding it in their hand. It's not life-threatening, but to the patient it feels like one, and they want to be seen as soon as possible. But the front desk is buried in the morning rush and the call rings to voicemail. A loose or lost implant crown is one of the easiest visits to book — but only if your phone is answered the moment it rings.
DentalReception AI answers every one of those calls in under two rings and books the recement visit live, 24/7 — writing it directly into your schedule in Dentrix, Open Dental, Eaglesoft, Curve Dental, or CareStack while the patient is still on the line.
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, or quote coverage.
What a D6092 call usually sounds like
D6092 is widely published as the CDT code for the recement or rebond of an implant- or abutment-supported crown. We state it only at that conservative level; confirm the official CDT definition and any payer rules with your clinical and billing teams.
On the phone, no patient asks for "D6092." They say their "implant crown fell off," "the cap came loose," or "my tooth came out but it's an implant." The AI receptionist recognizes the intent and treats it as a booking — capturing it, never interpreting the clinical fix or making a coding decision.
What the AI can safely capture and schedule
For an implant patient with a loose or lost crown, the agent moves quickly:
- Confirms the patient is established and pulls their record so the visit lands on the right chart.
- Captures what happened — when the crown came off, whether they still have it, and whether they're in pain — so your team can prioritize.
- Books the recement appointment live in the correct provider column, or routes urgent cases to staff. See appointment scheduling.
- Flags the case so your coordinator sees it's an existing implant patient. See dental implant calls.
What must be routed to clinical staff
The AI captures and schedules; it never advises on the repair or any symptom. These go to your team, not the agent:
- Clinical questions — what's wrong, how serious it is, whether the patient should do anything in the meantime, or any "is this an emergency?" judgment. The agent captures and routes; a person decides.
- Cost and coverage specifics — what a recement costs or whether a plan contributes. The agent collects details and relays the question rather than quoting an answer.
- Code or billing requests — anyone asking what will be billed is routed to staff.
Anything beyond booking the visit and capturing context becomes a task or transfer for the front desk.
Context passed into your PMS
Because the booking writes back in real time, your team opens each repair ready:
| Captured on the call | Written to the PMS |
|---|---|
| Patient identity / record match | Linked to existing chart |
| When the crown came off | Notes on the appointment |
| Pain or urgency reported | Flagged for staff prioritization |
| Recement-visit intent | Appointment booked in correct column |
| Clinical or cost question | Task routed to clinical staff |
This is a natural fit for dental implant practices, and it works alongside the rest of your workflow — see the confirmed integrations.
Frequently asked questions
Does the AI assign the D6092 code to the appointment?
No. The agent captures the patient's request and books the visit; it does not assign, confirm, or bill any CDT code. Code selection stays with your clinical and billing staff at the point of care. The reference to D6092 here is informational only — confirm the official CDT definition independently. The AI captures what happened, books the recement in the right column, and writes a clear summary for your team.
What if the patient is in pain or thinks it's an emergency?
That detail is captured and routed, not judged by the AI. If a patient describes pain, bleeding, or anything urgent, the agent records it and flags the call to your front desk or triage workflow with full context, so a person decides how quickly the patient should be seen. The AI never diagnoses, assesses severity, or gives at-home instructions — it makes sure the urgency reaches your team fast.
Can it tell the patient what the recement will cost?
No. Cost and coverage are routed to your team, not guessed. The agent captures the patient's insurance details and answers the general questions you configure, but specifics are relayed to staff so the people authorized to give those answers do.
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 line — no re-keying. For other systems, DentalReception AI connects via API. Every call still produces a summary and any needed task.