Book a Demo
Book a Demo

← Platform

Campus

Every parent told. And proof that they were.

A Pakistani school's relationship with its parents runs on messages. The fee is due. Your child was not in school today. The results are out. The bus is late.

Most schools send those from somebody's phone, or from a web panel with no record of who got what. GLOWSIMS sends them from the data itself — and keeps the receipt.

The messages a school actually sends

Not a blank box and a contact list. Each kind of message pulls its own recipients from the part of the system that knows who they are.

Fee

The highest-volume message in any school, and it comes in the varieties a school really needs: the voucher is ready, the dues are outstanding, the payment is overdue, you are now a defaulter, and we have received your payment.

Each of those exists for schools on full vouchers and for schools on monthly instalments.

Pick the fee head and the student status — and that last one matters more than it looks. Sending to withdrawn students who still owe you money is a specific job, and it is a filter rather than a workaround.

The message carries the figures from the ledger: the voucher amount, the arrears, the due date, what was paid, what is left.

Absence

Daily, monthly, or weekly. And where your school marks attendance per period, per subject.

And it will not send the same thing twice. Where a teacher corrects the attendance, or the system runs again, a parent does not get a second message for the same child, the same subject and the same day. Schools running period-by-period attendance were sending parents six and eight messages a day before this existed.

Three ways to aim it: only the parents not yet told, only the parents already told — for when a batch failed and needs resending — or everybody absent regardless.

Results

When the report cards are out, for one assessment or across a date range, restricted to particular classes where you need it.

Everything else

A general announcement to any combination of classes, departments, contact groups and individual people — or to the students on one bus route, or the students taking one subject with one teacher.

Greetings that find their own recipients: birthdays for students and staff, a welcome to a new admission, a welcome to a new member of staff, a follow-up to a new enquiry.

App credentials, for getting a parent from "your account exists" to actually logged in — which is the step where most app rollouts die.

Warning letters, as a message accompanying the formal letter so it is not missed.

And a day-end summary to the owner, for owners who want the day's collection pushed to them rather than going to look for it.

In English or in Urdu

Both, with an on-screen Urdu keyboard for composing, and a live count as you type showing how many characters you have used and how many messages it will send as — because Urdu costs more per character and a school should see that before sending, not afterwards.

Your own wording, saved

Messages are written once as templates and reused.

Each one belongs to a kind of message, so your fee defaulter wording and your fee receipt wording are different things, and each can exist in English and in Urdu with one of them set as the default.

The details come from the record

Write the wording and mark where a detail belongs. The student's name, the father's name, the fee title, the voucher amount, the balance, the due date, the class, the date, the subject, the grade, the marks, the position — each one filled in per recipient as the message goes out.

So the message a parent reads names their child and their amount, from your wording.

And it checks your wording before you send it

Type a detail marker that does not exist — a spelling slip — and you are warned, before four hundred parents receive a message with a raw tag in it.

Starter wordings are available to begin from, a template can be copied to make a variant, and marking a second one as the default demotes the first automatically rather than leaving two and letting the system pick.

Before it goes

Every send shows you the recipients first: each student with their admission number, their name, their father's name, their class, their contact number, the exact message they will receive, and what it will cost in messages.

And you can untick anybody. The parent you spoke to this morning, the family with a payment arrangement, the number you know is wrong. Reviewed, then sent.

And fix the wrong numbers on the spot

Preparing a send is when a school discovers its contact list is out of date.

So the contact book lets a number be corrected in place — click the number, type the right one, done — without leaving the screen to go and edit the admission record. Which is the difference between fixing eleven numbers and fixing none.

Who received it. Who did not. And why.

This is the part that separates this from sending messages off a phone.

Every send is one record with every recipient under it. For each one: the number, the exact message they were sent, when it was queued, when it went, whether it was sent, pending or failed — and where it failed, what the network said about it.

A parent saying they were never told is answered from the record in seconds, with the message they were sent and the time it was delivered.

And a failure can be resent individually, rather than resending to four hundred people to catch eleven.

What you have left

