Skip to main content
GullySystem
Healthcare

WhatsApp, SMS and Email Notifications for Diagnostic centres

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 are told their report is ready and sent the preparation rules before a fasting scan. Referring doctors receive a link once signed. Delays on a busy machine reach those booked that day.

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.
Diagnostic centres

How the business operates.

A centre with an X-ray room, two ultrasound rooms and a CT scanner handles walk-ins, booked scans, hospital referrals and health check packages through one front desk. That desk is the bottleneck.

Slot booking by machine and room

Book ultrasound, X-ray, CT and MRI slots against the room that does them, and send the preparation a scan needs with the booking.

Study status from scan to dispatch

Follow each study through booked, scanned, in draft, signed and delivered, with views by room and radiologist.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Patient registration and visits. Register each patient once, found by phone number or ID, with every visit, prescription, referrer and report on the same record.
  • Slot booking by machine. Book ultrasound, X-ray, CT, MRI and other rooms by slot. The preparation each scan needs is printed or sent at booking, so fasting and test values are asked for in advance.
  • Rate lists and health packages. Keep separate rate lists for walk-ins, hospitals, corporates and camps. Group scans and tests into health check packages.
  • Billing, dues and refunds. Bill each visit from the right rate list, take part payments, record every discount with the person who approved it, and refund a cancelled scan with the reason written down.

Operational bottlenecks to check

Every machine keeps its own diary

Ultrasound uses a register, CT uses a sheet, and the desk cannot see either while a caller waits on the line. Double bookings follow.

Preparation is missed

A patient arrives for an abdomen scan after breakfast, or for a contrast study without a recent creatinine value. The slot is lost.

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. Booking

    A patient or a referring doctor books by phone, on WhatsApp or at the desk. The slot goes on a machine and room, and the preparation instructions go with it.

  2. 2. Registration and billing

    The desk registers the patient, notes the referrer and the prescription, and bills from the rate list that applies. Cash, bank transfer, card or a credit account settles the visit.

  3. 3. Scan

    The technician sees the room’s worklist, checks preparation and consent, and marks the study scanned. Images go to the centre’s PACS or viewer.

  4. 4. Reporting

    The radiologist opens the study, writes findings from a template and signs. A critical finding is flagged so the referring doctor gets a call.

  5. 5. Delivery

    Signed reports are printed with films or a CD, or sent as a PDF. Messages go through the centre’s own WhatsApp Business account where that is set up.

  6. 6. Month end

    Credit visits roll into statements for each hospital and corporate. The owner sees studies by machine, modality and referrer.

Industry reports to connect with

  • Studies by modality, machine and day
  • Reports awaiting sign-off, by radiologist
  • Visits by referring doctor and hospital
  • Credit dues by hospital and corporate

Questions before implementation.

When should diagnostic centres 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