Online Booking and Waitlist Auto-Fill

A same-day cancellation in a therapy or physio clinic has a short window for recovery. If no one checks the waitlist within an hour or two, the slot goes empty. At $95-$180 per session, two or three unfilled cancellations per week per clinician accumulates into meaningful lost revenue across a year. The problem compounds in practices where the same clinicians managing the waitlist are also treating patients back-to-back. This workflow automates the recovery loop: cancellation opens a slot, waitlisted patients are notified immediately, the first to confirm gets the booking, and the clinician does nothing until the schedule is already full again.

The stack

Jane App ($79-$149/month) is the foundation. Its built-in waitlist, recurring appointment management, and online booking cover the client-side cancellation problem for most clinics without additional tools. Automated reminders (SMS and email at 48 hours and 24 hours before the appointment) run natively inside Jane and cut no-show rates by roughly half.

ClinicSync (~$50/month) extends Jane with two-way SMS messaging and purpose-built rebooking flows. It is Jane-native, meaning it has legitimate data access through Jane’s partner API rather than scraping or workarounds, and is PIPEDA-confirmed with Canadian data residency. When a slot opens, ClinicSync contacts the next waitlisted patient by text without a front-desk call.

Rebookly handles a different problem: recurring clients who quietly lapse. When a client with a recurring booking hasn’t scheduled within 14 days, Rebookly sends a text follow-up with a booking link. It is Canadian-built and PIPEDA compliant.

HealOS is a multi-agent platform that bundles scribe, receptionist, and billing alongside scheduling automation in a single Jane-native product. The per-seat cost is higher, but for practices with five or more clinicians it avoids maintaining separate ClinicSync and Rebookly subscriptions. It is worth evaluating at that scale.

For the therapist-side scheduling problem (clinician availability changes that cascade into displaced clients), n8n self-hosted on an OVH Canada VPS handles the automation logic. This is a $12-15/month infrastructure cost, not a SaaS subscription.

How it gets wired

Jane’s built-in waitlist handles the core loop. When a patient cancels, Jane marks the slot as open and surfaces the next waitlisted patient. For the notification to fire automatically rather than waiting for a staff member to act, ClinicSync sits between Jane and the patient’s phone. ClinicSync polls Jane through the partner API, detects the opening, and sends an SMS to the waitlisted contact. The patient replies or clicks the booking link; ClinicSync writes the new appointment back into Jane. The connection depends on ClinicSync’s ongoing API relationship with Jane, which is why generic tools cannot replicate this: Jane has no public API, and Zapier or Make cannot read schedule data or write appointments without it.

Rebookly connects to Jane through the same partner API channel. It watches recurring appointment patterns and fires the 14-day lapse text when the expected next booking doesn’t appear. Setup requires authorising Rebookly’s Jane integration and configuring the message template and timing. The outbound text links to the clinic’s Jane online booking page; no separate booking surface is needed.

The therapist-side problem requires a different approach. When a clinician changes their availability, every client in the affected recurring slots needs a rebooking prompt before those slots open to the general waitlist. A defined submission channel (a shared Slack channel, a form, or a specific email address) collects the availability change. An n8n workflow on the OVH Canada VPS reads the new availability, identifies affected client bookings from Jane’s data, and sends rebooking prompts to each affected client with a booking link. Clients who don’t respond within 24 hours get a follow-up; slots that remain open after 48 hours are released to the waitlist. The clinician approves the final schedule before anything is confirmed. This logic is too conditional for ClinicSync or Rebookly to handle; it requires a workflow engine with branching logic and a Canadian-hosted execution environment.

The complete data flow: patient or clinician change event in Jane, read by ClinicSync or n8n via the Jane partner API, outbound SMS or email to patient, patient response via booking link back into Jane, appointment written to the schedule.

Compliance posture

Jane App has Canadian data residency and satisfies PIPEDA and BC PIPA. ClinicSync is PIPEDA-confirmed, built specifically for Jane clinics in Canada, and has no US data routing. Rebookly is Canadian-built and PIPEDA compliant.

n8n self-hosted on OVH Canada’s Beauharnois, Quebec infrastructure keeps all automation logic and any PHI-adjacent data on Canadian soil. OVH Canada holds ISO 27001 and SOC 2 Type II certifications and is not subject to the US CLOUD Act. This matters because the n8n workflows handle patient names, appointment times, and contact information in the process of building rebooking prompts.

Don’t route this through Zapier or Make. No BAA, US servers, no PIPEDA statement. Any flow that touches a patient name or appointment record legally can’t run through either. On Microsoft 365? Swap the n8n layer for Power Automate inside your Canadian tenant. It’s included in Business Standard and needs no separate VPS.

Common pitfalls

• ClinicSync’s rebooking texts work well for straightforward waitlist fills. The message tone matters: a text that reads as automated rather than personal gets ignored. Spend time writing the template before going live.
• Rebookly’s 14-day lapse trigger will fire for clients who deliberately paused treatment. Add a simple opt-out mechanism (reply STOP) and check the lapse list manually once a month for clients who shouldn’t be receiving recovery texts.
• Therapist-side availability changes are the most common source of schedule chaos in multi-clinician practices. The n8n workflow only functions if clinicians actually use the defined submission channel. Undocumented availability changes that bypass the channel leave the automation blind and clients in displaced slots without notice.
• Jane’s online booking does not automatically enforce therapist-patient pairing preferences in the waitlist fill sequence. ClinicSync’s waitlist rules need to be configured to match patient-therapist pairs before offering alternative clinicians. Skipping this configuration sends patients to the wrong clinician and creates more rescheduling work.
• HealOS adds capability but also vendor lock-in. Evaluate it carefully before committing; migrating off a multi-agent platform after building workflows inside it carries a real switching cost.

When this is worth the setup

A solo practitioner with a Jane subscription and at least five cancellations per month can recover most of the lost revenue with Jane’s built-in waitlist features and ClinicSync alone. The investment is the ClinicSync subscription and a few hours of configuration. Adding Rebookly makes sense once lapsed recurring clients are a visible problem, typically when a practice has been running long enough to accumulate clients who attended three to six sessions and stopped without formally discharging. The n8n layer for therapist-side scheduling is worth building when a practice has two or more clinicians and has experienced at least one cascade of displaced clients from a single availability change. HealOS becomes worth evaluating at five or more clinicians where managing three separate Jane-adjacent subscriptions starts to create its own overhead.