GemuCube Solutions
Employee portal dashboard on laptop and mobile screens
Portal Development

Employee Self-Service Portal for a 500-Seat BPO Operation

A 500-seat BPO was routing every employee request — payslip retrieval, leave filing, personal data updates, IT support tickets — through email to a shared inbox. We built a self-service portal that handles 80% of these requests automatically.

AR

Adam Raymond Belda

IT Operations Director / Co-Founder

9 min read
January 22, 2025

Client

Philippines-Based BPO Operation

Industry

Business Process Outsourcing

Duration

10 weeks

Engagement

Project-Based

The Situation: A Shared Inbox Handling 400 Requests Per Month

The client's HR inbox received approximately 400 employee requests per month. Every request — regardless of complexity — went to the same place and waited for a human to read, categorize, and respond. Payslip requests took 2 business days on average. Leave applications had no standard form, so approvals required back-and-forth clarification in 30% of cases. IT support tickets arrived via email with no structured information, forcing the IT team to follow up before they could begin resolving the issue. HR was spending 60% of their time on administrative tasks that added no strategic value.

Portal Architecture We Designed

We built the portal on a structured four-module architecture. Module 1 — Payslip Access: employees could view and download their last 24 months of payslips immediately, without any HR involvement. Payslips were generated from the payroll system and stored in a secure, role-restricted document library. Module 2 — Leave Management: a structured leave application form with leave balance display, manager approval workflow, and automated notifications. Leave approvals were routed to the correct manager based on the organizational hierarchy in the HR system. Module 3 — Personal Data Management: employees could update their personal contact details, emergency contacts, and bank account information through a form that triggered an HR review workflow for any changes affecting payroll. Module 4 — IT Support: structured intake forms by issue category — hardware, software, access, network — with mandatory fields that gave the IT team everything they needed before they opened the ticket.

Security and Access Control

Every employee accessed the portal through their company Microsoft 365 account — no separate login, no password to forget. Azure AD single sign-on ensured that access was tied to employment status: when an employee's account was disabled in M365 on their last day, portal access was revoked automatically. Role-based permissions ensured managers could see their team's leave requests but not other departments. Payslip documents were encrypted at rest and accessible only through authenticated sessions — not via shareable direct links.

Rollout: From Resistance to Full Adoption in 3 Weeks

The IT team launched the portal to a pilot group of 50 employees for the first two weeks. Feedback sessions identified three usability issues — all resolved before the company-wide launch. The full 500-seat rollout happened over a single Friday afternoon. By the following Monday, 78% of employees had successfully logged in and completed at least one self-service action. By the end of week 3, the HR inbox volume had dropped from 400 to 68 requests per month.

The Results

HR inbox volume reduction

400 → 68 requests/month (83% reduction)

Payslip retrieval time

From 2 business days to instant

Leave approval cycle

Reduced from 3 days to 4 hours average

IT ticket resolution time

Reduced 40% due to structured intake

Portal adoption rate

94% of staff active within 30 days

Technology Stack

Microsoft 365Azure AD / Entra IDSharePoint OnlinePower AutomateZoho DeskMicrosoft Intune
employee portal self-service portal BPO systems portal development Philippines HR portal

Start a Similar Project

Ready to build this
for your business?

Schedule a discovery call and we will map exactly what we would build for your specific situation — no generic proposals.