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, the front desk confirms the waitlist match, the waitlisted patient gets an SMS with a booking link, 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.

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.

n8n self-hosted on an OVH Canada VPS (or Power Automate on M365) is the automation glue. It coordinates SMS notifications through Quo when a slot opens, handles therapist-side availability changes that cascade into displaced clients, and manages conditional rebooking logic. The infrastructure cost is roughly $12-15 CAD/month for the VPS, not a SaaS subscription.

Quo (formerly OpenPhone) is the business phone and SMS provider. n8n triggers outbound texts through Quo to notify waitlisted patients when a slot opens. The patient receives a booking link pointing to the clinic’s Jane online booking page.

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 Rebookly and n8n subscriptions. It is worth evaluating at that scale.

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. The challenge is notification: Jane has no public API, so there is no way to programmatically detect cancellations and fire automated texts without relying on undocumented methods that may break without notice.

The practical approach is semi-automated. The front desk sees the cancellation in Jane, confirms the waitlist match (checking therapist-patient pairing, appointment type, and timing), and then triggers an n8n workflow. The trigger can be a simple form submission, a Slack message to a dedicated channel, or a button in a lightweight internal tool. The n8n workflow sends an SMS via Quo to the waitlisted patient with a booking link to the clinic’s Jane online booking page. The patient clicks through and books directly in Jane. This eliminates the phone call and automates the outreach while keeping a human in the loop for the matching decision. Full automation without a public API is fragile and not recommended.

Rebookly is purpose-built for Jane clinics. 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 submitted change, cross-references it against the clinic’s known schedule, and sends rebooking prompts to each affected client with a link to the clinic’s Jane online booking page. 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 requires a workflow engine with branching logic and a Canadian-hosted execution environment.

The complete data flow: patient or clinician change event triggers a notification, n8n sends an outbound SMS via Quo or email to the patient, the patient responds via a booking link to Jane’s online booking page, and the appointment is confirmed in the schedule.

Compliance posture

Jane App has Canadian data residency and satisfies PIPEDA and BC PIPA. 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.

Quo (formerly OpenPhone) does not have confirmed Canadian data residency. Request a Data Processing Agreement before onboarding. SMS messages sent through Quo should not contain protected health information: include only the patient’s first name, the date/time of the available slot, and the booking link. No diagnosis, treatment type, or clinician name in the text body.

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

• Without a public Jane API, any tool claiming deep Jane integration is working through undocumented methods that may break without notice. Build workflows around Jane’s official features (waitlist, online booking, reminders) rather than depending on unofficial integrations. If a vendor can’t explain how their integration survives a Jane update, that’s your answer.
• 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. Configure Jane’s waitlist rules 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 Quo for SMS follow-up. The investment is a Quo subscription and a few hours of configuration on the n8n workflow. 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 separate Jane-adjacent subscriptions starts to create its own overhead.