Practice Operations
Rescheduling a Manual Therapy Series Without Losing the Cadence
One visit moves and the rest of the manual therapy series drifts. What the message has to say, what the reply has to trigger, and who owns the exception.
A manual therapy series is held together by intervals, and the intervals are held together by messages. A patient books eight osteopathic manipulative treatment visits at a set cadence, misses one in week three, and what happens next depends entirely on what the practice says to them and how fast.
Most practices have already bought something to send the reminder. That is the part that demos well.
The part that does not demo is the reply. A patient texts back that Tuesday no longer works, and the message tool has nothing to do with the schedule, so the text lands in a queue and a person opens the calendar and starts moving appointments by hand. The practice now owns the original work plus a tool to check.
Meanwhile the series quietly comes apart. The remaining visits sit where they were, spaced against a date the patient no longer intends to keep. Nobody rebooks them, because from the schedule’s point of view nothing is wrong. Every appointment still exists.
The patient reads it the same way the schedule does, which is to say not at all. They meant to call. Six weeks later they are gone, and the only record of it is a run of appointments that were kept until they were not.
A reminder is not a reschedule
The distinction sounds pedantic right up until you count the callbacks. A reminder tells the patient something. A reschedule changes the schedule. Most front-office messaging stops at the first and hands the second back to whoever is on the phones.
That handback is the cost, and it is invisible in the reminder tool’s own reporting. Delivery rate looks excellent on a message that created work instead of removing it.
No-show behavior is not uniformly getting worse, which makes this easy to put off. In a 2025 MGMA Stat poll, 73% of practices said their no-show rates had stayed the same or decreased year over year, while 27% said they had increased. A stable average across a lot of practices still leaves the group that is losing ground, and for a specialty running eight-visit courses, the loss compounds. One dropped visit does not cost one visit. It costs the tail of the series behind it.
What a message has to be able to do, then, is finish the transaction. Offer real times from the schedule, take the patient’s answer, write it back, and move the rest of the run to match.
The message has to know which visit this is
Native reminder behavior in an electronic health record commonly fires against the chronologically first upcoming appointment. For a practice booking one visit at a time, that is fine. For one running a series, it is the wrong unit entirely.
A patient on a cadence needs to be told which visit is next, how many remain before the review point, and that the rest of the run is still where they left it. Two lines. That is most of the drift prevented, because drift starts with a patient who has lost the thread.
Inside athenaOne the raw material is there. The patient record carries the demographics and the preferred contact method, and a secure message can be sent to the patient and read back from their inbox, which means the practice controls the content rather than inheriting whatever the default reminder says. Practices that do this usually turn the native reminder off for the recurring appointment type, so the patient is not getting two messages that disagree with each other.
Everything in the message stays administrative. Date, time, location, which visit in the run, what to bring. How the course is going belongs in the room with the physician, and no message should go anywhere near it.
The reply is where the work is
Inbound is the half nobody buys and every practice needs. A patient answers with a sentence, not a button press, and that sentence has to become a schedule change.
Read the reply, match it to the patient and the appointment, offer times that exist against the provider’s template rather than times that sound plausible, take the confirmation, and cascade the remaining visits to preserve the interval. Then write the change back so the chart and the calendar agree, and close the loop with a confirmation the patient can keep.
There is a mechanical trap underneath the cascade. Changing the duration of a slot in a template requires freeing the neighboring slots to make room, so a calendar dense with recurring visits resists adjustment. What looks like moving one appointment becomes three edits, and the person doing it under pressure often just books the patient somewhere convenient, which breaks the interval nobody wrote down. Automation is better at this than a person, for the unglamorous reason that it does not get tired at the third edit.
Practices are also getting firmer about attendance in general. A January 2025 MGMA Stat poll found 42% of medical group leaders reported their practices charge a no-show fee, against 58% that do not. A fee without a working reschedule path is just a penalty, and a penalty is a poor substitute for a message the patient can answer.
Decide the cadence rule once, then say it out loud
When week three moves, does week four move with it or stay put? Both answers are defensible. Deciding it differently depending on who took the call is not.
Write the rule down, then put it in the message. If the practice preserves the interval, the confirmation says so: your next visits have moved to these dates. If it does not, the confirmation says that instead. Patients accept either rule and resent neither. What they resent is finding out later that the schedule they thought they had is not the schedule that exists.
Open-access and same-day scheduling approaches make the same argument from the capacity side, which is that access improves when the rules governing the calendar are explicit rather than negotiated per call. A recurring series is that argument in miniature, run eight times per patient.
The rule also gives the automation somewhere to stop. It executes the cadence rule and offers the times. It does not decide that a patient who has missed three in a row should come off the arrangement. That is a conversation between the practice, the patient and often the physician, and the workflow should raise it rather than settle it.
Where the person takes over
The handoff points are specific enough to put on a card.
A patient who asks why the cadence is what it is goes to clinical staff. A patient who wants a different physician goes to a scheduler with the redirect language already written, because a caller asking for someone by name needs a real alternative rather than a brush-off. A patient in distress, or one whose message reads as anything other than a scheduling request, goes to a person immediately, and the automation should be biased toward handing off early rather than trying one more time.
What is left for the AI is the volume: the outbound message, the times, the reply, the cascade, the write-back, the confirmation. That is the shape practices keep describing when they say they want an extra team rather than another dashboard. Not a tool that owns the patient relationship, but one that does the mechanical part of it so the front desk has time for the calls that are actually conversations.
The test takes one query. Count the series reschedules that finished without a person opening the calendar. If the answer is none, the tool is sending reminders, not running the series.
Key Takeaways
- Judge a messaging tool by how many reschedules it completes without a person opening the calendar, not by delivery rate.
- Turn native reminders off for recurring appointment types, since they commonly fire against the first upcoming appointment only.
- Put the series position in the message: which visit this is, how many remain, and that the rest of the run is unchanged.
- Build the inbound path first, because the reply is where the front-desk work actually is.
- Offer times that exist against the provider’s template rather than times that sound plausible, then write the change back to the chart.
- Expect a slot duration change in a dense recurring calendar to require freeing neighboring slots, so a cascade is never one edit.
- Decide once whether a cancellation moves the rest of the run, then state the rule in the confirmation message.
- Hand off early on anything that is not a scheduling request, and keep cadence questions with clinical staff.
A manual therapy series survives on intervals, and intervals survive on messages that can be answered. Send the message that knows which visit this is, build the path that turns the reply into a schedule change, write the cadence rule down before you need it, and hand off the moment the conversation stops being about a date. The patients who drift off are almost always the ones who meant to call back.
Related reading
- how the standing appointment holds a manual therapy run together
- two-way texting that writes back to the chart
- the cancellation cascade in a recurring appointment series
Sources
Ready to See It in Action?
See how PGA sends the message, reads the reply and moves the rest of the series without a callback
Schedule a Demo →Written by Kevin Henrikson