The channel ladder of official WhatsApp, Telegram, and its backups — plus the limits that keep Klasku messages one-way.
Down a channel ladder, tried in order per message. The first rung is official WhatsApp (WABA), used when your school switches it on and the message type has a matching template. Otherwise the message drops to Telegram — free, as long as the recipient has linked the Klasku bot. Below that sits SMS, which only runs when a school opens it with our team; that channel is currently off.
The ones about money and schedules: an invoice issued, a due-date reminder, confirmation that a payment arrived, a canceled session, the outcome of an excused-absence request, a booked make-up class, an offer of a free seat, a published report card, and the link to an online class on the morning of the session.
No. The official WhatsApp route is provided by Klasku and switched on per school; using it draws on the school's Notification Credit balance, counted when a message actually arrives. A school that has not switched it on can still send every message type — the route simply drops to Telegram.
Telegram only becomes usable once the recipient has linked the Klasku bot through a one-time linking link. Before that, the message drops to the next rung: SMS, if the school has opened it with our team.
Yes. A failed message is retried a few times with widening gaps before it is finally marked failed. All sending runs through a background queue rather than inside a staff member's click, so no screen ever hangs waiting on a channel.
Yes. Bulk announcements go over Telegram to recipients who have linked the bot, and each recipient draws one broadcast credit from the school's balance. Announcements never travel the official WhatsApp route: their category is marketing, and that route is not the place for it.
Yes. The Parents Portal and the Teachers Portal can be added to a phone's home screen and send push notifications — a COMPLEMENTARY channel that mirrors the first delivery attempt, not a replacement for the message itself.
Yes. Reminders are scheduled as day offsets around the due date, and the school sets the list itself — by default seven days before, three days before, on the due date, three days after, and seven days after.
Yes, per message type, from the school's settings. A switched-off type is still recorded in the history as skipped, with a note saying who switched it off, rather than vanishing — so an admin never mistakes it for a failure.
Partly. Bulk announcements are written by you, word for word. Automatic messages — invoices, reminders, payment confirmations, schedule changes — use fixed forms that insert your school's data: student name, class, amount, and dates.
Yes. The school's message history records every message with its recipient, its type, the channel actually used, and its state. Failed messages state their reason, so the list doubles as a work list.
They do. The only quota that can run out is bulk announcements — each recipient draws one broadcast credit, and when that balance is empty the send is refused with the reason stated. Transactional messages such as invoices, reminders, and payment confirmations never stop with it.
Once, through a linking link that opens the Klasku bot and identifies the recipient immediately. The prompt appears by itself in the Parents Portal and the Teachers Portal, and an admin can copy someone's link from the tenant panel to send by hand.