AI voicemail triage for dental offices
Your voicemail box fills up overnight, every night. Oriva reads what is in it and ranks it by how soon someone needs to act, so your team opens a sorted queue instead of a stack.
What the first hour actually looks like
One person checking in a patient, taking a call, and working last night's messages, all before nine. Roughly a third of inbound calls go unanswered, and that is arithmetic, not a staffing failure.
By morning the box holds a confirmation, a reschedule, a billing question, a daughter calling about her mother, and one message about swelling. In a plain list they all look identical, and the only way to find the urgent one is to play every message in order while the phone rings again.
Triage, not just answering the phone
Most of this category sells a way to stop voicemail from existing. Oriva starts from the box you already have.
Answering is about capture. Triage is about order. Even a practice that answers the phone well ends the night with messages waiting, and the question at 7:52am is not how many there are. It is which one to open first, and what to do once it is open.
| Answering the call | Triaging the message | |
|---|---|---|
| What it solves | Fewer calls go unheard | The right message gets worked first |
| What comes back | A recording, or a booked slot | A transcript, an intent, a one-line summary, the callback number, and any flags |
| An emergency at 9pm | Depends who is on the line | Flagged, lifted out of the queue, and shown on its own until someone acts |
| When the read is unclear | The message still has to be sorted by hand | Parked for review with no suggested action |
| What your team opens | Every message, in the order left | A queue already ranked by urgency |
How the queue is ordered
Four intents, an emergency flag, and an honest bucket for what does not fit. The whole rubric, in public.
| Order | What it is | What happens |
|---|---|---|
| Emergency | Swelling, bleeding, a knocked-out or broken tooth, severe pain. | Leaves the queue, gets its own card, stays until a person acts. |
| Cancel or reschedule | The time-sensitive ones. | A cancellation frees a slot you can still refill today. A reschedule carries the caller's own words onto your waitlist. |
| Everything else | Running late, billing, insurance, a prescription, a post-op question, a wrong number. | Routes to a person with a summary. Running late is never filed as a cancellation. |
| Confirmations | The patient is keeping the appointment. | Nothing is at stake if it waits an hour. One click clears it. |
| Needs review | Below the confidence threshold. | Flagged for a human. Never silently guessed. |
What your front desk actually sees
A message arrives at 9:14pm. Next morning it sits above the confirmations:
“Patient wants to move Thursday's cleaning to next week”
Ruth calling for her mother Eleanor · callback ends 4417 · asked for “next week, morning”
Missing digits stay missing rather than invented. When the caller is not the patient, the card says so, so your team confirms authorization first. The original recording sits one tap away, under a standing note that intents are AI-suggested and can be wrong. Then four buttons.
What Oriva will not decide for you
The defaults are conservative on purpose, and the conservative ones are the ones that ship.
Manual is the default
Automation is a toggle you turn on, not one you turn off. Out of the box, every state change is a click by a person.
Emergencies stay with a human
Even with automation on, a message flagged as an emergency is excluded from it by rule rather than by setting.
It abstains instead of guessing
Low confidence, more than one request, or a poor recording, and Oriva offers nothing. Declining to guess quietly is the point.
Only the unambiguous is automated
With automation on, the agent acts on single-intent, non-emergency, high-confidence messages, one at a time. Everything else queues for you.
Every action is on the record
Each message carries which classifier read it and who acted on it, and each status change writes an audit entry.
Where it fits with what you already run
Triage starts at the recording. Oriva takes the audio your phone system already produces, so patients keep calling the number they always have and nothing about how they reach you changes on day one.
What is not built yet. Writing decisions back into Dentrix, Open Dental or Eaglesoft is in active development. For now, a decision made on the board is one your team then enters in your practice management system.
Questions we get
What is dental voicemail triage?
Voicemail triage is the step between a message being left and a person acting on it. Each message is transcribed, read for what the caller is asking for, summarized in a line, and ranked by how soon someone should respond. Urgent messages come out of the queue and onto their own card, routine ones queue behind them, and anything unclear is parked with no suggested action. It is sorting rather than diagnosis: the read exists to help your team decide, not to decide for them.
What happens to the voicemails patients leave overnight?
Each message is transcribed and classified as it lands, so by the time your team opens the board the whole night is already sorted. A message that reads as an emergency is lifted out of the queue onto its own card and stays there until a person acts on it. Cancellations and reschedules come next, because those are the gaps you can still refill today. Confirmations, which cost nothing by waiting, sit further down.
How does it tell an urgent message from a routine one?
Two checks run on every message. A model reads the transcript, and a fixed list of clinical terms is checked separately, so swelling, bleeding, a knocked-out or broken tooth, or severe pain still raises the flag even when the model is unavailable. Urgency words on their own are not enough, which is why an ASAP about a bill reads differently from an ASAP with pain. When the read is uncertain, or one message carries more than one request, Oriva offers no suggestion at all and parks it for a person.
Who decides what happens to an urgent message?
Your team does. Nothing changes on its own: every state change on the board is a click by a person, and messages flagged as emergencies are excluded from automation by rule rather than by setting. When an urgent message comes in, someone on your team chooses how it is handled, including whether to hand the callback to Veronica. That handoff is always a choice a person makes.
How does this work with the phone system we already have?
Triage starts at the recording, so patients keep calling the number they have always called. The ingest is designed to take the audio your phone system already produces, transcribe it, and post it to the board. Writing decisions back into Dentrix, Open Dental, or Eaglesoft is in active development, so for now a decision made on the board is one your team then enters in your practice management system.
Is this HIPAA compliant, and what happens to the recording?
Oriva is built to be HIPAA compliant. Data is encrypted in transit and at rest, access follows least-privilege principles, and we sign a Business Associate Agreement with practices using Oriva for protected health information. The recording is kept alongside the transcript so a read can always be checked before anyone acts on it, and every status change writes an audit entry. Formal third-party attestations such as SOC 2 are on the roadmap rather than in place, and we would rather say so here than on a sales call.
Type a message and watch it get sorted
Write a message the way a patient would leave one, and see exactly where it lands. Invented messages only, please: the demo runs on synthetic data and is not a place for patient information.