Attendance closes 8:30am
Form 1A needs review
Two exceptions need office confirmation before the morning summary is published.
Built for Ghana - West Africa
Run the school day before it runs you.
Sunrise SMS gives Ghanaian schools a branded operating system for admissions, attendance, fees, report cards, parent updates, and the daily office work that decides whether a term feels calm or chaotic.
✓Built for Ghanaian school workflows
✓Hands-on rollout, not just software
✓Branded portals families can trust
akoma-school.sunrisesms.app
Good morning, Headmistress Ofori
Akoma International School - Term 2, Week 6
Bursar follow-up
12 arrears notes
Send polite reminders after review.
Parent portal
Branded
Report cards
P4 drafting
Receipts
Ready to reconcile
Today's focus
Approve attendance exceptions, review fee reminders, and publish the parent announcement before closing.
A rollout partner for the first term
Sunrise should feel like guided implementation: configure the school, clean the data, train the team, then open the portals.
Designed for the school owner and the front desk
The interface keeps strategic oversight and everyday admin work close together, so leadership and operations see the same truth.
Premium enough for the brand parents see
A school-branded parent experience matters. Sunrise should not feel like a cheap tool pasted onto a serious institution.
Features
Built around the work that makes or breaks a school term.
Sunrise SMS is designed for the people behind the counter, in the classroom, at the bursar desk, and at home checking the parent portal.
A clean school office from day one
Admissions, students, guardians, staff, classes, contacts, and documents are set up around how schools actually run.
Attendance before the first period disappears
Teachers get quick class lists, attendance states, notes, and the school office gets a daily view without chasing paper.
Fees, arrears, and receipts in one trail
Bursars can follow invoices, receipts, balances, payment plans, arrears review, and reconciliation without spreadsheet drift.
Parent portals that feel like the school
Families see the school brand, balances, messages, report cards, attendance updates, and the information meant for them.
Communication tied to real school events
Announcements, attendance alerts, fee reminders, and report-card notices come from the same records teams already use.
Controls for growing school groups
Plans, modules, custom domains, entitlements, audit trails, scoped API access, and tenant-separated data stay manageable.
Use cases
One system, different jobs, clear handoffs.
Sunrise should not make every role look at the same dashboard. The public story now mirrors how the actual product is split across school leadership, office teams, teachers, parents, and students.
School owners and heads
Know what is blocking the school day.
See attendance gaps, fee follow-up, report-card readiness, parent notices, and operational queues without asking every office for updates.
Daily command centerRole-aware dashboardsAudit-ready records
Front desk and bursar teams
Turn repeated office work into one reliable trail.
Admissions, guardian records, invoices, receipts, arrears notes, and announcements stay connected to the student and the term.
Student and guardian CRMFinance workflowsCommunication history
Teachers, parents, and students
Give each role the view they actually need.
Teachers handle attendance and grades, parents check balances and reports, and students see classes, grades, messages, and report cards.
Teacher portalParent portalStudent portal
How it works
Set up once. Run the week with confidence.
The interface should make ownership clear: who acts, what data is involved, and what gets recorded for review.
1
Map the school as it really works
Configure terms, houses, classes, roles, fee items, grading rules, branding, and the modules the school actually uses.
2
Clean the data before launch
Import students, guardians, staff, classes, subjects, opening balances, and records with ownership clearly assigned.
3
Run the week from one desk
Handle attendance, fee follow-up, receipts, grading, report cards, announcements, and portal access without duplicate work.
API and data
Built for schools that need controlled integrations.
API access is treated as an entitlement, not an open promise. Schools can connect approved workflows while Sunrise keeps tenant boundaries, role access, and audit trails clear.
POST /v1/school/events
{
"type": "attendance.exception_reviewed",
"student": "tenant-scoped-record",
"notify": ["guardian", "school-office"]
}
✓
Scoped API access for entitled schools
✓
Tenant-aware records for students, guardians, attendance, finance, and communications
✓
Audit logs, exports, and protected access patterns for operational review
✓
Custom domain and branded portal setup when the school plan supports it
Pricing
Choose a plan after school size, modules, and support needs are clear.
Public pricing is not listed until real plans and limits are approved. Plan details should reflect school size, enabled modules, support level, branding, custom domain, and API requirements.
FAQ
Clear answers before the first rollout.
No fake client logos, no invented delivery rates, and no unapproved public pricing.
Is Sunrise SMS a bulk SMS tool or a school system?+-
It is positioned here as a school management system. Messaging is part of the communication module, not the whole product.
Can each school use its own branding?+-
Branding and custom domains are plan-gated capabilities. The product should only promise them where the plan supports them.
Does it support parent and teacher access?+-
Yes. The product includes role-aware portals for parents, teachers, students, and staff.
Is pricing public?+-
No approved public pricing is listed yet. Plans should depend on school size, modules, support, branding, and API needs.
Walkthrough brief
Start with the school's real operating model.
A useful Sunrise walkthrough should map the school before showing screens. Use this brief to align leadership, office, academic, finance, and parent-portal needs before a rollout decision.
What the walkthrough should cover
- ✓School size, campuses, terms, houses, classes, and staff roles
- ✓Modules needed for launch: attendance, fees, report cards, portals, communications, and optional services
- ✓Data import readiness: students, guardians, staff, opening balances, and existing records
- ✓Branding, parent portal, custom domain, support, and API requirements