Recording soon
Product preview · not currently available for purchase; shown as planned operating scope.
The Alotime system
AlotimePatient Reactivation
03 / 06
The patients who stopped coming, contacted once.
A measured sequence to appropriate inactive patients — three messages over a week, each one sent only if the last got no reply, and stopped the moment somebody answers.
Watch it run
One of six, one record
Patient Reactivation does not keep
an inbox of its own.
Everything it handles lands in the same patient record as the other five, so nothing is worked twice and nobody has to be told the same thing again.
Patient Reactivation, running
It selects. It contacts. It stops.
A measured sequence to appropriate inactive patients — three messages over a week, each one sent only if the last got no reply, and stopped the moment somebody answers.
Day 0Email
“It has been a while since your last check-up — would you like to book one?”
Day 3Message · only if there was no reply
“A short reminder — there are openings this week if you would like one.”
Day 7Email · final message
“Last note from us for now — reply any time and we will find a slot.”
ReplyThe sequence stops here
A reply moves the conversation to your team with its full history attached.
What the clinic gets
- It selectsRule-based, on criteria the practice sets. Not everyone on the list.
- It contactsDay 0, day 3, day 7 — each step conditional on silence before it.
- It stopsA reply ends the sequence and hands the conversation to your team.
The gap it closes
Not a staffing failure. A coverage one.
A list that only growsEvery practice has patients who simply drifted. Nobody has the hours to call them.
Outreach that stopsA single email is easy to miss. Five is harassment. The line is in between.
Where it usually diesA reply that lands in a shared inbox at 9 PM is a reply nobody sees.
How it works
Three steps, and then it stops.
01It selects
Rule-based, on criteria the practice sets. Not everyone on the list.
02It contacts
Day 0, day 3, day 7 — each step conditional on silence before it.
03It stops
A reply ends the sequence and hands the conversation to your team.
The boundary
What it will never do.
Every product in the system has a written line it does not cross. This one is Patient Reactivation’s.
Never, in any configuration
- Message a patient who has opted out
- Claim a clinical reason to come in
- Continue a sequence after somebody replies
- Contact anyone the practice has excluded
Every reply is visible in the panel with the sequence that produced it.
The path a request takes
Four stages, and then a person.
Nothing here is a promise about outcomes. It is the path Patient Reactivation actually takes, and the point where it stops.
01
Arrives
A list that only grows
Every practice has patients who simply drifted. Nobody has the hours to call them.
02
It selects
It selects
Rule-based, on criteria the practice sets. Not everyone on the list.
03
It contacts
It contacts
Day 0, day 3, day 7 — each step conditional on silence before it.
04
Next step
It stops
A reply ends the sequence and hands the conversation to your team.
Watch it run
Patient Reactivation, end to end.
One unedited recording of this product handling a single request, from the moment it arrives to the moment your team opens it.
Where it shows up
One panel, one record.
Patient Reactivation does not keep its own inbox. Everything it handles lands in the same patient record as the other five, so nothing is worked twice.
See the panel
Representative panel view
Design direction · no patient data
Patient Reactivation
Every reply is visible in the panel with the sequence that produced it.
Stage 01It selectsLive
Stage 02It contactsRecorded
Stage 03It stopsExplicit
One clear operational trailVisible path
- 01It selectsRule-based, on criteria the practice sets. Not everyone on the list.
- 02It contactsDay 0, day 3, day 7 — each step conditional on silence before it.
- 03It stopsA reply ends the sequence and hands the conversation to your team.
What it never doesClinic decides
- Message a patient who has opted out
- Claim a clinical reason to come in
- Continue a sequence after somebody replies
Founder-led · built for dental clinics
Uygar Kaan Yılmaz
Founder, Alotime
@getautosmile
I build Alotime for the hours a dental practice cannot cover. If something in the system gets a patient conversation wrong, that is mine to fix — and you will always know who to call.
Get Alotime. Get more smiles.
Request a free clinic analysis
- 15-minute discovery
- Clinic-specific estimate
- No commitment required