For clinics, diagnostics and hospitals

Fewer missed appointments.

Remind patients before they are due, tell them the moment a report is ready, and answer the reply on the same screen — over SMS, WhatsApp and email, from one patient list.

Reminders scheduled off a date on the recordSMS, WhatsApp and email in one inboxPatient name, phone and email encrypted at rest
The QuickGrow dashboard — sidebar, header and the headline counters for a workspace with 25,000 contacts.

The reception phone is the bottleneck.

Most of what a clinic desk does all day is repeat the same four sentences. None of it needs a person, and all of it costs you a slot when it does not happen.

Patients forget

A slot booked three weeks ago is a slot nobody remembers. The chair sits empty and the queue behind it does not move up.

“Is my report ready?”

The same call, twenty times a day, for a result that has been sitting at the counter since morning.

Follow-ups never happen

The review visit, the repeat test, the medicine reminder — everyone agrees they matter and nobody has time to make the calls.

Replies scatter

One number gets the SMS, someone’s personal WhatsApp gets the photo, and the clinic address gets the email. Nobody sees all three.

You set the date once. It sends itself.

A reminder is not a broadcast — it is tied to one patient’s date. You put the date on the record, say how long before it should go out, and the schedule does the rest.

  1. Put the date on the record

    Appointment date, test date, review date — each patient carries their own dates as fields on their contact record. Import them from a spreadsheet, type them in, or have your practice software write them in over the API.

  2. Pick the offset

    Choose a date-based trigger and say how many days before or after that date the journey should start. One day before the visit, seven days after a test, thirty days before a repeat prescription — same mechanism each time.

  3. Build the message steps

    Add the sends: SMS, WhatsApp or email, from a saved template with the patient’s name and time filled in. Put a wait between steps for a second nudge, and a condition branch for “only if they have not confirmed”.

  4. It runs on its own

    The schedule checks every minute and starts the journey for the patients who are due. Each patient enters a given reminder once per day, so a duplicate row in your list does not mean a duplicate message.

An automation on the builder canvas: a tag trigger, then email, WhatsApp and SMS steps separated by real time delays.
Automations

Every reminder is the same four pieces.

Trigger, wait, send, branch. The canvas below is a cart-recovery journey from the demo workspace, but an appointment reminder is built from exactly the same blocks — which is the point. Learn it once and every other reminder in the clinic is twenty minutes of work.

  • Triggers: a date on the record, a tag added, a field changed, a form submitted, a new contact.
  • Steps: send on any of the three channels, wait, add or remove a tag, update a field.
  • Branches: split on a field value so confirmed patients drop out of the chase.
The shared inbox: a conversation list with WhatsApp, Email and SMS threads side by side, next to an open WhatsApp conversation.
Shared inbox

A patient replies. Someone sees it.

Every inbound message — SMS, WhatsApp or email — becomes a conversation in one list, whichever channel it arrived on. The desk works the list instead of three phones, and the thread stays with the patient record it belongs to.

  • Assign a conversation to a named person, then resolve, reopen or tag it.
  • Saved quick replies for the answers you give forty times a week.
  • A reply on WhatsApp opens a 24-hour window — inside it you can write freely, outside it only an approved template goes out.

A report-ready alert is not a newsletter.

The three channels are not interchangeable, and the difference matters most for the messages a patient is waiting on. This is what each one actually does.

For a report-ready alert, WhatsApp and SMS both arrive without the patient opening anything, and neither needs the desk to pick up the phone. You choose which one to use for each patient — nothing switches channel on its own if a send fails. Keep email for the case where the document itself is going out.
WhatsAppSMSEmail
Reaches a patient with a basic handsetNoYesNo
Can start a conversation coldApproved template onlyYesYes
Sender the patient recognisesYour business numberBranded sender name with Masking SMSYour own domain
Room for detail and attachmentsShort, with buttonsA line or twoYes
Reply lands in the shared inboxYesYesYes
Held back overnight9pm to 8am9pm to 8amSends any hour

Kept apart, kept short, kept honest.

QuickGrow is a messaging system, not a medical records system, and it holds no health certification of any kind. Treat it as the layer that tells a patient to come in — never as the place the clinical detail lives.

One branch cannot see another

  • Each branch or brand is its own workspace with its own patient list, senders and templates.
  • A contact belongs to one workspace unless you deliberately mark it shared across the account.
  • Staff get a role — reception, marketing, manager — and the role decides who can open the inbox, send, or export the list.

The record itself

  • Patient name, phone number and email are encrypted where they are stored.
  • Every action is written to an audit trail that is never quietly deleted.
  • An erasure request removes the contact along with their messages, activity and consent records, in one go.

Guardrails on sending

  • Consent is checked per channel before an SMS goes out — no consent, no send.
  • Quiet hours hold SMS and WhatsApp back between 9pm and 8am local time.
  • Per-patient send caps and a cooldown stop the same person being messaged all day.

Five jobs, set up once.

None of these need a person once they are built. Between them they are most of what the desk repeats every day.

Date-based

Appointment reminders

One the day before and one on the morning of, from the appointment date on the record. A condition branch drops the patient who already confirmed.

API or tag

Report-ready alerts

Your lab system calls the API when the result is signed off, and the alert goes out that minute — a WhatsApp template, or SMS for a patient without it.

Date-based

Post-visit follow-ups

Seven days after the visit, a check-in. Thirty days before a repeat test is due, a nudge to book it.

Segments

Recall lists

Build a segment with the rule builder — patients tagged for a screening, not seen in twelve months — and send the recall to just them.

Inbox

The reply desk

One list for every inbound message across the three channels, assigned to the person on duty and resolved when it is done.

Automatic

Opt-outs handled

An opt-out reply is captured and flagged. Withdrawing consent is a step someone takes; from then on every campaign skips that patient automatically.

The things worth knowing before you sign up.

How does the system know when a patient’s appointment is?

You put the date on the patient’s contact record as a field — imported from a spreadsheet, typed in, or written by your own software through the API. A date-based automation then starts a set number of days before or after that date. The schedule checks every minute and enters each patient at most once a day, so a duplicated row does not become a duplicated message.

What happens when a patient replies to a reminder?

The reply becomes a conversation in the shared inbox, whichever of the three channels it came in on. Anyone with inbox access can pick it up, assign it to a colleague, answer with a saved quick reply and mark it resolved. On WhatsApp a reply opens a 24-hour window in which you can write freely; outside that window only an approved template can go out. If the reply is STOP or UNSUBSCRIBE it is flagged for your team to act on — on SMS that removal is not automatic today, though once done every later campaign skips them.

Which channel should a report-ready alert go on?

WhatsApp first if the patient uses it: a utility template is the category meant for account and order updates, and it is delivered without needing an open conversation. Fall back to SMS for a patient on a basic handset — Masking SMS puts your clinic name in the sender field so it does not look like spam. Use email when the document itself is what you are sending. Bear in mind both SMS and WhatsApp are held back between 9pm and 8am, so a result signed off late at night goes out first thing.

Keep patients informed, not chasing.

Build one reminder and see what a week without “is my report ready?” looks like. You pay a platform fee plus the channels you actually send on — and buying volume waives part of the fee.