Per-patient cadence. And proof the message actually went.

Not everyone comes back in a year

Recall built on an annual cycle works for the routine half of your schedule and
quietly fails the half that matters most.

The glaucoma patient on a four-month interval. The diabetic who needs to be seen
before the referral goes stale. The child midway through a vision therapy package
with re-exams that follow the program, not the calendar. The post-op who needs
three touches in six weeks and then nothing for a year.

Force those into an annual template and you get two failures. The ones who come
back too late. And the ones who get an automated card reminding them their
"annual eye exam" is due, six weeks after you saw them, which is the kind of small
thing that tells a patient exactly how closely you are watching.

Cadence that follows the condition

Set the interval on the patient, not on the practice. Four months, six weeks,
two years, a schedule that tracks a therapy program through its phases.

Vision therapy packages and re-exams stay attached to the program, so the
twelve-week block does not depend on someone remembering that week eight is a
progress check.

The part that is actually different: you can see it arrived

Here is the failure nobody markets against, because nobody wants to bring it up.

A reminder system that silently does not send looks identical to a reminder system
that works. The schedule is thinner than it should be. Nobody knows why. The
assumption is that patients are not responding, and the actual answer is that a
number went bad in March and eleven hundred messages went nowhere.

IrisMed gives you delivery receipts. Sent, delivered, failed, and why.

• Email, SMS, and voice, from one stack, with the same reporting.
• Delivery state per message — not a queue count, the actual outcome.
• Failures surface as work, so a dead number becomes a task instead of a
  statistic.
• Campaign-level view for recall pushes, so you know what landed before you
  judge the response rate.

Why the receipt is the whole argument

Every recall system claims it sends. The question is what happens the week it
stops, and how long it takes you to find out.

If the answer is "we notice when the schedule looks light," you are running your
recall on inference. You should be running it on evidence.

Schedule a Demo

Ask to see a failed message. That is the screen worth looking at.