Best Scheduling Software for Physical Therapy: 3 Steps 2027

The category decision comes before the vendor

A multi-location scheduler is practice-management software where one account runs appointments for several sites, and each site keeps its own calendar, staff hours and appointment types. The first decision is which category you are buying: a booking-first tool that handles calendars, reminders and payments, or a PT-specific system where documentation, billing and scheduling share one database. Most confusion in this category comes from comparing a booking tool with a PT system as if they were the same product.

TL;DR: If you want published prices and unlimited sites on a booking-first tool, Cliniko and Jane are the clearest options in this list. If you want scheduling tied to PT billing and multi-clinic reporting, WebPT and Spry describe those features on their pages, but both are quote-based, so you will not see a price before a sales conversation. SimplePractice belongs on the shortlist only after it answers the multi-site question in writing.

Key Takeaways

• Multi-site support is the first filter, and Cliniko and Jane both state unlimited locations on the pages we opened.

• Three of the five products profiled publish dollar prices (Jane, SimplePractice and Cliniko); WebPT and Spry are quote-based.

• SimplePractice's multi-site controls are unconfirmed in the pages we could open, so get a written answer before you shortlist it.

• Cliniko's per-practitioner bands make monthly cost predictable, but SMS reminders and telehealth add costs or card requirements.

• A scheduler does not reroute cancellations or chase no-shows across sites by itself, so that work needs a workflow layer with human review.

• Confirm a business associate agreement in writing before any patient data goes into a scheduler.

How we evaluated these tools

We ordered these products by fit for one reader: an owner or operations lead at a small healthcare business who has two or three finalists and wants a direct answer. The weights below are our judgment about what matters to a multi-site buyer, not a vendor score or a ranking signal. Every price and limit in this article comes from a vendor page, help article or API reference we opened for this piece, and each figure sits next to its citation. We did not test any of these products or run a pilot, so every statement about how a product behaves comes from its published material.

We profiled five products. Raintree and Net Health are not profiled because we could not open an official site or pricing page for either in this session. Prompt Health's homepage describes multi-clinic and enterprise practice types and shows no prices, but its pricing address returned a not-found response, so we did not profile it in depth.

Feature matrix from public pages

The matrix records what each vendor's public pages state. A "not checked" cell means we did not confirm the claim, which is different from saying the product lacks the feature.

The gap that matters most for multi-site buyers is SimplePractice. Its calendar features page does not mention locations or location-level booking controls, and its help-center article on calendar location filters returned a blocked response to us, so we cannot say whether location filters exist or which plan includes them.

What each vendor publishes about price

Pricing checked October 19, 2026. Figures here come only from vendor pricing pages we opened in this session, and a vendor that prints no dollar figures is marked quote-based.

The Balance, Practice and Thrive plans on Jane are listed at $59, $79 and $99 a month according to Jane (2026), and the Balance plan covers one practitioner profile and 20 appointments a month, while Practice and Thrive each include one full-time practitioner. Jane's page also says it does not offer a free trial.

Plus plan on SimplePractice: $99 a month according to SimplePractice (2026). The Starter and Essential plans are $49 and $79 a month, each with a 50% discount for three months, and the page says the paid account must start within 7 days to claim it. Group Plus lists $74 per additional practitioner at standard rate.

Cliniko 2 to 5 practitioners: $95 a month according to Cliniko (2026). The other bands run from $45 for one practitioner to $395 for 26 to 200, SMS reminders cost 10 cents per message on prepaid credit, paying annually gives one extra month free each year, and the 30-day trial needs no payment details. Telehealth stays locked until a card is on file.

A third-party listing, CostBench, shows the same Cliniko bands and says it last verified them on September 13, 2026, according to CostBench (2026).

WebPT's pricing page prints no dollar figures. It names Starter, Enhanced and Ultimate plans, says pricing is based on the plan and any customization and can be set per provider per month or per visit, and sells add-on modules named Engage, Care, Monetize and Plus. Your real cost therefore depends on which modules you add. Spry is also quote-based, and its published terms appear in the profile below.

A worked budget for ten clinicians across three sites

This is an illustrative group, not a customer: ten practitioners across three sites sending 600 SMS reminders a month, which is our assumption. Cliniko 9 to 12 practitioners: $195 a month and SMS at 10 cents a message, both according to Cliniko (2026). Monthly billing for the band comes to $195 × 12 = $2,340 a year, while annual billing for 11 paid months, the annual option described above, comes to $195 × 11 = $2,145, a $195 saving. Reminders add 600 × $0.10 = $60 a month, or $720 a year. The annual-billing total is $2,145 + $720 = $2,865, or $955 per site, and the monthly-billing total is $2,340 + $720 = $3,060. An automation calling Cliniko's API would need business_id, practitioner_id and appointment_type_id on every available-times request, and Cliniko's reference limits that request's window to seven days.

Vendor profiles, ordered by fit rather than rank

Cliniko