The gateway's remaining balance and its expiry, with today's and the total count of sent, pending and failed — so you know before a fee-reminder run whether you have the credit for it.

A school can hold more than one sending arrangement, with a different sender name, and choose which to send from.

The messages nobody sends

A lot of a school's messaging is automatic. A child is marked absent and the parent is told. A fee is received and the receipt goes out. A meeting is scheduled. A complaint is logged. An announcement is published.

And when one of those silently does not happen, every cause looks identical: nothing.

So there is a log of every automatic attempt. For any date range, by kind of event: whether it fired, was aborted, or was skipped — with the reason, in plain terms, and how many people it reached.

Fired means it went. Skipped means it ran and there was nobody to tell, which is correct on a day when nobody was absent. Aborted means something was missing — the setting was off, no default wording existed, no sending arrangement was configured — and it names which.

A school saying "parents have not had absence messages all week" used to be an afternoon of guessing. It is now one screen with the answer on it.

Messages are also marked by whether a person sent them or the system did, so the two can be told apart at a glance.

And the thing that silently kills it

The commonest reason a school's messaging stops is that the sending credentials expired and nobody knew.

So a check runs every morning and flags any arrangement expiring within thirty days — a warning at a month, more urgent inside a week, and marked critical on the last day. With the name of the one that needs renewing.

It is a small feature. It is also the difference between renewing on Tuesday and finding out on Friday that no parent has been told anything since Monday.

Who can send what

A school should not give everyone the ability to message every parent.

Sending fee messages, absence messages, result messages, announcements and greetings are each separately controlled, as are managing the contact book and correcting a student's or an employee's number.

So the accounts office can chase fees without being able to broadcast to the whole school, and the person who prepares the absence list cannot send a message to four hundred families by accident.

And the credentials are not in the school's hands

The sending arrangements themselves — the provider, the sender name, the account, the password — are set up by us rather than by the school.

That is deliberate. It means a school's messaging cannot be broken by somebody in the office changing a setting they did not understand, and the credentials are not sitting on a screen that anybody with an administrator login can read.

Before you ask

Questions schools ask

Can we send fee reminders automatically from the ledger?

Yes. The voucher is ready, the dues are outstanding, the payment is overdue, you are now a defaulter, and we have received your payment — each for schools on full vouchers and on monthly instalments. The figures come from the ledger, so the message names the parent's own amount.

Will parents get several absence messages a day if we mark attendance per period?

No. The same child, the same subject and the same day will not be sent twice, even if the teacher corrects the attendance or the system runs again.

Can we send in Urdu?

Yes, with an on-screen Urdu keyboard for composing and a live count showing how many messages the text will send as — Urdu costs more per character, and you see that before sending.

Can we save our own wording?

Yes. Templates are kept per kind of message, in English and in Urdu, with one set as the default — and you mark where each detail belongs so the message names the parent's own child and amount.

Can we check the list before it goes out?

Yes. Every send shows each recipient with their name, class, number and the exact message they will receive, and anybody can be unticked before sending.

Can we fix a wrong phone number while preparing a send?

Yes. Click the number in the contact book, type the right one, and it is corrected on the student's record — without leaving the screen.

Can we prove a parent was told?

Yes. Every send keeps each recipient's number, the exact message, when it was queued, when it went, and whether it was sent, pending or failed — with the network's own reason where it failed. A failure can be resent individually.

How do we know if automatic messages have stopped?

There is a log of every automatic attempt by date and kind of event, showing whether it fired, was skipped because there was nobody to tell, or was aborted — and when it was aborted, exactly what was missing.

What happens when our sending credentials expire?

A check runs each morning and flags any arrangement expiring within thirty days, escalating inside a week and on the final day, naming the one that needs renewing — so you find out before the messages stop.

Can we control who is allowed to message parents?

Yes, in detail. Fee messages, absence messages, result messages, announcements, greetings and the contact book are each separately controlled, so the accounts office can chase fees without being able to broadcast to the whole school.

Send a fee reminder run and watch it land

Book a demo and we will prepare a defaulter list from a real ledger, review it, send it, and show you the delivery record per parent.