Skip to main content
GullySystem
Healthcare

WhatsApp, SMS and Email Notifications for Physiotherapy clinics

Send business messages from approved events and recipient rules.

Platform

Does this function belong in your operation?

Use when people need consistent updates triggered by business records.

An order, payment, booking or task reaches a notification event.

Patients receive appointment reminders, and the clinic gets call lists of those who missed a session or whose package has run out.

Bring the records the workflow depends on.

  • Message events
  • Recipient permissions
  • Approved channel accounts and wording

Outputs to check

  • Message event and recipient log
  • Delivery and failure status
  • Retry or follow-up queue

Follow the whatsapp, sms and email notifications workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the trigger

    Specify the business event and the message it justifies.

  2. 2. Select recipients

    Apply contact, permission and audience rules.

  3. 3. Prepare the message

    Use the approved content and required event details.

  4. 4. Submit through the channel

    Retain the attempt reference and distinguish queued from delivered status.

  5. 5. Resolve failures

    Correct invalid details or retry under the agreed duplicate-control rule.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Office assistant

Reviews event messages, checks recipient details and resolves failed or withheld submissions.

Accounts assistant

Checks financial message content and follows up delivery failures without changing the underlying ledger.

Owner

Reads what went out in the business’s name. Every word is on file.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Invalid recipient

Hold the message and request a corrected address or number.

Provider rejects message

Record the reason and retry only under the agreed rule.

Event repeated

Use the event reference to avoid unintended duplicate messages.

Can this work independently?

Notifications depend on a source event and an authorised delivery channel. They can use file or manual triggers, but order, booking or payment systems provide more reliable references. Provider acceptance, delivery and human reading are distinct outcomes and should not be treated as equivalent.

Systems and records it connects with

  • Collections and follow-up: Due balances, payment promises and follow-up outcomes.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Service reminders: Due-service triggers and follow-up outcomes.

Configure, test and introduce the workflow.

  • Gather the messages your staff type today. We write back which can come from records and which stay manual.
  • You approve wording and languages. Templates arrive for each channel, ready for the approval step WhatsApp requires. Sender details come from you. Share the WhatsApp number, SMS account and email, and a test message reaches your own phone before customers see any.
  • Go live small. A handful of customers receive live messages, staff check delivery status, and the office is trained.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • A repeated event does not send unintended duplicates.
  • Recipient rules respect recorded permissions.
  • Failures are visible for follow-up.
Physiotherapy clinics

How the business operates.

Physiotherapy clinics, sports injury centres and single therapist practices book sessions by therapist and treatment plinth. Each patient record works as the clinic’s EMR, holding the assessment, treatment plan, SOAP progress notes and the session package counted visit by visit. Billing follows the sessions done. Exercise sheets go home with the patient. GullySystem sets up the branches, therapists and packages you choose.

Patient records and case history

Keep registration details, complaint, medical history, referring doctor and every earlier course of treatment in one electronic medical record, or EMR. Consent for treatment is attached to the same record.

Appointments and therapist calendar

Book first visits, follow-ups and home visits by therapist and treatment plinth or room, with walk-ins, reschedules and cancellations on the same screen.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Patient records and case history. Keep registration details, complaint, medical history, referring doctor and every earlier course of treatment in one electronic medical record, or EMR. Consent for treatment is attached to the same record.
  • Appointments and therapist calendar. Book first visits, follow-ups and home visits by therapist and treatment plinth or room, with walk-ins, reschedules and cancellations on the same screen.
  • Assessment and progress notes. Record findings, goals, goniometer readings, outcome scores and a note for each session, under subjective and objective headings or whatever the clinic sets. The next therapist opens the plan and sees what was done.
  • Rehab plans and session packages. Set out a plan and sell a package of sessions for a frozen shoulder, a knee replacement or a stroke recovery. See sessions used, sessions remaining and the package end date.

Operational bottlenecks to check

Patient notes sit in paper files

A patient’s first assessment is in one folder and later sessions are in another. The therapist covering a day off has to ask what was done last, from the ultrasound dose to the cervical traction weight. Nobody writes it down.

Package sessions are counted by hand

A patient paid for ten sessions of lumbar rehab and believes some are left. Without a count against the patient’s name, the balance is a matter of memory.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and booking

    A patient calls, comes in with a surgeon’s referral or books online. The first visit goes on the calendar against a therapist and a treatment plinth.

  2. 2. Assessment

    The therapist records the complaint, history, findings and goals, such as range of motion, gait and pain scale. A treatment plan follows, with the number of sessions suggested for the lumbar spine, shoulder or knee.

  3. 3. Sessions

    Each visit is marked done by the therapist, with a short progress note. The session is counted against the package or the plan, along with the modality used, from interferential current to a hot pack.

  4. 4. Home exercises

    An exercise sheet with the sets, repeats and cautions is shared with the patient on WhatsApp or printed at the desk. Gait or posture cues are added in words.

  5. 5. Billing

    Reception bills the session, or takes one off the package balance, paid in cash, by bank transfer or on a card. Kinesio tape, bands or equipment hire go on the same bill.

  6. 6. Review and follow-up

    A review note is written when the plan ends or is changed. Patients who have missed a session are listed for a call, and the referring doctor can be sent an update.

Industry reports to connect with

  • Sessions done by therapist and by branch
  • Package balances and sessions left per patient
  • Patients who have missed their next session
  • Therapist payout for the month

Questions before implementation.

When should physiotherapy clinics consider whatsapp, sms and email notifications?

Use when people need consistent updates triggered by business records. An order, payment, booking or task reaches a notification event.

What should we bring to the requirements discussion?

Bring anonymised examples of Message events; Recipient permissions; Approved channel accounts and wording. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Send business messages from approved events and recipient rules. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Messaging depends on provider availability, account permissions and current channel rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A repeated event does not send unintended duplicates. Use this check when reviewing the first working version.

Talk to us

Discuss whatsapp, sms and email notifications for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements