What Schoolyi connects to, and what it does not

Not available. SMS sending is a provider interface with no provider implementation, so SMS notifications are not delivered.

What happens instead: Email covers every notification path today, including fee reminders and absence alerts. Where a message needs to reach a parent by phone, the fee follow-up view builds a WhatsApp deep link that opens a pre-filled message from the staff member’s own device — a manual send, not automated delivery. If automated SMS is a firm requirement, say so during evaluation rather than assuming a provider can be dropped in.

Not available. Schoolyi builds WhatsApp deep links a staff member sends manually; it does not send through the WhatsApp Business API.

What happens instead: Fee follow-up and parent contact views generate a wa.me link with the message pre-filled, so the send is one tap for a staff member and is attributable to a person rather than a system. That is genuinely useful for defaulter follow-up and genuinely not automation. Templated bulk sending through the WhatsApp Business API does not exist.

Not available. There is no Google OAuth sign-in, no Classroom roster sync, and no Google Calendar API integration.

What happens instead: Staff sign in with credentials; parents and students can use magic-link sign-in by email, which removes the password without requiring an identity provider. Exam schedules are available as a standard ICS feed any Google Calendar can subscribe to. If Google sign-in for staff is a procurement requirement, treat it as absent rather than planned.

Not available. There is no Entra ID or Azure AD single sign-on, no Teams integration, and no Microsoft Graph connection.

What happens instead: Sign-in is credentials with magic-link as an option for families. Microsoft 365 email works as the SMTP provider for all transactional mail, which is the one place the two products do meet. Single sign-on against Entra ID does not exist, and a school with a mandatory SSO policy should weigh that heavily.

Not available. There is no ledger posting into accounting software, and no scheduled sync of financial data.

What happens instead: Fee collection, receipts, refunds, and payroll are held in Schoolyi with Excel and CSV export, and payroll produces Indian statutory formats for PF, TDS, and professional tax. Moving those figures into your accounting system is a file handoff your finance team performs, not an automatic posting. If your auditor expects automated journal entries, plan for that gap explicitly.

Not available. No biometric or attendance hardware integration exists.

What happens instead: Attendance is marked in the application against registers generated from the timetable, and the academic calendar defines which days count. Where a school already runs biometric hardware, the realistic path is a file import rather than a live device connection, and it is worth scoping that before assuming it.

Not available. Schoolyi installs as a progressive web app with an offline shell, but does not send push notifications.

What happens instead: Notifications appear in the application and, where configured, by email. The app is installable to a home screen and works offline for the shell, which covers the "feels like an app" requirement but not the "buzzes the phone" one. If push is essential to your communication plan, count it as missing.

Not available. There is no API key or OAuth client model for an external system to integrate against.

What happens instead: The application API is authenticated by session and documented in an OpenAPI specification, which makes it readable but not a third-party integration surface. Programmatic data movement today means CSV and Excel import and export. If a partner vendor needs to integrate on a timer, treat that as a requirement to raise rather than an assumption to make.