Recall or reactivation? A decision tree for dental teams

Recall and reactivation are two different lists, and the fastest fix for a messy "inactive patients" report is to stop treating it as one. The decision tree below asks every patient in your practice management system a short run of yes or no questions and lands each one in exactly one of four buckets: active recall, lapsed (reactivation), unscheduled treatment, or unsuitable to contact. Each bucket gets an owner, a working rhythm, and a definition of done. Nobody gets called by two people about two different things, nobody who should be left alone gets called, and the treatment list stops hiding inside the recall list.

This page is for the person holding an inactive patient export of, say, 1,400 rows (an illustrative number) with no idea who to call first, in what order, or who to leave alone. The export is not the problem. It was never sorted, so every call becomes the wrong kind of call for somebody.

What is the difference between dental recall and patient reactivation?

Recall is scheduling patients who are due or nearly due for their next hygiene visit at the interval their provider set; the full definition and the numbers behind it are in our hygiene recall glossary entry. Reactivation is bringing back patients who already fell through recall, typically with no completed visit in 12 to 18 months or more and nothing on the schedule; that one is covered under patient reactivation. The dividing line is a date your practice picks once and holds to, because the two lists need different scripts, different expectations, and usually different owners.

Why does unscheduled treatment come out of the reactivation list first?

Because the patient already said yes. A patient with diagnosed, accepted treatment and no appointment is not a cold call and should never hear the reactivation script. They need a scheduling conversation that picks up where the last visit left off: the tooth, the fee, the thing that stopped them at checkout. That call belongs to whoever presents treatment, not to whoever works hygiene recall, and it runs on its own treatment plan follow-up cadence with its own stop rules.

This is also why the tree checks for unscheduled treatment before it checks recall status. A patient can be overdue for hygiene and have an accepted quadrant sitting in the chart at the same time. If they land on the recall list, the caller books a cleaning and the quadrant waits another six months. If they land on the treatment list, the coordinator books the quadrant and adds the hygiene visit in the same call. Same patient, one call, and the higher-value list wins the tiebreak. For a number on what that pile is worth, the unscheduled treatment calculator gives you one you can defend.

A patient who already said yes to a crown is not a reactivation call. They are a scheduling call that someone dropped.

Which bucket does this patient belong in?

Run the questions in order and stop at the first bucket. The order is the point: exclusions first, so nobody unsuitable gets called; unscheduled treatment second, so accepted work never hides behind a hygiene due date; then the schedule check; then the recall or reactivation split. Three questions end in "leave alone," and that is a legitimate outcome. The cutoffs shown are common choices, not rules; pick yours once and use them in every office.

Print this page from your browser: the tree and the bucket table below come out as plain tables, which is all a front desk needs next to the phone. No download, nothing to sign up for. If you run OpenDental, how to run hygiene recall in OpenDental covers the recall setup behind steps 8 and 9, and how to pull the list the whole tree runs against.

What does each bucket need to stay clean?

A bucket is only useful if someone owns it, works it on a rhythm, knows what finished looks like, and writes down what happened. In a single office two of the owners may be the same person. In a group, the same roles exist at every location, so "done" means the same thing at every office and a manager can compare them.

How does the tree change between one office and nine?

The tree does not change. What changes is who holds it, and how often it gets re-run.

• One office: the office manager runs the tree against a fresh export, the same two people work buckets 1 and 3 every day, and bucket 2 gets a protected weekly hour that does not move when the schedule gets busy.
• A group: the tree is a written standard with identical cutoffs in every office, and the question a regional manager asks is not "are you calling?" but "which bucket, and what did you log?"
• Both: re-run it often, because patients move between buckets every day. A booked hygiene visit takes someone out of bucket 1, a new diagnosis moves them into bucket 3, a returned envelope moves them into bucket 4.

What goes wrong when the list is never sorted?

• Two callers, one patient: the recall caller and the treatment coordinator both reach the same person in the same week, about different things.
• The dismissed or deceased patient who gets called, because the status flag was never set and the export did not filter on it.
• Every child in a lapsed family gets a separate voicemail instead of one conversation with the parent who books for all of them.
• Reactivation hours spent on families who moved away, while patients eighteen months out and still local sit further down the list.

Each of these is a sorting error, and each costs more than the wasted call: a patient who feels processed rather than known is one step closer to being a former patient.

Where the tree breaks, and what we built for it

One person can run this tree by hand against a monthly export, and in a single office with a steady front desk that is often enough. It stops holding when the export is a week old and the buckets have quietly changed, when the recall caller and the treatment coordinator keep separate spreadsheets, or when a group needs to know which of its offices actually worked bucket 2 this month. That is the job Patient Outreach does with the same logic. MyDentalForce integrates with OpenDental today and builds one ranked daily call list per office from that office's own OpenDental data, with recall, unscheduled treatment, and lapsed patients on the same list, rebuilt every morning so the buckets are never stale. Every call outcome is logged and written back to OpenDental, managers see per-office activity and results, and balance outreach runs as its own weekly list, which keeps the collections carve-out in bucket 4 honest.

Start with the export you already have, the tree above, and a highlighter. When the sorting itself becomes the job, across one office or nine, hand it to software that rebuilds the list every morning and logs what happened. See how Patient Outreach ranks the list, or book a walkthrough below and we will run it on your own OpenDental.