Skip to main content
GullySystem
Wellness

WhatsApp, SMS and Email Notifications for Yoga studios

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.

Students receive a class reminder, a waitlist offer and a note when a pass is about to run out. Teachers hear about cancelled batches. A substitute teacher notice goes to the booked mats.

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.
Yoga studios

How the business operates.

Most studios start with a printed timetable and a notebook. That works for one room and one teacher. It fails once passes expire in different weeks and three teachers cover seven batches, because nobody can say who is owed classes or what each teacher has earned.

Class schedule and batches

Lay out the weekly timetable by room, teacher and style, with batch size, a substitute teacher and a cancelled session recorded on the same grid. A change reaches the students booked.

Booking and waitlist

Students reserve a mat for a batch. A full class opens a queue, and the first name in it is offered a freed place by message. The rest wait their turn.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Class schedule and batches. Set the weekly timetable by style, hall, teacher and batch time. Changes show at once. Substitutions and public holidays reach every student the moment the desk saves them.
  • Student records. Keep contact details, goals, injury and pregnancy notes, plan history and attendance for every student. The teacher reads the notes before class and adapts the poses for a sore knee or a stiff back.
  • Booking and waitlist. Students reserve a mat in a class, and a full batch holds a waitlist. Cancellation closes before the class starts, and the freed mat passes to the next name in line without a call from the desk.
  • Attendance and check-in. Mark who came from the teacher’s phone, a desk list or a scanned QR code. The session is counted against the pass or the membership. The dated register stays on record for every class, so an absent student is never charged.

Operational bottlenecks to check

Pass balances are not written against the student

A student claims four classes left, the desk thinks two. Without a count that falls at each check-in, the argument is settled by whoever is more polite on the day.

A full room has no waiting list

Eight mats are booked, a ninth student arrives, and cancellations come in too late to use. Nobody is called from a queue, so the freed mat stays empty.

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 trial

    An enquiry arrives by phone, WhatsApp or the website. Front-desk staff book a trial class and note the student’s goals, any back or knee injury and any pregnancy, so the teacher is prepared.

  2. 2. Joining

    The student picks a monthly membership, a ten-class pass or a drop-in. The payment is recorded, and the plan starts on the date chosen, not the day it was paid. Then the first class is booked.

  3. 3. Booking

    The student reserves a mat in a batch. A full class opens a waitlist. A cancelled mat goes to the next name.

  4. 4. Class

    The teacher opens the class on a phone and marks who is on a mat. One session comes off the pass, or the day counts against the membership, before savasana ends. The register is dated and timed.

  5. 5. Month end

    Classes taught by each teacher meet the rate agreed for them. Substitutions and covered batches are counted to whoever took the room, and the month’s payout is ready for the owner to approve.

  6. 6. Renewal

    Students whose plan is ending are listed a week ahead. A reminder goes through WhatsApp, text message or email. The renewal is recorded when payment is taken, so the plan carries on without a gap.

Industry reports to connect with

  • Attendance by class, batch, hall and teacher
  • Active memberships and ten-class passes with sessions left
  • Renewals due, frozen plans and lapsed students
  • Collections by plan, intensive, teacher training and retail

Questions before implementation.

When should yoga studios 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