MILabs
Integrations

Review request automation with Cliniko

Review request automation for Cliniko, with staff-approved wording, opt-out checks and a log of every request sent.

Updated 2026-03-14

Review request automation with Cliniko

Clinics that run their diary, records and invoices in Cliniko often share a gap with other small businesses: patients who had a good visit seldom get asked to leave a review. This build sends that request at the right moment, once the clinic has recorded a visit as complete. Healthcare calls for a more careful version of the usual pattern. A review message should carry no clinical detail, no treatment name and no reason for the visit, so the template relies only on the patient's name and a neutral thank you. Opt-out status is checked before anything goes out, and the clinic chooses which review sites are linked. Staff keep control of wording and timing. Because Cliniko holds the record of truth, the workflow reads from it under the access the clinic grants, and it keeps its own log of requests sent rather than writing into patient files.

How it works

  1. Confirm with the clinic which Cliniko API credentials and permissions are available, since the scope of the connection sets what the workflow can read.

  2. Set a trigger on visits the clinic marks as done, reading only the appointment date, the patient's name and the contact details on file.

  3. Check the opt-out and do-not-contact status for that patient before any message is built, so a patient who has asked not to be contacted receives nothing.

  4. Fill a neutral template with the patient's first name and send it by email or SMS, using the review link the clinic has approved.

  5. Record each request in the workflow's own log, leaving Cliniko's clinical and billing records untouched, and review the log with the team regularly.

good questions, straight answers

Frequently asked questions

How does MILabs test a review request automation against Cliniko?
MILabs tests the workflow with test contacts and sample completed visits before any live message goes out. The checks cover the opt-out rule, the wording of each template, the link to each review site and the entry in the request log. Where a Cliniko connection is involved, the test uses the credentials and permissions the clinic has set, so the team can confirm what the workflow can reach. The clinic approves the final wording before any real patient receives a message.
What does MILabs do after delivering a review request automation for Cliniko?
After handover, MILabs checks the request log with the clinic to confirm that messages are going to the right contacts and that opt-outs are respected. The team can adjust templates, timing rules and the linked review sites when the clinic's needs change. Any change to the Cliniko connection is agreed with the clinic first, since permissions sit in its own account. MILabs is a Sydney agency and delivers work for clinics outside Sydney remotely.
Can a review request automation work with Cliniko?
Yes, the workflow can be built to connect with Cliniko, provided the clinic creates API credentials in its own account and the permissions cover the appointment and contact details the workflow needs. Where those permissions do not reach a field, the build works around the gap. Clinics that prefer no direct connection can still use the approved-text route, where staff copy an approved reminder or message into Cliniko by hand while testing is under way.
What does a review request automation write to Cliniko?
In the planned version, the workflow does not write into Cliniko's clinical notes, invoices or patient files. It reads the details it needs to decide when a request is due, such as the visit details and the contact details on file, and it keeps a separate log of requests sent. Any write back to Cliniko would be a later addition, agreed with the clinic and limited to what its API permissions allow. Clinical and billing records stay under the clinic's control throughout.
What does a review request automation with Cliniko need from me?
It needs a clear decision on the wording of each message, the review sites you want to link, and the rule for who should not be contacted. You also need to confirm with your Cliniko administrator which API credentials and permissions can be created in your account, because that sets what the workflow can reach. Please provide sample contact details for testing, and name one person on your team who will check the request log.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.