Optisoft Forum

Login

Automatic deposit /...
 
Notifications
Clear all

Automatic deposit / pre-payment trigger for repeat Fail-to-Attend and late-cancellation patients

2 Posts
2 Users
0 Reactions
134 Views
(@tinsonopticiansmaidstone)
Active Member Customer
Joined: 1 year ago
Posts: 4
Topic starter   [#55]

The problem

Fail-to-attends and last-minute cancellations cost us chair time and lost revenue, and there's currently no automated way to protect against the small number of patients who repeatedly do it. Staff have to remember who the repeat offenders are and manage deposits by hand — that doesn't scale and gets missed.

The request

Optisoft should automatically track repeat Fail to Attend / Cancelled events per patient and, once a practice-defined threshold is reached, flag that patient so their next booking requires a deposit before it's confirmed — with a notification sent to the patient explaining why.

Importantly, this needs no payment processing inside Optisoft. The deposit is always taken by staff (in shop or over the phone) — the system's job is only to count the strikes, flag the patient, gate the online booking, and alert staff. It builds directly on statuses Optisoft already records (Booked / Attended / Fail to Attend / Cancelled), so it's essentially a per-patient counter, a small rules engine, and a booking gate.

How it could work

  • Optisoft counts qualifying events (Fail to Attend, and optionally late cancellations) against the patient record.
  • When the count hits the practice's threshold, the patient is flagged.
  • In practice / over the phone: staff see the flag at the point of booking and take the deposit before confirming.
  • Online: depending on the practice's setting, either (a) the patient can't complete an online booking and is shown a message to phone the practice to book, or (b) the booking is accepted as provisional and fires a prominent staff alert to contact the patient and take prepayment before the slot is confirmed.
  • The deposit is redeemed against the visit if they attend, and forfeited if they Fail to Attend again.
  • A notification (using the existing email/SMS engine) tells the patient a deposit is required and why.

Options each practice can set

Because every practice runs differently, all of this needs to be configurable per practice:

  1. Which events count — Fail to Attend only, or Fail to Attend and late cancellations.
  2. What counts as a "late" cancellation — a day threshold, e.g. cancellations made within 3 days of the appointment count against the patient; anything cancelled earlier doesn't. (So a patient who books two weeks out and cancels four days before is fine; one who cancels the day before is not.)
  3. How many strikes before it triggers — e.g. 2, 3 or 4 events, and whether that's counted consecutively ("twice in a row") or as a rolling total within a set period (e.g. within 12 months).
  4. How online bookings are handled for flagged patients — choose one:
    • Block: the patient can't complete an online booking and is shown a message to contact the practice directly to book (deposit taken by staff at that point); or
    • Provisional + alert: the booking is accepted as provisional/unconfirmed and triggers a prominent staff notification/to-do to contact the patient and take prepayment before the slot is confirmed — with an option to auto-release the held slot if payment isn't taken within a set time.
  5. Deposit amount — a fixed figure, or set per appointment type (shown on the staff alert and the patient notification).
  6. When the flag clears — automatically once a deposit-secured appointment is attended, or manually by staff.
  7. Staff override — ability to waive the deposit for genuine cases (illness, bereavement, etc.).

Why it's worth building

No-show deposits are becoming standard across healthcare and dental. Because this design needs no payment integration — it works entirely off statuses Optisoft already tracks, with staff taking the deposit — it's low-risk to build and would save every practice the manual bookkeeping while recovering revenue that's currently just written off.



   
Quote
(@abrown)
Active Member Admin
Joined: 7 years ago
Posts: 17
 

Hi,

Thank you for your suggestion.

I agree that this would be a useful feature to have within Optisoft and can certainly see the benefit it would provide.

I’ll submit this as a change request to our programming team for their consideration and potential inclusion in a future update.

Kind regards,

Adam



   
ReplyQuote
Share:

Community Hub

Log Out