This is the function where ScolaOS is weakest, so it is worth putting the gap first rather than working up to it.
ScolaOS has no bulk email composer and no bulk SMS composer. The email and SMS providers underneath are real, but they are wired to transactional messages: password resets, one-time codes, discipline alerts, export delivery. There is no screen where you write a message and send it to every parent in year 8 by SMS. We checked the codebase again on 5 August 2026 to be sure.
Several competitors state exactly that capability. If "send an SMS to all parents" is your core requirement, they meet it and we do not.
What follows is still worth reading, because reach is the wrong thing to buy on, and the rest of this comparison explains why.
Competitor pages verified 20 July 2026. ScolaOS column verified against source on 5 August 2026.
The comparison
| Capability | Fedena | Entab | Campus 365 | Vidyalaya | Classe365 | ScolaOS (code) |
|---|---|---|---|---|---|---|
| Bulk SMS to parents | STATED | STATED | STATED | STATED | STATED | No composer |
| Bulk email campaigns | STATED | STATED | NPS | STATED | NPS | No composer. Transactional email only |
| NPS | STATED | NPS | STATED, integration | NPS | Yes, the primary broadcast channel | |
| WhatsApp template management | NPS | NPS | NPS | NPS | NPS | Yes, with versioning and variables |
| Event-triggered messaging | NPS | NPS | NPS | NPS | NPS | Yes, event to template mappings |
| Delivery reporting | NPS | NPS | NPS | NPS | NPS | Yes, delivery webhooks and analytics |
| In-app notifications | STATED | STATED | STATED | STATED | STATED | Yes, with a live push |
| Notice board | NPS | NPS | NPS | NPS | NPS | Yes, drafted then explicitly published |
| Read acknowledgement | NPS | NPS | NPS | NPS | NPS | Yes, who acknowledged, not just who was sent |
| Consent requests with responses | NPS | NPS | NPS | NPS | NPS | Yes, a separate documented flow |
| Absence alert channel | SMS and push | SMS and in-app | SMS or push | Unnamed | SMS | In-app and portal only |
| Parent portal | STATED | STATED | STATED | STATED | STATED | Yes, including across several schools |
| Native mobile app | STATED | STATED | STATED | STATED | STATED | No. Installable web app |
A fairness note. Communication is one of the better-documented areas in this category, so these blanks are more meaningful than in our other comparisons, but they still are not findings. Campus 365's documentation was unreachable when checked. Vidyalaya states instant absence notifications without naming the channel, so we have not attributed one.
Delivered, opened, acknowledged
Schools buy communication software on reach and then discover the metric they actually needed was different.
Delivered means the network accepted it. Opened means an app registered a view. Acknowledged means a named parent confirmed they read it, and that confirmation is stored against them.
For a fire drill notice, delivered is fine. For a policy change, a fee revision, a trip authorisation or anything with a legal edge, delivered is worthless. The question that arrives afterwards is never "did we send it", it is "can you show me who confirmed".
ScolaOS notices carry read acknowledgement: a notice is drafted, explicitly published to a target audience, and you can see who acknowledged it rather than who was on the list. None of the five vendors states an equivalent, which we suspect is a publishing gap for at least some of them, so ask.
This is the argument for our position rather than an excuse for it. We would still rather have the SMS composer as well.
Consent is the part that matters legally
Related but distinct, and rarely present in this category.
ScolaOS has a separate consent flow: a consent request is issued, responses are recorded per parent, and the responses are retrievable as a set. Calendar events carry their own parental consent tracking for trips and activities.
The practical difference is that a consent is a question with a recorded answer, whereas a notice is a statement with an acknowledgement. Schools frequently use notices for both and discover the gap when a trip goes wrong.
No vendor in this comparison states a consent capability on its own pages. Ask each of them how a trip permission is recorded, and whether the record survives the academic year.
WhatsApp, which is where our depth actually is
If a school's parents use WhatsApp, this is the strongest channel in the product, and it is genuinely built rather than bolted on.
Template management with versioning and variables, so a message template can change without breaking what was sent before. Event-to-template mappings, so a school event triggers the right template without anyone composing anything. Delivery webhooks feeding real delivery reporting and analytics. Per-tenant usage quotas, which matter because WhatsApp business messaging is metered. And an audit log of what was sent.
Entab states WhatsApp among its channels and Vidyalaya states a WhatsApp integration. Neither publishes template versioning, event mappings or quota management, so ask what their WhatsApp support actually includes, because the range between "we can send WhatsApp" and a managed template pipeline is wide.
The app question, answered plainly
All five competitors state native mobile applications. ScolaOS does not have one. It is an installable web app: it installs to a phone home screen, works offline and behaves like an app, but it is not an App Store or Play Store download.
For communication specifically this matters more than elsewhere, because push notification behaviour and parent expectations both differ. Parents who expect to find your school in an app store will not find it. Weigh that honestly against the acknowledgement and consent capabilities above.
What ScolaOS does not do
- No bulk SMS composer and no bulk email campaigns. All five competitors state at least one.
- Absence alerts are in-app and portal only. Four of five state SMS on that path.
- Fee reminders are in-app and portal only today.
- No native mobile apps.
- No AI in communication, so no suggested wording or sentiment reporting.
- Email and SMS reach parents only through transactional flows, not campaigns you compose.
Frequently asked questions
Can ScolaOS send bulk SMS to parents?
No. There is no bulk SMS composer. The SMS providers are real but wired to transactional messages such as one-time codes. WhatsApp is the broadcast channel, with managed templates and delivery reporting. If bulk SMS is essential, several vendors in the comparison state it and we do not.
What is the difference between delivered and acknowledged?
Delivered means the network accepted the message. Acknowledged means a named parent confirmed they read it and the confirmation is stored. For anything with a deadline or a legal consequence, only the second is evidence. ScolaOS notices track acknowledgement; no competitor states it on its own pages.
How are trip permissions recorded?
In ScolaOS through a consent flow that is separate from notices: a request is issued, each parent's response is recorded, and responses are retrievable together. Calendar events carry their own consent tracking. Ask other vendors how they handle this, because most treat a notice and a consent as the same object.
Are parents notified automatically when a child is absent?
In ScolaOS, yes, automatically on every attendance mark, but as an in-app and portal notification with a live push, and only to parents with a linked account. Fedena, Entab, Campus 365 and Classe365 state SMS on this path. An SMS reaches a parent who has never opened the app; an in-app notification does not.
Does ScolaOS have a parent mobile app?
Not a native one. It is an installable web app that works offline and installs to the home screen, but it is not an app store download. All five competitors state native apps.
Which channel should a school actually use?
Match the channel to the consequence. In-app for routine information, WhatsApp where parents already are, and an acknowledged notice or a consent request for anything you may need to evidence later. The mistake is using one channel for all three.
Can one parent see children at more than one school?
In ScolaOS, yes. There is a cross-tenant parent portal, so a parent with children at two schools running the platform sees both from one account. No vendor in this comparison states an equivalent.
In summary
If your requirement is reach, and specifically bulk SMS, this is the one comparison in our series where we would point you elsewhere without much argument.
If your requirement is evidence, that a named parent acknowledged a notice or answered a consent request, that is what ScolaOS is built around, and it is the thing schools usually discover they needed after the fact.
Decide which of those two problems you have before you shortlist.
ScolaOS is a product of Terra System Labs Pvt Ltd, which is ISO 9001:2015 compliant and ISO 27001:2022 compliant.
Explore the ScolaOS platform, see published pricing, or book a walkthrough.
