Skip to main content
GullySystem
Wellness

WhatsApp, SMS and Email Notifications for Nutritionists and dietitians

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.

Clients get their chart by message with a water and meal reminder schedule. Alerts reach the dietitian when a client replies with a weight or a photo. Missed check-ins prompt a gentle note.

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.
Nutritionists and dietitians

How the business operates.

Clients come for weight loss, PCOS, thyroid, diabetes, pregnancy or sports nutrition, on a one, three or six-month package. The plan changes weekly and each change must be recorded. Most of the work happens between consultations.

Client intake and health history

Keep goals, conditions, food preferences, the diet recall and uploaded lab reports on one profile, open to you and to the associate you assign.

Diet chart builder

Build charts from your own meal templates by condition and preference, then send them out as a branded PDF.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client intake and history. Capture goals, diagnoses, medicines, allergies, food preferences, the twenty-four hour diet recall and uploaded lab reports on one profile. The assigned dietitian and any associate open the same file.
  • Consultation notes. Write each session as a dated note with the complaint, the findings and the changes agreed. Earlier notes stay in order, so the next call starts from what was said last time.
  • Diet chart builder. Assemble a chart from your own meal templates grouped by condition, cuisine and calorie band, then adjust portions for the client. Each revision is saved and the latest goes out as a branded PDF.
  • Food and portion library. Hold the foods, household measures and swaps you use most, with the nutrient values from the source you are licensed to use. Charts pull from this list, so a swap is written once.

Operational bottlenecks to check

Follow-ups are missed

A client stops sending their weight, and two weeks pass. You notice when the client asks for a refund, and by then the chart has been dropped.

Diet charts are rewritten from scratch

Every chart begins on a blank page, although half repeats what you wrote last week for another client with the same TSH report.

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 intake

    A new client arrives from a referral, a website form or a message. Goals, conditions, medicines, allergies and food habits are filled in, and a first consultation is booked.

  2. 2. Assessment

    The dietitian records height, weight, waist, blood pressure and the diet recall, and attaches any lab reports. Findings and the agreed goal are written as the first note.

  3. 3. Plan and chart

    A chart is built from saved meal templates and the household measures the client uses. Portions are adjusted, and the finished chart goes out as a PDF.

  4. 4. Follow-up review

    Weight, measurements and meal photos come in each week. The dietitian logs the reading, notes the plateau or the loss and revises the chart when needed.

  5. 5. Follow-up and sessions

    Late check-ins are listed by days of silence. Review calls and clinic visits are booked, and each ends with a note and the next date.

  6. 6. Renewal or closure

    Before the package ends, the client’s progress is shown beside a renewal offer. A client who finishes is closed with a summary of what changed.

Industry reports to connect with

  • Active clients by dietitian, goal and package type
  • Clients overdue for a weekly check-in, by days of silence
  • Weight and waist change by client over the length of the package
  • Charts issued and revised, by dietitian and condition

Questions before implementation.

When should nutritionists and dietitians 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