Cliniko Multi-Location SMS: Separate Settings for Every Branch

Cliniko Multi-Location SMS: Separate Settings for Every Branch

Run SMS for every branch of your Cliniko account with its own number, reminder timing, messages and staff alerts. Learn which settings are per location, which run account-wide, and follow a branch-by-branch rollout checklist.

Running a clinic group across several branches brings its own SMS headaches. One site books mostly early morning physio, another runs evening Pilates classes, and a third does a lot of telehealth. A single reminder schedule and one set of messages rarely suits all of them.

If your practice runs several businesses inside one Cliniko account, DataFlows lets each location have its own SMS settings: its own sending number, reminder timing, messages and staff alerts. In this guide you will learn how Cliniko multi-location SMS works in DataFlows, which settings are per location and which run once for the whole account, how to handle numbers and Sender IDs across branches, and a branch-by-branch checklist for rolling it out.

What Is Cliniko Multi-Location SMS?

Cliniko multi-location SMS is the ability to run patient text messaging for several clinic branches from one Cliniko account, with each branch configured on its own terms. In Cliniko, a practice with more than one site usually sets each site up as a separate business on the same account. When you connect that account to DataFlows, every business or location is pulled in automatically. Each location then gets its own settings tab in DataFlows, where you choose the sending number, reminder timing, reminder and confirmation messages, the alert email and the staff SMS alert contacts for that branch. A few account-level features are the exception: recalls, post-appointment follow-ups and invoice SMS run once for the whole account using the default location's settings. Patient replies from every branch land in one combined Inbox, with each conversation labelled by location, so a central front desk or each branch team can see exactly where a message belongs.

Why It Matters for Australian Businesses

Australian allied health groups often grow one site at a time. A practice that started with one room in a suburban centre may now run three or four clinics across a city, each with its own patients, practitioners and opening hours. SMS settings that suit one site can easily be wrong for another.

Per-location settings matter for a few practical reasons:

  • Patients expect the right branch details. A reminder that names the wrong clinic or gives the wrong context causes confusion and calls to reception.
  • Branches run on different rhythms. A site that takes many same-day bookings may want a fixed daily reminder time, while a site with long initial consults may want reminders 48 hours out.
  • Escalations need to reach the right team. When a patient asks to reschedule, the alert should go to the staff at that branch, not to a shared inbox nobody owns.
  • Compliance stays consistent. DataFlows is an ACMA-registered Originating Telco, messaging is designed around the Spam Act 2003, and a STOP reply opts the patient out across every location and feature on the account.

Key Benefits

  • Separate settings for every branch: each location has its own settings tab for number, reminder timing, messages, the alert email and staff SMS alert contacts.
  • Flexible numbers: share one Virtual Number across locations or give each location its own. Sharing one Sender ID across several locations is also supported.
  • Replies reach the right place: with a shared Virtual Number, each reply goes to the location that last texted that patient.
  • One Inbox for everyone: all locations appear in a single combined Inbox, with each conversation labelled by location.
  • A Dashboard that flags gaps: the Cliniko Dashboard shows a warning banner when some locations are not set up yet.
  • Simple account-wide features: recalls, post-appointment follow-ups and invoice SMS run once for the whole account, so there is one place to manage them.
  • No monthly fees for the integration: DataFlows is pay-as-you-go. You buy SMS credits and top up, and credits never expire.

How Per-Location Settings Work

What each location controls

When you connect Cliniko with your API key, DataFlows pulls in every business or location on the account. Each one gets its own settings tab. On that tab you set:

  • Sending number: a Virtual Number (two-way, so patients can reply) or a Sender ID (your clinic name, one-way only). A sending number is mandatory before Settings will save.
  • Reminder timing: "Hours before appointment" (a true rolling lead time, default 24 hours, up to 168) or "Fixed time each day" (default 09:00, which covers today's and tomorrow's appointments in one go). You can add a Second Reminder and any number of Additional Reminders, each with its own timing and message.
  • Messages: reminder, booking confirmation, cancellation notice and reschedule notice templates, with merge tags such as {patient_name}, {date}, {time}, {practitioner} and {business}, plus message overrides by appointment type.
  • The alert email: where escalation alerts go for that branch.
  • Staff SMS alert contacts: named staff at that branch who receive SMS alerts when a reply needs a person.

Because messages are set per location, the {business} tag and your wording can match each branch. A city clinic can mention parking in its reminder, while a suburban site can mention its side entrance.

What runs once for the whole account

Three features are account-wide rather than per location:

  • Recalls: recall automation uses Cliniko's own recall records and runs once for the account.
  • Post-appointment follow-ups: the follow-up message sent to attended patients runs once for the account.
  • Invoice SMS: the text sent when a new unpaid invoice is created in Cliniko runs once for the account.

These three use the default location's settings. Before you switch them on, check which location is your default and make sure its sending number and settings are the ones you want every patient to see for these messages. Because a single template covers every branch, write recall, follow-up and invoice messages so they read correctly for patients of any location. The {practitioner_name} tag in follow-ups helps keep them personal.

Sharing a Virtual Number or giving each branch its own

You have two options for Virtual Numbers:

  • One shared number: every location sends from the same Australian mobile number. When a patient replies, the reply goes to the location that last texted that patient. This keeps costs down and gives patients one number to save.
  • One number per location: each branch has its own Virtual Number. This suits groups where branches run as separate teams, or where patients often see more than one location and you want replies kept clearly apart.

A Virtual Number is $10 a month with no setup fee, and receiving replies is free. Almost every reply-driven feature (AI confirmations, cancel and reschedule detection, waitlist claims, the Inbox and replying STOP) needs a Virtual Number, so it is strongly recommended for every location.

