Skip to main content
GullySystem
Healthcare

WhatsApp, SMS and Email Notifications for Diabetes 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 a note about tomorrow’s fasting sample, their next review date and the diet sheet from the dietitian. A reminder to bring the meter goes out the day before. Clinic holidays reach all booked patients.

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.
Diabetes clinics

How the business operates.

A diabetes clinic lives on follow-up. Patients return every few months with a glucose diary, a fresh HbA1c result and questions about a changed dose. The doctor needs the earlier readings beside the new ones.

Registry by diabetes type and duration

Hold type, year of diagnosis, treatment group, co-existing conditions and the treating doctor for every patient, so a list can be pulled at once.

Glucose diary and HbA1c trend

Enter fasting, post-meal and meter readings beside each HbA1c result, with the trend drawn across visits for the doctor to read.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Diabetes patient registry. Hold diabetes type, year of diagnosis, treatment group, co-existing conditions and treating doctor, with filters that pull any group on demand.
  • Glucose diary and meter readings. Enter fasting, post-meal and bedtime values from the diary or a meter file, and prompt patients to send their readings before a review.
  • HbA1c and laboratory trends. Chart HbA1c, lipid and kidney results across visits, with the laboratory’s report attached to each value.
  • Medicine and insulin history. Record every tablet and insulin change with device, units, date and reason, so the order of adjustments can be read on the next visit.

Operational bottlenecks to check

Readings are spread over diaries and slips

A patient hands over a diary, a meter and three lab slips. The trend has to be pieced together by eye during a short consultation.

Annual complication checks are missed

Foot examination, retinal screening, urine albumin and lipid tests each fall due on a different date. Nobody holds a list. Overdue patients are found only when a complication appears.

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

    The desk opens a record with the diabetes type, year of diagnosis, contact details and the doctor, and imports earlier results if the patient has them.

  2. 2. Tests and measurements

    Samples go to the laboratory, and a nurse records weight, blood pressure and meter readings on the visit.

  3. 3. Review

    The doctor reads the HbA1c trend and diary, changes the regimen if needed, and sets the next review date and the next screening items.

  4. 4. Education

    An educator or dietitian logs a session on injections, meal planning or hypoglycaemia care, with the next session booked.

  5. 5. Referral and screening

    Letters to eye, kidney and foot specialists are tracked until the report returns. Yearly checks are marked done against the patient.

  6. 6. Recall and billing

    Overdue patients are listed for calls. Consultations, tests, packages and counter supplies are billed against the same record.

Industry reports to connect with

  • Patients overdue for HbA1c
  • Foot, eye and urine albumin checks due
  • Referral letters without a returned report
  • Insulin and tablet changes by patient

Questions before implementation.

When should diabetes 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