Running SMS reminders and campaigns from a clinic is the easy part. The harder question comes later, when a patient says "I never agreed to these texts", a practice manager wants to know why an appointment was marked confirmed, or an auditor asks how the clinic handles opt-outs. At that point you need a clear record, not a memory of what probably happened.
This guide explains how the DataFlows Cliniko integration builds an SMS audit trail as it works. You will learn how consent checks apply to reminders, campaigns and recalls, how STOP replies are recorded in Cliniko, where appointment notes fit in, what the Activity Log shows, and exactly which columns come out of the Export Replies (CSV) report.
What Is a Cliniko SMS Audit Trail?
A Cliniko SMS audit trail is the combined record of who your clinic texted, why they were eligible to receive that message, what they replied, and what happened next. In a DataFlows and Cliniko setup, that record lives in two places. Inside Cliniko, every message sent is logged in the patient's Communications, STOP replies are recorded in the patient file, the SMS marketing opt-in is updated, and optional notes can be added to appointments. Inside DataFlows, the Activity Log keeps a running history of reminders, appointment event messages and reply processing, with an export to CSV for the reply side. Together they let staff answer practical questions quickly: did this patient get a reminder, did they confirm, did the AI classify the reply correctly, and were they opted in to marketing when a campaign went out. It is not a legal compliance product on its own, but it gives you the evidence trail to support the obligations your practice already has.
Why It Matters for Australian Clinics
Australian clinics send two very different kinds of SMS. Appointment reminders and confirmations are service messages tied to a booking. Recalls, reactivation campaigns and promotions are treated as marketing, and marketing messages in Australia are covered by the Spam Act 2003, which centres on consent, sender identification and a working way to unsubscribe.
Health businesses also handle sensitive personal information, so it pays to know exactly what is stored and where. The DataFlows app and database are hosted in Sydney, with encrypted (HTTPS) connections, and data can be deleted on request. DataFlows stores patient names, mobile numbers, message text, delivery status and replies so that the audit trail exists in the first place.
This article explains how the software behaves. It is not legal advice. Every practice should check its own obligations under the Spam Act, the Privacy Act and any professional body guidelines, and talk to an adviser if unsure.
Key Benefits of a Built-In SMS Audit Trail
- Consent is checked before sending, not after. Reminders follow each patient's Cliniko reminder preference, and campaigns and recalls default to patients opted in to SMS marketing in Cliniko.
- Opt-outs are recorded where staff look. A STOP reply turns off the marketing opt-in in Cliniko, records the STOP in the patient file and blocks the number across the whole DataFlows account.
- Every automatic change is explainable. The only change DataFlows makes to an appointment automatically is marking it confirmed, and the Activity Log shows the reply, intent, confidence score and action behind it.
- Messages appear in the patient record. Every message sent is logged in the patient's Communications in Cliniko, so front desk staff do not need to switch systems to see what went out.
- Reply history can leave the system. Export Replies (CSV) gives you a spreadsheet for reviews, spot checks or internal reporting.
Step by Step: How the Audit Trail Builds Itself
1. Reminders follow each patient's reminder preference
In the Reminders settings, the option "Follow each patient's reminder preference in Cliniko" makes DataFlows respect what is already recorded in Cliniko. Patients set to Email or None get no SMS reminders. This option is on for new setups.
That means the decision about whether a patient wants SMS reminders stays in one place: their Cliniko file. If a patient changes their mind at reception, staff update Cliniko and the next reminder run follows it.
2. Campaigns default to patients opted in to SMS marketing
The Campaign Builder finds patients by appointment date range and outcome, or by how long ago their last appointment was. The option "Only patients who've opted in to SMS marketing in Cliniko" is ticked by default.
When you reach the review screen, it shows how many patients were left out by that check. This is useful evidence in its own right: you can see that the filter ran and how much it narrowed the list before anyone pressed Send. Untick the option only for non-marketing practice notices, such as a clinic closure, and keep a note of why.
3. Recalls are treated as marketing
Recall Automation uses Cliniko's own recall records and is checked once a day. Because recalls are treated as marketing under the Spam Act 2003, by default only patients opted in to SMS marketing in Cliniko are sent a recall. A skipped recall is retried later if the patient opts in, so you do not lose the recall by respecting consent. Recall messages should include opt-out wording.
Recurring Schedules work differently. They are designed for pre-appointment messages such as consent confirmations, so the marketing opt-in check is not applied to those drafts. Nothing recurring sends by itself: each run only prepares a draft that a person must review and send, which adds a human checkpoint to the record.
4. STOP replies update Cliniko and the Blacklist
When a patient replies STOP (or QUIT, END or UNSUBSCRIBE, unless those words are used in a keyword list), DataFlows does several things at once:
- Blacklist. The number goes on the account Blacklist, so no further SMS goes out from any location or feature.
- Cliniko opt-in. The patient's SMS marketing opt-in is turned off in Cliniko.
- Patient file. The STOP is recorded in the patient's Cliniko file. Reminder settings are left alone.
- Activity Log. The opt-out shows in the AI Reply Processing Log.
Your clinic's own confirm, cancel and reschedule words never count as opt-outs. To resume messaging a patient who opts back in, remove the number from the Blacklist.
5. Optional notes on the Cliniko appointment
Notes put context directly on the appointment, where clinicians and reception already look. There are three places they come from:
- Confirmations. Turn on "Log confirmations to Cliniko notes" if you want a note added when a patient confirms. It is off by default.
- Escalations. When a reply is a cancellation, a reschedule request, a question or anything below the confidence threshold, DataFlows never cancels or reschedules the appointment. Instead it flags the reply to staff by email or SMS, adds a note to the appointment, and sends the patient a "someone will be in touch" reply.
- Surveys. If you run satisfaction surveys, you can optionally add a note to the Cliniko appointment as well.
6. Review the Activity Log
The Activity Log in DataFlows has three sections:
- Reminders Sent. Every reminder that went out.
- Appointment Events Sent. Booking confirmations, cancellation notices and reschedule notices.
- AI Reply Processing Log. What the patient said, the detected intent, the confidence score and the action taken. Opt-outs are shown here too.
Exact keyword matches such as YES or CANCEL are handled instantly without the AI. Anything else is classified by the AI with a confidence score, and only a confident confirmation (default threshold 75%, adjustable) is marked confirmed in Cliniko. The log lets you check those decisions one by one.
7. Export Replies (CSV)
From the Activity Log, "Export Replies (CSV)" downloads a spreadsheet with these columns:
- Reminder sent at and message sent
- Patient name and patient phone
- Patient reply and reply received at
- AI intent and AI confidence
- Action taken
- Cliniko appointment ID
The export is reply-driven. Reminders that nobody replied to are not included. If you need to show that a reminder went out to a patient who never responded, use the Reminders Sent section of the Activity Log and the patient's Communications in Cliniko rather than the CSV.
How DataFlows Helps
The DataFlows Cliniko integration is native. DataFlows checks Cliniko's API directly, so there is no third party automation tool in the middle and no extra system to audit. You connect it with a single Cliniko API key, ideally from a Cliniko user who can view and edit patients and appointments, because that access is needed to record opt-outs and mark confirmations.
For a full audit trail you will want a Virtual Number. Replies, AI confirmations, escalations and STOP opt-outs all depend on patients being able to text back, and a Sender ID is one-way only. An Australian Virtual Number is $10 a month with no setup fee, and receiving replies is free. One number can be shared across locations.
DataFlows is an ACMA-registered Originating Telco and its messaging is designed around the Spam Act 2003, with STOP style replies handled automatically platform-wide. Pricing is pay-as-you-go: you buy SMS credits and top up, with no monthly fees on any plan and no monthly fee for the Cliniko integration. Credits never expire. You can start with a free 2 week trial, no credit card required. See bulk SMS pricing for current rates.
Best Practices for Clinic SMS Records
- Keep Cliniko as the source of truth. Record reminder preferences and SMS marketing opt-ins in Cliniko, and let DataFlows read them rather than keeping a separate list.
- Leave the marketing opt-in filter ticked. Untick it only for genuine practice notices, and note the reason in the campaign name or your internal records.
- Put opt-out wording in marketing messages. Recalls and campaigns should tell patients how to stop messages.
- Decide on confirmation notes early. If your team wants confirmations visible on the appointment, turn on "Log confirmations to Cliniko notes" before you go live.
- Export replies on a regular schedule. A monthly CSV export gives you a dated snapshot you can file with your own records.
- Spot check AI decisions. Review a sample of the AI Reply Processing Log and adjust the confidence threshold or clinic context if needed.
- Check your obligations. Confirm your consent and record keeping practices with your own advisers. The software supports your process; it does not replace it.
Conclusion
A good SMS audit trail is built while messages are being sent, not reconstructed afterwards. With DataFlows and Cliniko, reminders respect each patient's preference, campaigns and recalls default to opted in patients, STOP replies update Cliniko and the Blacklist, and the Activity Log and CSV export show what patients said and what happened next.
Ready to give your clinic a clear record of every patient SMS? Sign up at dataflows.com.au and connect Cliniko in minutes.
