Package and Series Booking in an Alternative Practice

Package and series booking breaks the assumption every scheduling system is built on, which is that a patient decision produces one appointment. A patient buys eight sessions in a single conversation, and what the practice actually owes them is eight slots at a particular spacing, with a provider they will keep seeing, over a period of weeks.

Almost nothing in a standard scheduling workflow knows that the eight belong together. The system knows about appointments. The package exists in a payment record, a paper card, or the patient’s memory.

So the practice books the first one and intends to book the rest. Sometimes it books three and leaves the tail. Sometimes it books all eight and then one moves, and the spacing that mattered quietly stops mattering because nobody re-derived it.

The money makes this worse rather than better. A package is usually paid up front, which means the practice is holding revenue against visits that have not happened, and every session that never gets rebooked is a liability sitting on the books and a patient who did not get what they paid for.

The failure is rarely dramatic. It looks like a patient who came four times in the spring, meant to come back, and never did, and a front desk that had no list telling it to call.

The package is a booking rule, not a product

The first move is to write down what the package actually promises the schedule, because until it is written down it exists only as convention.

A package has a count, a spacing, a validity window and usually a provider constraint. Eight sessions, roughly weekly, to be used within four months, with the same practitioner unless the patient asks otherwise. Those four facts are the entire booking rule, and every downstream decision follows from them.

These practices sit under a broad umbrella that covers complementary, alternative and integrative health approaches, and the label matters less operationally than the delivery pattern underneath it. Multi-session delivery is the norm rather than the exception. The research literature on acupuncture, for example, measures what happens after a course of treatment rather than after a single visit, which tells you what the operational unit really is.

Once the rule is explicit it can be enforced at booking time. The scheduler is not asked to remember that this patient has five left. The appointment type carries the package, the count is visible, and the offer the patient hears reflects both.

Writing the rule down also exposes the disagreements. Practices routinely discover at this point that two practitioners run the same package at different cadences, or that the validity window was never decided. Better to find that in a config conversation than in a refund conversation.

Book the series, not just the next one

The most common and most expensive failure in multi-visit work is booking one leg of it and never booking the other.

This is not specific to packages. At one vascular group, roughly nine in ten visits are a pair of linked appointments booked with specific spacing, and nothing in the scheduling template enforces the pairing. It exists as convention, the patient calls asking to see the doctor, and the second half of the workflow silently does not exist until a human notices it in review.

A package is the same failure stretched over months. Book one, mean to book the rest, and the rest depends on the patient calling back.

The fix is to make the full series the default outcome of the booking conversation rather than an optional extra. Offer the whole run against the spacing rule, take what the patient will commit to, and leave an explicit task for whatever they would not commit to rather than an intention.

Patients will not always take eight slots on the phone, and that is fine. The distinction that matters is between a series with four booked and four tracked, and a series with four booked and four forgotten. The first is a workflow. The second is how packages expire unused.

Reminders were built for one appointment at a time

Here is a failure that looks like a patient problem and is actually a configuration problem.

Native reminder behavior in an electronic health record commonly fires against the chronologically first appointment only. A patient with two appointments on the same day gets reminded about one and misses the other. Stretch that across a series and the effect is subtler but the same: the patient is reminded about the next visit and has no working picture of the run they committed to.

Series patients need a different message than one-off patients. Where they are in the course, when the next one is, how many remain, and when the window closes. That is a two line message and it prevents most of the drift.

Sending it from the practice rather than relying on native reminder behavior is the only reliable way to get it right, and it is also the point where practices usually turn the native reminders off for these appointment types to avoid sending patients two contradictory messages.

The content stays administrative. Dates, counts, location and what to bring. Nothing about how the course is going, which is a conversation for the practitioner in the room.

When one visit moves, work out what happens to the rest

A series is a dependency chain, and rescheduling one link is where practices lose the spacing they designed.

The patient cancels session three. Does session four move with it, or hold? If the spacing is the point, the tail shifts. If the window is the constraint, something has to compress. Most practices have never made that decision explicitly, so it gets made differently by whoever happens to answer the phone.

There is a second mechanical hazard. Changing the duration of a slot in a template forces you to free up the neighbouring slots to make room, which means a schedule dense with series appointments resists exactly the kind of adjustment a cascade requires. The reschedule that looks like one change is three.

So the rule needs to be decided once and then applied consistently. Move the tail, keep the tail, or offer both and let the patient choose. Any of those is defensible. Improvising is not, because it produces a schedule nobody can predict and patients who compare notes.

Automation handles the mechanical part well. It knows the remaining appointments, the spacing rule and the window, and it can offer a cascaded set of new times in one pass instead of six phone calls. What it should not do is decide that a patient who has cancelled three times in a row should be dropped from the series. That is a conversation the practice owns.

The half-finished package is the best outreach list you have

The most valuable list in a practice like this is not new patients. It is the people who already bought.

A patient with three sessions left and no future appointment has already decided they want the care, already paid for it, and is not on anyone’s calendar. That is the cheapest booking in the building, and it goes uncontacted in most practices because nothing produces the list.

The list is easy to derive once packages are tracked against appointments. Sessions purchased, sessions used, next appointment booked or not, and days since the last visit. Sort by how close the validity window is to closing and work down.

Outbound reactivation against that list belongs in the same category as any other recall campaign, and it responds to the same discipline. Call at a sensible hour, offer specific times rather than asking when suits, take the booking on the call, and stop contacting people who have said no.

The payoff is not only revenue recognition. A patient who finishes the course they paid for is a patient who got the thing they bought, and that is the version of this workflow worth building. Everything else is bookkeeping around it.

Key Takeaways

Write the package rule down as a count, a spacing, a validity window and a provider constraint before automating anything.
Make booking the full series the default outcome of the conversation, not an optional extra the patient has to request.
Track every unbooked session as an explicit task, since the difference between tracked and forgotten is the whole workflow.
Replace native reminders for series appointments, because they commonly fire against the first appointment only.
Tell series patients where they are in the course, how many remain and when the window closes, in two lines.
Decide once whether a cancellation moves the tail or holds it, and apply that rule consistently across schedulers.
Expect a duration change in a dense template to require freeing neighbouring slots, so a cascade is never a single edit.
Work the purchased-but-unbooked list by closing validity window, since those patients have already decided and already paid.

Packages are sold as one decision and delivered as eight appointments, and the gap between those two facts is where the money and the patient both go missing. Write the rule down, book the whole run, replace the reminders, decide the cascade in advance, and call the people who paid for sessions they never used.

Sources