Best fit: Groups that want published prices, unlimited locations and a public API, and that keep clinical documentation elsewhere. Each location gets its own appointment calendar, and patients are shared across sites rather than assigned to one.

Limitations: Invoices, payments and expenses are reported per location, so a group-wide roll-up needs an export or a separate step. The pages we opened do not name physical therapy specifically, and SMS and telehealth are extra costs.

Implementation: Set each practitioner's working days and hours for every site, because a practitioner cannot take bookings at a site until those hours exist. Then choose which services each site offers.

Primary evidence: Cliniko's help article on adding locations and its API reference.

Our read: Strongest on the calendar and the published price, and weaker if you want reporting that rolls up across sites without extra work. If your team also moves Cliniko data into accounting, see the Cliniko-to-Xero automation guide.

Jane

Best fit: Booking-led groups that want unlimited admins and locations on every plan, a custom-branded online booking site and published monthly prices.

Limitations: Jane's page says it has no free trial and offers a demo account through its community or support team instead. Licenses cannot be split or shared between people, and AI Scribe and group telehealth are priced per opted-in practitioner. The Thrive plan adds rooms and equipment, patient self check-in and automated waitlist management, so compare the tiers before you decide.

Implementation: The pricing page does not describe onboarding, so ask in writing how locations and practitioner profiles are set up.

Primary evidence: Jane's pricing page.

Our read: A solid first comparison for a multi-site group that can work without a trial. The pages we opened do not describe PT documentation. For an automation angle, see the Jane and SimplePractice comparison for automation.

SimplePractice

Best fit: Practices already on SimplePractice that want to add a site, once the vendor confirms multi-site calendars on the plan you would buy.

Limitations: The pricing page lists Starter, Essential and Plus, and the Starter and Essential plans are labeled solo. The calendar features page we opened does not mention locations, and the help-center article on calendar location filters did not open for us.

Implementation: Unconfirmed in the pages we could read. Ask about location setup, calendar filters and online booking by site in writing.

Primary evidence: SimplePractice's pricing page.

Our read: Price is published, and multi-site is the open question. Put that question first on any call.

WebPT

Best fit: PT-only groups that want scheduling tied to billing and multi-clinic reporting, and that are prepared to negotiate a quote.

Limitations: The pricing page publishes no dollar figures, and the add-on modules mean the quote depends on what you add. "Multi-Location Practices" appears as a practice type, but the details sit on a page we did not open.

Implementation: Not described on the pages we opened. Ask for timeline, data migration and training scope before signing.

Primary evidence: WebPT's pricing page.

Our read: The Ultimate tier is the one to price for a group. Its Plus module includes multi-clinic financial and provider reporting, and its billing features include multiple TIN billing.

Spry

Best fit: Multi-location groups that prefer pricing tied to visit volume and want scheduling, billing and multi-site rollout from one vendor.

Limitations: Pricing is based on visits per full-time provider, so you need a visit forecast before a quote means anything. No free trial is mentioned, and the page offers a demo option instead.

Implementation: The site says free data migration is included and that every location gets the same access to the response team. Ask for the migration plan in writing.

Primary evidence: Billing service on Spry: 4 to 6% of collections according to Spry (2026). Essentials includes online scheduling, a patient portal, a patient waitlist and appointment reminders.

Our read: Good on paper for a group with stable visit volume. Get the visit count and billing terms before comparing it with fixed-price tools.

Three steps to shortlist

1. Write down your site count, practitioner count and monthly reminder volume. Those three numbers decide which Cliniko band applies and what a visit-based quote from Spry or WebPT will cost, so collect them before any call.

2. Send every finalist the same written questions: can one login show every site's calendar, are reports per site or group-wide, which BAA terms apply, what export or API access exists for schedules and no-show data, and which modules are in the quote versus sold as add-ons.

3. Move two sites first and keep your current system live through the cutover, then compare reminder and no-show counts by site before you move the rest. This is a rollout recommendation for your own group, not a result we measured.

Mistakes that cost multi-site groups time

• Treating a shared location field as group-wide reporting. Cliniko's reports are per location, so a roll-up needs a separate step.

• Comparing list prices without visit volume. Spry prices on visits and WebPT on quotes, so a published-price comparison will mislead.

• Forgetting site hours. Cliniko will not take bookings at a site until the practitioner's hours are set for that site.

• Ignoring message costs. Cliniko bills SMS per message from prepaid credit, and the cost grows with every site.

• Assuming a trial exists. Jane says it has none, and Spry offers a demo option instead.

• Skipping the BAA. Get it in writing before go-live, not after.

Where a workflow layer fits

A scheduler stores appointments. It does not, on its own, notice an opened slot at one site, offer it to a waitlist patient, or add up no-shows across sites. Those jobs belong to a workflow layer. The two designs below are proposed, configurable workflows. Neither is running for any customer, and we have not measured any result from them.

