Skip to main content
GullySystem
Education

WhatsApp, SMS and Email Notifications for Martial arts schools

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.

Parents get a message the evening before a grading with the time, the forms to bring and the fee due. Cancelled classes on a tournament weekend go to the right age group. Reminders stop once the fee is paid.

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.
Martial arts schools

How the business operates.

A martial arts school teaches karate, taekwondo, judo, kung fu or a mix. Whatever the style, a student moves through coloured belts or numbered grades, and each step needs a syllabus passed in front of an examiner.

Student ranks and belt history

Keep each student’s current belt, every earlier grade with its date and examiner, and the next grade they are working toward, so a transfer carries the whole story.

Class timetable and rosters

Set classes by age, rank and instructor, with a roll for each session and a quick sign-in for children’s classes.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Student ranks and belt history. Keep the current belt, every earlier grade with its date and examiner, and the next grade the student is working toward.
  • Class timetable and rosters. Set classes by age, rank, mat and instructor, take a roll for every session, and let a guardian sign a child in.
  • Syllabus sign-off. List the forms, techniques and sparring drills required for each belt, and mark each one when the instructor has seen it performed.
  • Grading eligibility and results. Check classes attended, forms signed off and fees paid before a student is listed, then record the pass, score and new belt.

Operational bottlenecks to check

Grading eligibility is decided from memory

The instructor recalls from memory who attends and who does not, so someone with too few classes gets put forward while a student who is truly ready is missed.

Belt history is kept in several places

The belt certificate, the register and the instructor’s notebook each hold a different date. Moving to another branch means repeating the story.

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. Trial and joining

    An enquiry becomes a trial class on a set mat. Joining brings a record, a waiver to sign and a fee plan.

  2. 2. Class and roll

    The student is placed in a class by age and rank. The instructor takes the roll, and children are signed in by a guardian.

  3. 3. Syllabus progress

    Forms and techniques are signed off against the next belt as the instructor sees them performed.

  4. 4. Grading

    The grading list is drawn from classes attended, forms signed off and the grading fee paid. The examiner records the result and the new belt.

  5. 5. Fees and sales

    Monthly fees, family plans, grading fees and uniform purchases are billed, and receipts are issued.

  6. 6. Events and instructor pay

    Students are entered in tournaments by licence and class. Instructors are paid from the classes taught.

Industry reports to connect with

  • Students ready for grading by belt
  • Attendance by class, instructor and month
  • Waivers missing or due for renewal
  • Fees due by family and month

Questions before implementation.

When should martial arts schools 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