Separate the school event from the external message
An attendance entry, fee receipt or notice is a school record. The message created from that record is a separate delivery task. Local storage can keep supported records available without an external connection, but it cannot reach an SMS provider or WhatsApp while offline. Explain that distinction to staff so saved does not become an informal promise that a family has been informed.
In SkoolMatic local software, supported automatic messages can be placed in a persistent outbox for relay to cloud messaging services. This is useful beyond absence alerts: the supported event categories include configured fee, payment, birthday, admission and announcement workflows. The relevant feature permissions, channel settings and event configuration still decide whether an event should create a message.
Decide which events and channels should be enabled
Ask the school owner to review each event type and the intended audience. An attendance absence, a fee reminder and a general announcement carry different urgency and context. A message should use the appropriate configured template rather than forcing every event into a generic notice. Confirm the guardian contact and the information that the template expects before using the workflow live.
SkoolMatic preserves supported announcement event types such as examination, circular, homework, holiday, transport and document-related notices through the local relay. That support does not automatically schedule a new alert for every school activity. The application workflow must create the event, and SMS or WhatsApp sending must meet the current template and channel requirements. A configurable SMS purpose is not itself an approved provider template.
Understand what happens when the connection returns
After reconnection, the local bridge retries eligible outbox work. The cloud service checks the request and current sending conditions before accepting the message. Staff should inspect the recorded outcome rather than repeatedly creating another message when the first one is waiting. A received response, an accepted delivery job and a provider delivery receipt describe different stages and should not be treated as interchangeable.
SkoolMatic uses persistent job identities and signed installation requests to help reconcile retries without creating another cloud job for the same queued message. Sending still depends on the school’s current access, balance, sender configuration and provider rules. A successful connection alone does not guarantee delivery to a handset. The school should investigate failed or blocked results through the supported status and support process.
Expire stale work instead of sending every old alert
A message that was useful yesterday may be confusing today. If the connection returns after a long outage, an old absence notice might arrive after the family has already spoken to the teacher. Agree how staff review stale work and what information needs a fresh human follow-up. Do not assume an outbox should eventually transmit every item regardless of age.
The current SkoolMatic local automatic-message flow applies a default 24-hour expiry to newly queued automatic deliveries. An expired item should be reviewed rather than assumed sent. A request already accepted by the cloud can still be reconciled after a lost response without deliberately sending a duplicate. Verify the recorded status before deciding whether a new, context-appropriate notice is necessary.
Apply the same connectivity rule to premium messaging
Premium SMS or WhatsApp changes the configured sending arrangement; it does not let the school bypass the internet. Supported automatic events still need the local-to-cloud relay, an active applicable service, valid sender setup and sufficient available credit where required. A school should not assume an inactive premium sender silently becomes a shared sender, because that changes the identity families expect.
SkoolMatic’s premium WhatsApp inbox needs an active connection to load and handle online conversations. The local interface explains when internet is required and provides the appropriate online access route. Credit top-ups, online renewals and payment verification also require connectivity. Keep these live services distinct from an automatic outbox: a pending reply in an unavailable inbox is not evidence that a background automatic message is queued.
Practise an outage with a small supervised example
Use a controlled sample rather than sending unnecessary alerts to real families. Record a supported event during a simulated outage, inspect the outbox, reconnect and review its final state. Include a blocked channel or insufficient-credit example through the approved test process. Ask the office team to explain what the status means and when it should contact support instead of manually repeating the send.
For urgent welfare or operational concerns, follow the school’s approved direct contact procedure rather than waiting for a queued message. Review recurring outages, outdated contacts and unresolved failures with the responsible administrator. The SMS versus WhatsApp guide helps schools choose the appropriate channel for each purpose. A SkoolMatic demonstration should include both shared and premium setup if the school plans to use them.
What schools should check
Stages
Distinguish recorded, queued, accepted and delivered.
Eligibility
Check current channels, templates, sender and credit.
Expiry
Review old work rather than assuming it was sent.
Premium
Keep online inbox access separate from automatic queues.
Related questions
Can WhatsApp or SMS messages leave the school while internet is unavailable?
No. Supported automatic work can wait in the local outbox, but sending through the configured cloud and provider services requires a connection. Saving the school event is separate from delivery.
Does premium WhatsApp work offline?
Premium sending still needs internet and an active applicable setup. Supported automatic messages can use the local relay queue, while the premium inbox requires connectivity for live conversations.
Will every queued message be sent after a long outage?
No. Current eligibility and message age are checked. The local automatic-message flow uses a default 24-hour expiry for newly queued deliveries, and expired or blocked work needs review rather than an assumption of successful delivery.
Explore the school software behind these workflows
Review the product workflow with your school team, then bring your current records and questions to a live demo.
Explore SkoolMatic featuresBook a Demo