Skip to main content

Service Management use case

Employee self-service portal software

An employee self-service portal gives staff one place to ask HR, IT and facilities for anything and one list of everything they have open. Behind it, each request runs in the team's own system, whether that is Workday, ServiceNow or a facilities tool. Fairfax County Public Schools uses this model across 200+ schools and offices.

Fairfax County Public Schools One service portal for staff across 200+ schools and offices, in front of its existing BMC Remedy system.

One portal, every department's systems behind it

  1. Experience layer

    One portal for HR, IT and facilities requests, organized by what the employee is trying to do, with every open request and its status on a single page.

  2. Workflow layer

    Each request routes to the owning team, runs across that team's systems with the approvals it needs, and escalates when it misses its target.

  3. Integration layer

    Reads the employee's manager, cost center and location from Workday and Entra ID, and sends each request to the owning team's system: an HR case, a ServiceNow or BMC ticket, or a facilities job.

    • Workday
    • SAP SuccessFactors
    • ServiceNow
    • BMC Helix
    • Microsoft Entra ID

AI in employee self-service portal

AI answers status questions and points people to the right service. It doesn't change pay, benefits or employee records; those changes are approved by HR.

What AI does

  • Answers status questions from live request data
  • Matches a plain-language question to the right service
  • Drafts case notes for HR and IT agents

Decided by people, not by AI

  • Changes to pay, benefits or employee records
  • Access and equipment requests
  • Policy exceptions

Six portals and a phone number

Ask a new employee how to get a standing desk and watch them guess. Facilities? IT, because it has a monitor arm? Procurement? Each team has its own portal, its own login and its own idea of what belongs there. When the guess is wrong, the request bounces, and the employee calls someone.

HR and IT service desks see this every day. A real share of their contacts aren’t problems at all. They are “where do I go for this?” and “I asked two weeks ago, what happened?” Both questions exist only because the work is split across systems the employee can’t see into.

Organized around the employee

The Kinetic portal is arranged by what people are trying to do, not by which department owns the system: I’m new, I’m moving desks, something’s broken, I need access. Search accepts plain language, so “my badge stopped working” lands on the right form.

Forms know who’s asking. Manager, cost center, location and current entitlements come from Workday and Entra ID, so the employee only answers questions that matter. A teacher at one school sees different services than an administrator at the district office.

Then the request goes where the work actually happens. A desk move might create a facilities job, update badge access for the new floor, and open an IT task to move the phone, each with its own approval if needed. The employee sees one request with one status. Every open request, across every team, is on one page.

What changes for HR and IT

The teams keep their tools. HR case workers still work in their HR system; the IT desk still works in ServiceNow or BMC. What they lose is the status-chasing. When people can see where their request stands, they stop calling to ask.

Fairfax County Public Schools replaced a mix of phone calls, paper forms and email across more than 200 schools and facilities with one portal in front of its existing BMC Remedy system. Staff at every school now use the same interface, and the district cut fulfillment time in half. Read the FCPS case study.

Where to start

Start with one department’s ten most common requests and the systems behind them, then add the next department’s. The portal grows by adding services, not by rebuilding. HR request management and facilities management are the usual second and third.

What you can build next

Most portals add one department at a time, reusing the sign-in, the request page and the connections already built.

Questions about employee self-service portal

Answered by Kinetic Data. Last updated .

  • Can employees make requests from Microsoft Teams or Slack?

    Not out of the box. Kinetic is headless, so customers bring the portal's services into Teams, Slack or another chat tool by building a small plugin against the Kinetic API, or through an MCP-capable assistant. Requests made that way run through the same workflows as the portal.

  • How is this different from the portal in Workday or ServiceNow?

    Those portals are good at what their own system fulfills. Kinetic's portal sits above them, so one request can update Workday, open a ServiceNow task and book a facilities job, and the employee still sees a single status.

  • How do employees sign in?

    Through your existing single sign-on, using SAML or OIDC with Entra ID, Okta or a similar provider. Government customers can also use CAC or PIV cards.

  • Can services differ by location?

    Yes. What appears in the portal, which fields a form shows and who approves can all depend on the employee's location, role and department, read from your HR system. Everyone still has one place to look.

Bring one process. Leave with a plan to build it.

Two hours with our team, at no cost. Bring one process that crosses your systems. We map it with you, show what Kinetic would build, and send you a written plan afterward.