DentalReception
🦷 RestorativeDental Code · CDT

D2920

D2920 Dental Call Handling for Re-Cement Crown

How DentalReception AI handles D2920 calls — what it captures, what it routes to your clinical team, and the context it writes into your PMS.

A patient calls because their crown came off — maybe while they were flossing, maybe biting into something — and they're holding it in their hand wondering what to do next. It should be a quick, reassuring call and a same-week appointment, but your front desk is mid-checkout and the phone rings out. Now the patient is anxious, searching online for whether they can glue it back themselves, and your easy re-cement visit is at risk of becoming a missed patient. A crown that simply needs re-seating is one of the fastest appointments you book — which is why losing the call stings.

DentalReception AI answers every one of those calls in under two rings and books the visit live, 24/7 — writing the appointment 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 D2920 call usually sounds like

D2920 is published in CDT references as the re-cement or re-bond of a 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, patients never use the code. They say "my crown fell off," "my cap came loose," or "it came out and I still have it." The AI receptionist recognizes that intent and treats it as a re-cement scheduling request — capturing the booking, not interpreting the crown or why it came off.

What the AI can safely capture and schedule

For a re-cement crown request, the agent handles the booking without a human:

  • Confirms the patient and pulls their record so the visit lands on the right chart and provider.
  • Books an appropriate slot in the right column, live during the call. See appointment scheduling.
  • Captures whether the patient still has the crown so the front desk knows what to expect.
  • Captures or refreshes insurance details before the visit — see insurance verification.
  • Writes a clear summary to the record. See call summaries.

For related call flows, see how the AI handles crown calls and lost crown calls.

What must be routed to clinical staff

The line is simple: the AI captures and schedules, it never advises. These go to your team, not the agent:

  • Clinical questions — pain, sensitivity, whether the crown can be re-cemented or needs replacing.
  • Coverage and cost specifics — what re-cementing costs or whether the plan pays. The agent collects details and relays the question rather than quoting an answer.
  • Code or billing requests — patients asking what will be billed are routed to staff.

Anything outside a clean booking 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 appointment ready to go:

Captured on the callWritten to the PMS
Patient identity / record matchLinked to existing chart
Re-cement / crown-came-off intentAppointment booked in correct column
Whether patient still has the crownNote on the appointment
Insurance details (if new or changed)Attached to record for verification
Full call summaryNotes on the appointment

Frequently asked questions

Does the AI assign the D2920 code to the appointment?

No. The agent captures the patient's re-cement 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 D2920 here is informational only — confirm the official CDT definition independently. The AI recognizes the crown-came-off intent, books the appointment, and writes a clear summary for your team.

Can it tell a patient whether re-cementing the crown is covered?

It collects and relays, it does not quote. The agent captures the patient's carrier and member details and answers the general questions you configure. Anything specific — the cost of re-cementing or what the plan pays — is routed to your team rather than guessed, keeping cost and coverage statements with the people authorized to make them.

What if the crown is broken or the patient is in pain?

That call stops being a routine booking. If a patient describes pain, a broken crown, or a tooth that hurts under it, the agent does not treat it as a simple re-cement. It captures the detail and routes the call to your front desk or triage workflow with full context, so a person decides how urgently the patient should be seen. The AI never diagnoses.

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 needed task.

Hear it answer your front desk's calls

Listen to a sample call, then point your after-hours line at DentalReception AI in an afternoon. No new hardware.