A patient replies to your appointment reminder at 7:40 in the evening. Somebody has to read that message, work out who sent it, and decide what to do. If replies land in a personal phone, a shared mailbox or nowhere at all, they get missed, and a missed reply can mean an empty appointment slot the next morning.
A two-way SMS inbox fixes this by putting every patient reply in one place, linked to the right patient and the right location. For clinics that use Cliniko, the DataFlows integration (branded the AI SMS Receptionist) includes a Patient Inbox built for exactly this job.
In this guide you will learn what a two-way SMS inbox is, why it matters for Australian clinics, how the Cliniko Patient Inbox works, how it sits alongside AI reply classification, and the habits that keep it running smoothly.
What Is a Two-Way SMS Inbox?
A two-way SMS inbox is a shared screen where a business can read, track and answer text messages from customers in a single conversation thread. Instead of sending reminders in one direction and hoping nothing comes back, the business sends from a number that can also receive replies. Each incoming message is matched to the person who sent it, grouped with earlier messages in the same conversation, and shown to staff with a clear sign that something is waiting. Staff can reply directly in the thread, so the whole exchange stays in one place instead of being scattered across phones and email accounts. For a clinic, this means a patient's answer to a reminder, a question about parking, or a request to move an appointment is visible to the whole front-desk team. The inbox depends on a sending number that accepts replies, which is why the number you choose matters as much as the software around it.
Why a Two-Way Inbox Matters for Australian Clinics
Most Australian clinics already send appointment reminders by SMS, and patients are used to replying to them. A short text such as "Can we do 3pm instead?" is far easier for a patient than ringing the clinic during opening hours. That ease only helps if someone actually sees the reply.
Clinics with more than one location face an extra problem. Replies can arrive for different sites, and staff at one site may not know what the other site has already handled. A combined inbox removes that guesswork.
There is also a compliance angle. Patients who text STOP expect the messages to stop, and the Spam Act 2003 expects the sender to honour that. An inbox that handles opt-outs properly protects both the patient and the clinic.
Key Benefits of the Cliniko Patient Inbox
- One combined inbox for every location. All locations on your Cliniko account feed into the same inbox, and each conversation is labelled by location so staff always know which site it belongs to.
- Patient names resolved automatically. Replies show the patient's name rather than a bare mobile number, so staff can respond without hunting through Cliniko first.
- Replies in the thread. Staff reply inside the conversation, so the patient's message, the clinic's answer and any earlier reminder sit together in order.
- Unread and pending-escalation badges. You can see at a glance which conversations are new and which ones the AI has passed to a person.
- AI badges with confidence. When a reply has been classified as a confirmation, cancellation, reschedule request or question, the thread shows a badge with the confidence score.
- Opt-outs handled correctly. A STOP reply removes the conversation from the inbox, while the record stays in the Activity Log and on the Blacklist.
How the Two-Way Inbox Works Step by Step
Step 1: Connect Cliniko
Connecting takes one field: your Cliniko API key. In Cliniko, click your name at the bottom left, choose My Info, then Manage API keys and Add API key. Use a key from a Cliniko user who can view and edit patients and appointments, because DataFlows needs that access to mark confirmations and record opt-outs. Paste the key into DataFlows. It reads the region from the key, encrypts it, and pulls in every business and location on the account. An active, paid DataFlows account is required.
Step 2: Choose a sending number that can receive replies
Before Settings will save, each location needs a sending number. You can pick a Virtual Number or a Sender ID. The difference matters for the inbox. A Virtual Number is two-way, so patients can reply. A Sender ID, such as your clinic name, is one-way only, and Sender ID messages cannot receive replies.
Because the Patient Inbox, AI confirmations and STOP handling all depend on replies, a Virtual Number is strongly recommended. Each location that wants two-way replies needs its own Virtual Number. One Sender ID can be shared by several locations, but those locations will not receive replies.
Step 3: Send reminders and messages as normal
Once the number is set, reminders, booking confirmations and other messages go out from it. When a patient replies, the message arrives in the Patient Inbox. Nothing extra needs to be configured for the thread to appear.
Step 4: Read, reply and clear the queue
Open the inbox and look at the badges. Unread conversations are marked, and conversations waiting for a person are flagged as pending escalation. Open a thread, read the patient's message, and type your reply. Staff replies are sent from the same number the patient texted, so the conversation feels continuous to them.
Step 5: Check the record
The Activity Log keeps the history. Its AI Reply Processing Log shows what the patient said, the intent, the confidence score and the action taken, including opt-outs. You can also use Export Replies (CSV) to get reminder sent time, message sent, patient name and phone, patient reply, reply received time, AI intent and confidence, action taken and the Cliniko appointment ID. The export is reply-driven, so reminders with no reply are not included.
How the Inbox and the AI Receptionist Work Together
The inbox is not a separate tool bolted onto the side. It is the human half of the same reply pipeline that the AI SMS Receptionist uses.
When a patient replies, DataFlows first checks for an exact keyword match. Words such as YES, NO and MOVE are handled instantly without the AI, and the keyword lists are customisable. If the reply is not a keyword, the AI classifies it as a confirmation, cancellation, reschedule request or question, and gives it a confidence score. The patient can write in plain English, for example "Yep I'll be there" or "Something came up".
What happens next depends on the result:
- A confident confirmation is marked as confirmed in Cliniko automatically. The auto-confirm confidence threshold defaults to 75% and can be adjusted.
- Cancellations and reschedule requests are never actioned automatically. They are escalated to staff, and they appear in the inbox with a pending-escalation badge.
- Questions and low-confidence replies are also escalated to staff, so a person reads anything the AI is unsure about.
It is worth being clear about what the AI does not do. It classifies replies. It does not write free-text replies, and it is not a chatbot. When the inbox shows an AI badge, it is a label and a confidence score to help your team triage faster. The answer to the patient still comes from your staff, or from the clinic's own editable templates, such as the optional confirmation reply and the message telling a patient that a person will follow up.
Staff alerts can go by email, which defaults to the login email, and by SMS to named staff. Combined with the inbox badges, nothing needs to wait until someone remembers to check.
How DataFlows Helps
DataFlows is an Australian SMS platform, and the Cliniko integration is native. DataFlows checks Cliniko's API directly for appointment data, so there is no third-party automation tool in the middle. You connect with one API key, pick your numbers, and the inbox, reminders and AI reply handling work from the same setup.
Pricing is pay-as-you-go. You buy SMS credits and top up when you need to, with no monthly or annual fees for DataFlows messaging, and credits do not expire. Every message your clinic sends, including staff replies from the inbox, uses credits in the usual way.
The Cliniko integration also gives you the Dashboard with stat cards for Reminders Sent, Auto-Confirmed by AI and Escalated to Staff, a list of the latest AI activity, and a rolling 14-day Confirmation Tracker. Read together with the inbox, you can see both the numbers and the individual conversations behind them.
Best Practices
- Use a Virtual Number at every location that wants replies. A Sender ID is fine for one-way notices, but it cannot feed the inbox.
- Assign someone to check the inbox at set times. Badges help, but a routine such as start of day, midday and close keeps response times predictable.
- Treat AI badges as a guide, not a verdict. A low-confidence badge is a prompt to read the patient's actual words.
- Add clinic context for the AI. The optional Clinic context for AI field helps it understand the way your patients talk about your services.
- Edit your reply templates. The texts sent back to patients on confirmation and on escalation are your own wording. Keep them short, friendly and in your clinic's voice.
- Respect STOP every time. STOP, QUIT, END and UNSUBSCRIBE opt the patient out. The number goes on the account Blacklist, so no further SMS goes to them from any location or feature. To resume messaging, remove the number from the Blacklist, and only do that when the patient has asked to hear from you again.
- Review the Activity Log regularly. The AI Reply Processing Log is the quickest way to spot patterns, such as a reminder message that confuses patients.
Conclusion
A reminder system that cannot hear back is only doing half its job. The Cliniko Patient Inbox gives your front desk one place to see every reply across every location, with patient names, AI badges, unread and escalation flags, and a thread to answer in. The AI receptionist handles clear confirmations, and your team handles everything that needs a person.
Ready to try it? Sign up at dataflows.com.au, connect your Cliniko API key, set up a Virtual Number for each location, and give your patients a way to reply that your team will actually see.
You May Also Like
Cliniko AI SMS Reply Handling: Confirm, Cancel and Reschedule