Physio Patient Reactivation: What to Automate First

I'd start with the patients who stopped booking during an existing plan. Then I'd organise reviews already requested by a physio, followed by the older patient list. The work is finding a valid reason to contact each person and getting the message approved. My patient reactivation and follow-up strategy follows the same principle: establish the reason before preparing the approach.

Which Three Patient Reactivation Workflows Should a Physio Clinic Automate First?

1. Mid-Plan Drop-Offs

Start here because the practitioner can check an existing plan before deciding whether contact makes sense. An empty appointment calendar alone tells you very little.

1. Trigger: A patient recorded as being mid-plan has no upcoming appointment and has passed a clinic-defined interval since the last visit.
2. Prepare: The last visit date, the plan stage copied from the practitioner's designated field, and a short check-in draft. Add no clinical interpretation.
3. Approve: The treating physio or practice manager checks the reason, consent and wording before each message sends. Unclear clinical status goes to the physio.
4. Record: The approval, contact date, message and outcome in the patient record or linked task.
5. Measure: The share of eligible drop-offs contacted within a week and rebooked within 30 days. These are proposed measurement windows, not benchmarks.

2. Discharged Patients Due a Review

The physio sets the review date at discharge. Automation can then bring that instruction back to staff when the date arrives.

1. Trigger: A clinician-set recall becomes due, with no suitable appointment already booked.
2. Prepare: A draft from an approved template, or a call task where the record says a call is appropriate.
3. Approve: A physio or practice manager checks each recipient and message. Template approval alone does not authorise sending.
4. Record: The contact attempt and outcome, including whether the patient booked, declined or needs a clinician's reply.
5. Measure: Recalls actioned by their due date and the proportion rebooking within the clinic's chosen reporting window.

3. The Older Lapsed List

I'd tackle this third. An old patient record needs a current, defensible reason for contact and usable consent evidence before anyone drafts an approach.

1. Trigger: A monthly review of a clinic-selected group, such as patients last seen 6-24 months ago. That range is an example, not a clinical recommendation.
2. Prepare: Remove records marked deceased, moved away, opted out or lacking the required consent. Rank the remainder by a recorded reason to contact and prepare drafts.
3. Approve: The practice manager approves every message; clinical uncertainty goes to the treating physio.
4. Record: Replies, bookings, opt-outs and failed deliveries, with corrections written back to the practice software.
5. Measure: Replies, rebookings and opt-outs, keeping failed deliveries visible.

What Can Cliniko, Zanda and Nookal Already Do for Patient Recalls?

Check the existing software before paying for another system. These are the recall capabilities each vendor documents as at October 2026.

For this design, I'd use Zanda's task action to preserve approval. For Nookal, I'd confirm the approval process before enabling sends. Sending capability does not establish that a patient should receive a particular message.

How Do You Find Lapsed Patients Without a Spreadsheet Hunt?

Cliniko's Patients without upcoming appointments report filters by last appointment date, practitioner and business. Staff can also exclude patients who already have a recall.

That report does not export directly. Cliniko documents a separate administrator-only patient export, where a blank Next Appointment column identifies patients with nothing booked. A repeatable review can start with the report rather than a fresh spreadsheet search.

For a connected build, the Cliniko API documentation covers appointments and recalls; an API key inherits its user's permissions. I'd use a dedicated user with the minimum necessary access. A connection still needs to be tested, and missing plan information needs a staff task, not an AI guess.

What Rules Apply to Physio Recall SMS and Emails in Australia?

Physiotherapy is a regulated health profession under Ahpra, and Ahpra's advertising guidelines apply to how regulated health services are advertised. I'd have the practice manager check every recall template against those guidelines before it goes into use.

Corrs Chambers Westgarth's Spam Act commentary says commercial electronic messages require express or inferred consent, sender identification and a functional unsubscribe facility. A rebooking message promoting services needs that assessment; calling it a recall does not settle the question. Consult ACMA for the official rules.

The OAIC's APP 7 guidance says using sensitive information for direct marketing requires consent, including for existing patients. APP 7 gives way where the Spam Act applies, so the rules need to be considered together.

My operating rule would be to retain consent evidence, check suppression records before drafting and again before sending, and keep condition details out of SMS. This is general information; check the clinic's process against Ahpra, OAIC and ACMA guidance.

Example: A Patient Stops Booking Mid-Plan

Hypothetical example, not a client story: A clinic's review queue finds a patient with no future appointment and a practitioner-entered plan stage showing treatment was unfinished. The system prepares those facts and a neutral draft.

The physio checks whether contact remains appropriate. The practice manager checks consent and approves: “Hi Alex, it's Harbour Physio. Would you like us to help arrange another appointment? Reply here or contact reception. Reply STOP to opt out.” The clinic would need to check the final template and unsubscribe process before use.

The system records approval and contact. A reply describing worsening symptoms goes to a clinician. A STOP reply suppresses further marketing contact.

What Should Never Be Automated in Patient Reactivation?

• Clinical advice, symptom triage or deciding who is clinically due.
• Messages exposing a patient's condition in an SMS.
• Testimonials, discounts or free offers in recall copy. I'd leave incentives out of the first build.
• Contact without the required consent or after an opt-out.
• Further messages while a clinical or sensitive reply awaits a person's decision.

Keep appointment reminders and missed bookings in their own queues. See appointment reminder automation and no-show follow-up and rebooking. The broader boundary is allied health administration, not diagnosis.

What Should a Clinic Measure, and Where Does Truespeak Fit?

Define rebooking rate as patients booking within the chosen window divided by patients contacted. Report recalls actioned, replies, opt-outs and failed deliveries alongside that rate, separately for each workflow. A contact attempt and a booking need separate records.

For an Australian physio clinic that wants an approval-based reactivation process built around its existing practice software and then run for it, Truespeak is built for exactly that.

I design, build and run automation, including monitoring failures and reviewing exceptions. Agent Helper and Broker Book use the same pattern in real estate and mortgage broking: identify a reason to contact someone and prepare the approach for approval. For Richardson & Wrench Campbelltown, Agent Helper scored 2,883 contacts and produced ranked call cards with a reason to call and an opening line.

Truespeak has no physio or allied health clients, no physio industry page and no completed Cliniko, Zanda or Nookal integration. Any connection needs discovery; where no usable connection exists, that step stays manual. A clinician or practice manager approves every message.

See follow-up automation, or book a discovery call to map the first queue.