Reservo books appointments and takes deposits. It is not a clinical record system, holds no clinical notes, and carries no health-data certification. For an operator considering this deployment for physiotherapy practices, chiropractic offices, counselling services, dental front desks, or podiatry clinics, that boundary is the right place to start. Understanding it before you onboard your first practice is what keeps the scope legible and your obligations clear.
Reservo is a multi-tenant booking and appointment-management SaaS, sold once as source code you deploy under your own brand. Allied-health practices on your platform schedule patient appointments against real practitioner availability, take deposits on consultations, and receive automated email reminders — while their patient contact records remain on infrastructure you control. This page covers what the platform handles well for this family, where it stops, and what you still own as the operator.
Why the boundary is the argument, not an apology
A full clinical EHR — the systems practitioners use for charting, treatment plans, SOAP notes, e-prescribing, and insurance-claims workflows — carries a regulatory surface that a front-office booking platform does not. Software that holds clinical records attracts obligations under HIPAA in the United States, similar frameworks in other jurisdictions, and audit requirements from professional licensing bodies. The scope of those obligations depends on what the system stores and how.
A front-office booking platform that holds appointment times, patient contact details, intake question answers, and deposit records sits in a different category. Not because health data law is irrelevant to scheduling software — whether and how it applies is the operator's determination to make, not a product claim — but because the system is not storing the information that brings the heaviest clinical obligations with it.
That distinction is the argument for this deployment: you are running the scheduling and payment layer for a practice's front desk, not its clinical back office. The allied-health practices that fit this boundary are the ones where the clinical record system is separate — either an existing EHR the practice already runs, or a practice type where clinical charting is outside the front-office scope entirely. Cash-pay physiotherapy, wellness-oriented chiropractic, counselling, dental recall scheduling, podiatry appointments: practices in these settings buy front-office scheduling for what it does, and use separate tools for what it does not.
The compliance obligation that stays on your side of the boundary is yours to carry. Reservo does not carry it for you. There is no HIPAA Business Associate Agreement in the product, no health-data certification, and no claim of compliance with any health data framework. If you are deploying for practices that require those representations from you or from your infrastructure stack, take qualified advice before deploying. That is the honest starting point — not a risk mitigation clause, but an accurate description of what the product is and where it ends.
The per-practitioner market: what the incumbents show
The practices this deployment targets are already buying scheduling software. The competitor set they encounter is not salon software — it is per-practitioner clinical systems.
| Tool | What it is | Approximate pricing (as of 2026-08-07, aggregator-sourced, MEDIUM confidence — re-verify at each vendor's pricing page) |
|---|---|---|
| SimplePractice | Full clinical practice management — charting, insurance-claims workflows, client portal, treatment notes, telehealth | ~$49–99/month base + ~$69–74/month per additional clinician |
| Jane App | Clinical scheduling integrated with charting, billing, and patient messaging for multi-disciplinary practices | From ~$39–54/month; per-location and per-clinician fees at higher tiers |
Both SimplePractice and Jane App are clinical practice management systems. Their scheduling is one layer of a full clinical record stack. Their per-practitioner pricing reflects the value of everything the system holds: charting, claims, clinical notes, the complete record.
Reservo is not what you deploy instead of those systems for a practice that needs them. It is what you deploy for the front-office job — scheduling, deposits, email reminders, patient contact records — for practices that keep their clinical record system separate, or for the segment of allied health where clinical charting is outside the platform's scope by design.
At the owner level, what these incumbents show is that the per-practitioner subscription model for scheduling software is proven and the market pays for it. SimplePractice and Jane App are not alternatives the operator is weighing. They are evidence that health practices pay recurring per-practitioner fees for scheduling platforms. You are entering that market at the front-office layer: a narrower job, a narrower regulatory surface, and a one-time purchase rather than a per-practitioner vendor subscription.
What an established incumbent has that you will not on day one: years of brand trust with health practitioners in a regulated field, compliance certifications and BAA infrastructure, a support organisation built for healthcare, and deep integrations with insurance-billing systems. A practice with a long SimplePractice or Jane App history and a clinical workflow built around it is not a straightforward conversion target on those grounds alone.
What maps well for this family
Appointment scheduling with per-practitioner availability rules. Each practitioner on a practice's staff gets their own weekly schedule stored in the practice's configured timezone, with availability blocks for holidays, time off, and exceptions. Patients book against real availability. This is the core job, and it is what the platform is built around.
Deposit collection. Some clinical practices take upfront deposits for specialist initial assessments, first-time consultations, or appointment types with high cancellation exposure. Each service can carry a configurable fixed or percentage deposit, collected via Stripe Connect Express and settled directly into the practice's own Stripe balance. Refund and forfeiture rules are configurable per practice per your policy setup.
Group mode for supervised sessions. Group physiotherapy sessions, supervised exercise classes, and group therapy formats where multiple patients book the same practitioner time-slot up to a configured capacity ceiling are explicitly supported. The maximum concurrent patient count is enforced atomically at the reservation layer — a booking that would exceed capacity is rejected. This uses booking_mode = 'class' with the max_concurrent ceiling, which ships in v1 and is relevant to this family.
Patient contact records. Each practice on your platform maintains its own isolated patient record database. What the platform stores per patient: full name, email address, phone number, SMS opt-in flag, notes from the practice's staff, no-show count, and date of last visit. No clinical data is held in these records. The records stay on infrastructure you control.
Email reminders. Automated email reminders at 24 hours and 1 hour before each appointment run through a three-layer deduplication system — no missed sends, no duplicate sends. No-show reduction through reminders matters more in clinical practices than in many other deployment targets, and the pipeline is built and operational.
Per-practice isolation at the database engine. Each practice on your platform gets its own isolated environment enforced at the Postgres row-level-security layer: staff, services, patient records, booking policies, and a public booking page under a per-practice slug. One database, isolated practices.
Honest limits — specific to this family
Not a clinical EHR. Reservo holds no clinical notes, no SOAP notes, no treatment plans, no e-prescribing capability, and no insurance-claims workflows. A practice that needs any of those functions from its scheduling platform needs a clinical system, not Reservo. Reservo can sit alongside an EHR for front-office scheduling while the EHR handles the clinical record — these are different products for different jobs.
No health-data certification, no HIPAA BAA. Reservo does not carry HIPAA compliance status, is not a certified system under any health data framework, and ships no Business Associate Agreement. The operator's regulatory posture — whether and how health data law applies to their deployment, their hosting choices, their contractual obligations to practices, and their assessments under applicable frameworks — belongs entirely to the operator. This page will not provide compliance reassurance. Before deploying for practices in a regulated health context, seek advice from someone qualified to assess your specific situation. That is a genuine directive, not a legal disclaimer.
Intake form answers are collected but not server-side enforced. Each service on the platform can carry an intake form — a defined set of questions presented to the patient at booking time. Their answers are stored as JSON in the booking record. What does not happen: the server does not enforce required answers before accepting the booking. A patient who submits a booking with an incomplete intake form is not rejected — the booking goes through regardless. This is workable for most front-office contexts where intake answers are a convenience the practitioner follows up on. It is not appropriate for deployments where mandatory intake completion is a compliance function or a clinical safety gate. If that enforcement matters in your deployment, it has to happen at the practice level, outside the booking platform.
SMS reminders are roadmap. The automated reminder pipeline runs on email for v1. SMS reminders — often the channel allied-health practices rely on most for no-show reduction, since not all patients monitor email reliably — require carrier registration under Twilio's 10DLC framework and are on the v2 roadmap. Phone numbers are captured and stored at booking time, so the infrastructure is ready. Do not promise SMS reminders to a practice before v2 ships.
No staff invite UI in v1. Practitioner accounts can be managed at the org-admin level, but the in-product invite flow buttons are hardcoded disabled in the current build. Adding practitioners to a practice's account requires operator-level intervention. For practices expecting to self-manage their roster through the product UI — adding a new physiotherapist or removing a departing counsellor without calling you — set expectations clearly before onboarding.
Calendar sync is read-only iCal in v1. A practitioner who maintains their schedule in Google Calendar or Outlook can connect their public iCal feed to block availability on the platform. Busy time in their external calendar blocks slots — the connection is one-directional. Two-way sync and Google and Microsoft OAuth are roadmap. A practitioner expecting changes they make on the booking platform to appear in their personal calendar will not get that in v1.
No treatment-room scheduling. Reservo's booking engine is keyed to practitioners. Services are assigned to staff, availability is per-staff, and the slot reservation writes against a staff user ID. There is no resource entity in the schema — treatment rooms, therapy studios, and equipment cannot be scheduled independently of the practitioner who uses them. For a practice whose constraint is room availability shared across multiple practitioners, the platform cannot enforce that constraint.
English only in v1. Service names and descriptions are stored as plain text fields without localization. International allied-health deployments are outside v1's scope.
Own it
One purchase. Deploy for as many practices as your plan supports — the per-practitioner fee structure you offer is yours to design. Neither SimplePractice nor Jane App is available at any price as a multi-tenant codebase you operate under your own brand.
See the platform running → · Purchase Reservo for $249 →
Common questions — clinic and allied-health deployment
What data does Reservo actually store about a clinic's patients?
Reservo stores appointment records and patient contact details — not clinical data. What the database holds per patient: name, email address, phone number, SMS opt-in status, staff-added notes, a no-show count, and the date of their last visit. For each booking: the patient's contact details at booking time, the appointment start and end, status, deposit amount and status, any intake form answers the patient submitted as a JSON object, and cancellation information if applicable. What the database does not hold: clinical notes, diagnoses, SOAP notes, treatment plans, prescriptions, or insurance information. There are no clinical-data columns anywhere in the schema. The intake JSON contains only what the practice's own intake form asked — the field names and answers are whatever the practice configured, not a clinical record standard.
Is Reservo appropriate for a practice that has HIPAA or similar health data obligations?
Reservo carries no HIPAA compliance certification and ships no Business Associate Agreement. Whether and how health data law applies to a given deployment depends on the jurisdiction, the specific nature of the data processed, the hosting environment, the practices onboarded, and the contractual relationships in place — none of which the product determines. Reservo does not make compliance representations of any kind about any health data framework. The operator's regulatory posture is the operator's responsibility. Before deploying for practices in a health-regulated context, seek qualified advice that addresses your specific situation, jurisdiction, and deployment model. That is the honest starting point; any softer statement would be inaccurate.
What does SimplePractice do for a clinic that Reservo does not?
SimplePractice is a full clinical practice management system. It handles clinical notes and SOAP documentation, treatment plans, telehealth session hosting, insurance claim submission and payer tracking, a client portal where patients access session notes and homework, and progress reporting across a caseload. Reservo handles none of those things — it books appointments, takes deposits, sends email reminders, and maintains patient contact records. A practice that needs clinical charting and insurance billing needs SimplePractice or a comparable system, not Reservo. SimplePractice also carries years of established brand trust with mental health and therapy practitioners, compliance infrastructure including a Business Associate Agreement, and a support organisation built for regulated healthcare environments. An operator deploying Reservo for the first time will not have any of those on day one.
Can group therapy or group physiotherapy sessions be scheduled through Reservo?
Yes. Reservo supports group-mode services: a configurable maximum number of patients can book the same practitioner time-slot, enforced atomically at the reservation layer. A booking that would exceed the configured ceiling is rejected. This covers group physiotherapy sessions, supervised exercise classes, and group therapy formats where the practitioner holds a single slot for multiple patients booked independently against it. What Reservo does not support in v1: membership packs (prepaid session bundles), recurring class-series enrollment where a patient locks in every Thursday session automatically, and attendance tracking or check-in. For practices whose group offering is built around membership economics — twelve-session physiotherapy programs, subscription-based fitness access, enrollment-style class management — the platform handles the per-session slot mechanics but not the membership business model layered on top.
What should an operator understand about Reservo's intake form limitations before deploying for a clinic?
Each service on the platform can carry an intake form — a configurable set of questions shown to the patient at booking time. Their answers are stored per booking as a JSON object. The limit that matters most in a clinical context: Reservo does not enforce required answers on the server side. A patient who submits a booking without completing the intake form is not rejected. If intake data collection is a front-desk convenience — gathering information the practice staff will review before the appointment — this is workable. If mandatory intake completion is a clinical or compliance gate where an incomplete intake is grounds to reject a booking, that enforcement has to be implemented at the practice level, not inside the booking platform. Deploying Reservo for contexts where intake completion is a hard clinical requirement means building a workflow around it, not relying on the platform to enforce it.