Higher-education institution · UAE
Student services and administration portal
Representative product engineering programs delivered by Zestlan. Client names withheld where confidentiality agreements require. Metrics reflect documented outcomes from production deployments.
Context
Students submitted service requests through email and walk-in counters. Staff tracked requests in spreadsheets.
IT operated four separate applications without unified identity — students repeated logins between tools.
Challenge
Students and staff used disconnected tools for admissions, scheduling, and service requests, creating delays and poor visibility.
Solution
A unified web portal for student services, document workflows, notifications, and administrative reporting with role-based access.
Constraints
- SSO across legacy applications without rewriting all backends in phase one
- Document workflows with approval chains for transcripts, appeals, and administrative requests
- Peak load during registration periods
Architecture
Portal as experience layer — SSO gateway, unified request model, and notification fabric over existing admin systems.
Student portal shell
Single entry for services, status tracking, and document submission.
SSO & identity bridge
SAML/OIDC integration linking four legacy apps under one session.
Service request engine
Typed request workflows with SLA tracking and staff assignment queues.
Notification service
Email and in-app updates tied to request state changes.
Technology stack
Delivery approach
Prioritized self-service candidates by volume and automation feasibility.
Unified login across four apps — immediate student experience win.
Built top five request types with staff queues and SLAs.
Expanded self-service catalog; tuned for registration peak load.
Measured outcomes
- 60% of routine student requests handled through self-service workflows
- Average service response time reduced by 9 business days
- Single sign-on adopted across 4 previously separate applications
Engineering lessons
- SSO delivered visible value before all workflows were migrated — important for adoption momentum.
- Self-service only works when status transparency is real — opaque queues erode trust quickly.
- Staff queues needed the same SLA visibility as leadership dashboards to prevent silent backlog growth.
Discuss your product program
Every engagement is scoped to your business model, users, and constraints — detailed reference material available under NDA for qualified evaluations.