Skip to main content
GullySystem
Healthcare

WhatsApp, SMS and Email Notifications for Eye hospitals

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.

Eye-hospital messages can concern a changed clinic slot, a clinician-authorised return to the consultation queue or spectacles ready at the optical desk. Each event needs its own recipient and wording rule. Surgery preparation instructions must come from approved clinical text; the messaging workflow must not invent advice or decide clinical readiness.

Bring the records the workflow depends on.

  • Patient contact preference, authorised representative details and channel permissions.
  • Validated events for booking changes, optical collection and clinician-directed queue updates.
  • Approved message wording, especially clinical preparation text, with the responsible owner.

Outputs to check

  • Message record linking the authorised event, intended recipient and delivery outcome.
  • Follow-up queue for failed or uncertain delivery that requires staff contact.

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.

Front-desk coordinator

Triggers administrative updates from the correct encounter and checks the intended patient or authorised representative.

Clinical message owner

Approves treatment-related wording and readiness instructions; communications staff do not edit clinical content to fit a template.

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.

Telephone shared by a family

Use the approved privacy rule and minimal identifying detail; do not include diagnosis or lens information merely because the number is on file.

Patient not clinically ready

A timer reaching its end is insufficient for a return-to-examination message. Wait for the authorised clinical event.

Message fails after rescheduling

Keep the new booking and failed communication visible together so staff can contact the patient through the approved alternative process.

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 queue message is sent only from the authorised clinical or coordination event configured for that workflow.
  • A delivery failure remains a follow-up task rather than being recorded as successful patient contact.
  • The saved message identifies its template version and recipient without exposing unnecessary clinical information.
Eye hospitals

How the business operates.

An outpatient eye clinic moves in stages: registration, vision and refraction, a pressure check, the doctor’s exam, then dilation and a second look once the drops have acted.

Eye clinic queue with dilation status

Track each patient through registration, optometry, the doctor and dilation, with a status that shows who is waiting for drops and who is ready to be seen again.

Optometry and examination record

Record vision, refraction, pressure, slit-lamp and fundus findings in set fields for each eye, so the doctor, the optical counter and the next visit all read the same values.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Patient, visit and eye-specific examination record
  • Queue position and clinician-directed dilation status
  • Approved surgery plan, lens model and power
  • Lens serial or lot, consignment and patient-use record

Operational bottlenecks to check

Refraction is written twice

The optometrist’s readings are copied into the doctor’s notes and again at the optical counter. Each copy invites a mistake.

Dilated patients lose their place

Patients sent for drops rejoin the queue on someone’s memory, and the token order breaks down. Nobody knows who is ready.

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. Identify the patient and visit

    Create or locate the patient record and record the visit reason. Urgent needs follow the hospital’s clinical triage process rather than booking order.

  2. 2. Record the workup and examination

    Keep optometry measurements and clinician findings against the correct eye and visit. Record any clinician-directed change in queue status.

  3. 3. Prepare an approved procedure

    Where surgery is advised, organise the approved case, consent record, theatre slot and selected lens. Staff verify identity and laterality through the hospital’s own checks.

  4. 4. Record use and charges

    Record the lens and consumables actually used. Billing applies the approved package and separately authorised charges.

  5. 5. Coordinate follow-up and optical orders

    Use dates and prescriptions recorded by the clinical team for follow-up and spectacle orders. Keep the laboratory order and collection record separate from clinical findings.

Industry reports to connect with

  • Visit and queue status by work area
  • Approved theatre list and outstanding preparation items
  • Lens stock, consignment and patient-use reconciliation
  • Optical orders and insurer balances awaiting action

Questions before implementation.

When should eye hospitals 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 Patient contact preference, authorised representative details and channel permissions.; Validated events for booking changes, optical collection and clinician-directed queue updates.; Approved message wording, especially clinical preparation text, with the responsible owner. 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 queue message is sent only from the authorised clinical or coordination event configured for that workflow. 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