Sharing a Sender ID

One Sender ID can be shared by several locations. That suits a group that sends under one brand name. Remember that a Sender ID is one-way: patients cannot reply to it, so AI reply handling and the Inbox will not work for locations that use only a Sender ID. You can request a Sender ID from Settings. Registration is an Australian carrier requirement and is not instant, so allow time before you switch a branch over.

Alerts per location

The alert email and the staff SMS alert contacts are set per location. When the AI flags a cancellation, reschedule request, question or low-confidence reply, the alert goes to that branch's contacts. DataFlows never cancels or reschedules an appointment itself: confirming an appointment is the only automatic change it makes in Cliniko. Everything else is passed to your staff, a note is added to the appointment, and the patient gets a "someone will be in touch" reply from your own editable template.

The Dashboard and Inbox across locations

The Dashboard shows status banners, including a warning when some locations are not set up. Treat that banner as your rollout to-do list: it stays until every location has its settings saved.

The Patient Inbox combines all locations into one view, with each conversation labelled by location. A central reception team can work the whole Inbox, while branch staff can quickly pick out their own patients. AI badges show the classified intent and confidence, and unread and pending-escalation badges show what still needs attention.

Branch-by-Branch Rollout Checklist

Use this checklist to set up a multi-location Cliniko account in DataFlows. Work through one branch fully before moving to the next.

Before you start

  • Connect Cliniko once: add your Cliniko API key (in Cliniko: click your name bottom-left, then My Info, then Manage API keys, then Add API key). Use a key from a Cliniko user who can view and edit patients and appointments.
  • Confirm all locations appear: check that every business on the account has been pulled into DataFlows.
  • Decide your number plan: one shared Virtual Number, one per location, or a mix. Get any numbers you need from the Numbers page.
  • Request Sender IDs early: if any branch will use a Sender ID, request it from Settings now, since registration is not instant.
  • Pick your default location: recalls, post-appointment follow-ups and invoice SMS will use its settings.

For each location

  1. Open the location's settings tab and choose its sending number. Settings will not save without one.
  2. Set reminder timing to suit that branch. Remember only one reminder in total may use fixed-time mode, and two rolling reminders cannot use the same hours.
  3. Write the messages. Use the Insert buttons for merge tags and watch the live SMS part counter: messages over 160 characters split into more parts and are billed accordingly.
  4. Add appointment type overrides where needed, for example a Telehealth message that mentions a video call.
  5. Set the alert email to the person or team who handles that branch's escalations.
  6. Add staff SMS alert contacts for that branch, if you want SMS alerts as well as email. Email alerts are free; SMS staff alerts use credits.
  7. Review AI reply handling: check the confirm, cancel and reschedule keywords, the auto-confirm confidence threshold (default 75%) and the optional "Clinic context for AI" text for that branch.
  8. Save and test: book a test appointment for a staff member's own mobile, check the reminder arrives with the right branch details, and reply to confirm the reply lands under the right location in the Inbox.

After every location is live

  • Check the Dashboard: the "locations not set up" warning should be gone.
  • Switch on account-wide features: turn on recalls, post-appointment follow-ups and invoice SMS once you are happy with the default location's settings.
  • Brief each branch team: show them how the Inbox labels conversations by location and who receives alerts for their site.
  • Review the Activity Log weekly at first: look at Reminders Sent and the AI Reply Processing Log for each branch to spot wording that confuses patients.

How DataFlows Helps

DataFlows connects to Cliniko natively. It checks Cliniko's API directly, so there is no third-party automation tool in the middle. Connecting takes one field, your Cliniko API key, and DataFlows reads the region from the key, encrypts it and pulls in every business on the account.

From there, the Cliniko integration gives each branch its own settings while keeping one login, one Inbox, one Blacklist and one credit balance for the group. Patients get reminders and confirmations that suit their branch, staff get alerts for their own site, and managers get a Dashboard that shows reminders sent, appointments auto-confirmed by AI and replies escalated to staff.

The integration is built on DataFlows Virtual Numbers and registered Sender IDs. There are no monthly fees on any plan, credits never expire, and free setup is available. Hosted in Sydney, with encrypted (HTTPS) connections. Data can be deleted on request.

Best Practices

  • Use a Virtual Number for every location: reply-driven features need one, and a shared number keeps things simple for most groups.
  • Choose your default location carefully: recalls, post-appointment follow-ups and invoice SMS all use its settings.
  • Keep account-wide templates branch-neutral: write recall, follow-up and invoice messages so they make sense to patients of any location.
  • Put the branch in the message: use the {business} tag so patients always know which clinic the reminder is from.
  • Route alerts to real people: set each location's alert email and staff SMS contacts to the team that will act on them, not a general mailbox.
  • Keep messages to one SMS part: check the live counter, since longer messages use more credits.
  • Respect opt-outs across the group: a STOP from a patient blocks SMS from every location and feature, so do not try to re-add them at another branch. To resume, the patient's number has to be removed from the Blacklist.
  • Clear the Dashboard warning: do not leave a location half set up. Patients at that branch may miss out on reminders.

Conclusion

Running SMS for several Cliniko locations does not have to mean one compromise setup for every branch. With DataFlows, each location gets its own number, reminder timing, messages and alert contacts, while recalls, post-appointment follow-ups and invoice SMS run once for the whole account. Replies from every branch land in one Inbox labelled by location, and the Dashboard tells you when a site still needs setting up.

Ready to roll it out across your clinics? Sign up at dataflows.com.au, connect your Cliniko account, and work through the checklist above one branch at a time. Free setup is available if you would like a hand.

You May Also Like