Integrations
Connected to what your school already uses — through your own accounts.
SchoolOS reaches the outside world through provider interfaces, so a messaging vendor or a payment gateway can be changed by configuration rather than by rewriting a module. It also means the account is yours: your sender ID, your gateway, your bank.
- Available
- Running in production today.
- Connected at setup
- Built and metered inside SchoolOS. We connect your own vendor account during implementation.
- Planned
- On the roadmap. Not available today, and we will say so on a call.
Reaching parents
Every message is addressed from the records that hold the numbers, so a changed phone number is changed once.
Email
AvailableTransactional and bulk email from the school’s own address and domain.
SMS
Connected at setupTemplate-based SMS through the school’s gateway account, metered per school.
WhatsApp
Connected at setupTemplate messages through a WhatsApp Business account the school owns.
Mobile notifications
Connected at setupPush notifications to the parent and teacher experience on the phone.
Money
Payments reconcile against the invoice they were raised from, so collection and outstanding never disagree.
Payment gateway
Connected at setupOnline fee payment with server-created orders and signature-verified callbacks.
Tally
PlannedExport of collection and ledger data into Tally.
On campus
Hardware and location data land on the same records the office already works from.
Vehicle tracking
AvailableLive bus position on a map, per route, from the device on the vehicle.
Biometric attendance
PlannedDevice-driven attendance for staff and students.
ID card & barcode
PlannedCard printing and barcode identification for library and attendance.
Identity & platform
How your school’s own systems and domain meet SchoolOS.
Custom domain
AvailableThe application and the school website on a domain the school owns.
Google Workspace / Microsoft 365 sign-in
PlannedStaff signing in with the account the school already issues them.
API access
Connected at setupA versioned HTTP API for reading and writing school data.
Why the account is yours
Some school software resells messaging: the school buys a bundle of SMS credits from the vendor, at the vendor’s margin, and the sender ID belongs to the vendor too. When the contract ends, so does the number parents have learned to trust.
SchoolOS connects to your own gateway and your own WhatsApp Business account instead. You pay the vendor directly, the sender is your school, and nothing about your parents’ experience depends on our commercial relationship with a telecom provider.
Building against an interface
Email, SMS, WhatsApp, payments, storage and maps each sit behind a contract in the code that business logic depends on instead of depending on a vendor. Switching provider is a configuration change, and a school that already has an SMS contract keeps it.
The same design is why this page can be precise about status. An interface existing is not the same as a vendor being connected, and we distinguish the two rather than counting both as an integration.
Questions we are asked
- Does SchoolOS send WhatsApp and SMS messages to parents?
- The delivery pipeline, templates and per-school metering are built. The vendor account is your school’s own, connected during implementation, so messages are sent from your sender ID and billed to you rather than resold by us.
- Which payment gateway does SchoolOS support?
- Online fee payment is built against a provider interface: orders are created server-side and callbacks are signature-verified. Your gateway account is connected at setup, and money settles directly into the school’s bank account.
- Can SchoolOS run on our own domain?
- Yes. The application runs on a domain your school owns, with certificates issued and renewed automatically, and the school’s name, logo and colours throughout.
- Does SchoolOS integrate with Tally or biometric devices?
- Not today. Both are on the roadmap and are marked as planned on this page rather than presented as available.
Next step
Tell us what you already pay for.
If your school has an SMS contract, a gateway or a tracking vendor, bring it to the call. In most cases we connect what you have rather than replacing it.
What a demonstration involves
- Thirty to forty minutes, on a call, with your screen or ours
- Roughly how many students and staff you have
- What you use today for fees and attendance
- Whether you run one campus or several
No obligation, and no pricing pressure on the first call. If SchoolOS is the wrong fit for your school we would rather say so then.