US Tech Automations would configure a cancellation backfill as follows. The trigger is a scheduled check on a short fixed interval during clinic hours that calls Cliniko's available-times endpoint for each practitioner at each site, keyed by business_id, practitioner_id and appointment_type_id, over a window no longer than the seven days the API reference allows. The workflow compares newly open slots with its previous snapshot, matches them against a waitlist export you already maintain by site and appointment type, and writes a draft text for the front desk at that site. The output is a draft, not a sent message: a named staff member approves each text, and only patients with an SMS opt-in are eligible. Prerequisites are read access to the Cliniko API, a waitlist export with site and appointment-type fields, and a consent field your team already keeps. Booking stays manual in the first version, because the pages we checked do not establish a write endpoint that automated booking would depend on. Waitlist data quality limits the output, so clean it before the first run; the CRM data entry guide covers the intake side.

US Tech Automations would configure a multi-site no-show roll-up differently. The trigger is a daily run before clinic opens, pulling each site's no-show and cancellation counts from exports, because Cliniko's reports are kept per location. The action sums the counts by site and by practitioner, compares them with the prior week, and flags any site where the rate moves beyond a threshold your operations lead sets. The output is one digest with one row per site, not patient-level detail. The review point is the operations lead or finance reviewer, who reconciles the digest with the per-site reports before anyone changes staffing or reminder rules. Prerequisites are a repeatable export or API pull from each site, a naming map from site names to business records, and a written decision on who may see patient-level detail. A proposed design can run the same check every morning without a person forgetting it and keep a run log of what changed. It cannot set the threshold, fix a broken export or decide what a flagged site should do, and those stay with people. For the dashboard side of the digest, the reporting software guide for physical therapy clinics is the companion read.

Building the same workflow in Zapier, Make, or n8n

Zapier's help center says every run gets a status in Zap history, including Errored, Safely halted, On hold, Handled error and Scheduled, and that after you fix the cause you can replay failed tasks so you do not lose data, according to Zapier. Those tools can support run histories, retries, error branches and audit evidence when configured. The buyer still designs and owns the rest: alerts when a run fails, idempotency so a rerun does not text the same patient twice, escalation to a named person, access controls over patient data in run logs, and maintenance when an API changes. The same questions apply to Make and n8n, and an in-house build carries the same burden with more code to own.

A proposed US Tech Automations design would configure those same pieces in one place: a per-slot idempotency key, a named approver before any text is sent, role-based access to run logs, and a standing review of failed runs. The prerequisites to confirm are API credentials for each system, a business associate agreement covering any vendor that touches patient data in the flow, and a named owner for maintenance. Those are design points to check, not outcomes we have measured.

Who should pick which product

Use this table as a starting point, not a verdict.

Who this is for: Multi-site physical therapy or allied-health groups where an owner or operations lead owns the scheduling decision and can put the written questions above to each vendor.

Red flags: you need PT documentation and billing in one system and nobody owns that evaluation; you cannot sign a BAA with any vendor that will hold patient data; or you need a published price for WebPT or Spry before a sales conversation.

When not to use US Tech Automations: A simpler tool wins in three cases, and US Tech Automations is the wrong first purchase for each. If you run one site, the native booking and reminders in Cliniko or Jane may already cover the job, and a workflow layer adds maintenance for little gain. If your main need is documentation and billing inside one clinical system, choose a PT-specific vendor first and add workflow later, because the workflow depends on the system you pick. If your team cannot grant API or export access, or cannot sign a BAA covering the flow, there is nothing safe for a workflow to run on, so the scheduler's own features are the better choice.

Frequently asked questions

Can one scheduler run several PT locations from one login?

Yes on Cliniko and Jane, whose public pages describe unlimited locations, and SimplePractice needs written confirmation before you rely on it.

Do Cliniko prices rise as I add locations?

No. Cliniko's bands count practitioners, and its help article says you can have an unlimited number of locations on any plan.

Do I need a business associate agreement before loading patient data?

Treat it as required and get it in writing before go-live, because HHS guidance, as summarized according to Rivkin Radler (2016), says cloud providers handling ePHI must enter into business associate agreements. We did not confirm BAA terms for any vendor in this session, so ask each one directly.

Should I pick a PT-specific system or a booking-first tool?

Pick a PT-specific system if documentation and billing must sit in one place, and pick a booking-first tool if documentation lives elsewhere and you want a simpler calendar that adds sites easily.

Are free trials available?

Cliniko's trial needs no payment details to start, SimplePractice's pricing page describes a free trial that can extend, Jane says it has none, and Spry offers a demo option instead.

Could Zapier or Make replace a workflow vendor?

Yes, with configuration. The difference is ownership: you build and maintain the alerts, approvals, idempotency checks and access controls, and you keep the run logs audit-ready.

Conclusion

Start with the written questions, and let the answers set the shortlist. Cliniko and Jane give the clearest published prices and unlimited-location statements, WebPT and Spry need a quote before a fair comparison, and SimplePractice needs a written answer about multi-site calendars. If you want the cancellation and no-show work run by a configured workflow with human review points, see how US Tech Automations configures this before you finalize the platform.