Dental · Outbound

Hygiene Recall Reminders

Calls patients when their six-month cleaning comes due, books the visit on the call, and records the outcome, so recall happens without anyone working the phones.

The challenge

Recall is the steadiest source of hygiene visits, and the easiest task to let slip.

Where it breaks down:

The recall list gets worked in the gaps between everything else.


What it costs:

Cleanings come due and nobody calls.

Patients who aren't reached the first time rarely get a second call.


What it costs:

A six-month cycle quietly becomes a year.

Calls aren't logged the same way every time.


What it costs:

Nobody knows who to try again.

The approach

We designed it for the shape of a recall call: short, friendly, and aimed at a booked visit.

  1. Recall is repetitive and patient work, and often takes more than one attempt.
  2. Patients know their cleaning is due. The barrier is finding a time.
  3. The goal of the call is a booked visit.

The agent had to:

  1. Work the whole recall list, within your calling rules.
  2. Offer real times and book on the call.
  3. Stop when a patient says no, and record it.
The solution

A RevAIvo Voice outbound agent that works your recall list from start to finish.

1

Works the whole list

Runs through your contact list, so no patient is skipped because the day got busy.

2

Books on the call

Offers open times from your calendar (Google Calendar or TidyCal) and books the visit before the call ends.

3

Right person first

Confirms it's the patient before discussing the appointment, and keeps any voicemail to the minimum you set.

4

Outcome on record

Booked, declined, and not reached all land in Pulse, so the next pass through the list starts from facts.

It brings in your team when…

Scoped narrow on purpose. Where you've set a number it can connect the caller; otherwise it logs a callback request for your team.

  • The patient mentions pain or a dental concern.
  • The patient asks about insurance or cost.
  • The patient asks to speak to a person.
  • The patient asks to stop receiving calls. The request is recorded for your team.

What the call sounds like

Illustrative exampleNot a recorded call
Agent

Hi, is this Marcus? This is the dental office calling. It's time for your six-month cleaning. Would you like to schedule it?

Patient

Sure. I'd like a morning if you have one.

Agent

I can offer Thursday at 8:15 or Friday at 9:00.

Patient

Friday works.

Agent

You're booked for Friday at 9:00 for your cleaning. We'll see you then.

Patient

Thanks.

Agent

You're welcome. I'll text you a confirmation when we hang up.

Afterward: Booked, declined, and not-reached outcomes are all in Pulse. Patients who didn't pick up are the ones your next pass through the list starts with. The confirmation goes out when the call ends.

Sent after the call

TextWhen the call ends with a booked visit

Your appointment is booked for Friday at 9:00. See you then. If you need to change it, call (555) 010-0210.

Message wording is illustrative and deliberately minimal: no health details. It goes out when the call ends, based on how the call went.

What changes for your team

An illustrative scenario:

240recall calls a month your team wouldn't have to make
20 hoursof staff time back each month
Every calllands in RevAIvo Pulse with its outcome, ready to review

Say your team handles 600 recall calls a month, and the agent takes 40% of them end to end, at an assumed 5 minutes a call. These figures are assumptions for illustration, not customer results.

In a pilot we measure this with you, on your own calls in RevAIvo Pulse: calls connected, when patients pick up, and outcomes by disposition.

The result

Cleanings that get scheduled when they come due, and a clear record of everyone who wasn't reached.

Recall that actually gets worked, with a person for anything beyond scheduling.

Similar use cases

All dental use cases

Hear it on your own scripts.

Book a live call and we'll scope this to one call type, using your own scripts and rules.

Book a live call

These use cases are illustrative and for informational purposes only. The organizations, people, phone numbers, links, and messages shown are fictional examples, and any resemblance to real businesses or individuals is coincidental. Scenario figures are assumptions, not customer results. Actual results depend on your call volumes, scripts, and setup.