iShield Solutions Series, Employee Experience · Employee Service
Unified Employee Service Center
One Front Door for Every Employee Need: HR, IT, Workplace and Finance
Unified Employee Service Center gives employees one place to ask, request and follow up, while each department keeps its own teams, approvals and confidentiality rules behind a shared intake, routing and service-level discipline.
One portal for HR, IT, facilities and finance requests with virtual agent triage.
The journey at a glance
- ReachEmployee Portal · iShield Connect
- AskVirtual Agent
- FindService Catalog
- RouteEnterprise Services
- FulfilRequest Fulfillment
- HR casePeople Services
- Coordinate journeyPeople Services
The enterprise challenge
Employees do not think in departments.
Employees must navigate separate HR, IT and facilities channels for everyday needs.
- Fragmented onboarding
- Repeated questions
- Inconsistent service
A new joiner needs a laptop, building access, a payroll set-up and policy answers in the same week, and each one usually arrives through a different portal, mailbox or phone line.
A unified service center does not merge HR, IT and facilities. It gives them one intake and one routing discipline with clear ownership behind it: conversational answers for routine questions, a catalog for requests, confidential handling for HR cases and coordinated journeys for moments such as onboarding.
Solution overview
Replace three different portals with one employee front door. People Services handles HR cases, Service Catalog covers IT and facilities, Virtual Agent on Teams/Slack triages and deflects — all with the same SLA engine.
Buyer challenges
Too many front doors
Employees guess which portal or mailbox to use, and requests arrive in the wrong queue.
Repeated questions
The same policy and how-to questions reach people because answers are hard to find.
Fragmented journeys
Onboarding and moves need tasks in several departments that nobody coordinates end to end.
Confidentiality handled inconsistently
Sensitive HR matters travel through general queues and email.
Decision owners
- Head of employee experience
- Which services join the front door, and in what order.
- HR operations
- Case categories, confidentiality rules and HR approvals.
- IT service owner
- Catalog items, fulfilment and IT approvals.
- Department service owners
- Service definitions, owners and service levels.
End-to-end enterprise journey
Many needs, one door, the right team behind it
Needs from every department enter through the same door. Step through the journey to see how a question or request is answered, routed, fulfilled and, when it is personal, handled confidentially.
- Reach · Employee Portal
- Ask · Virtual Agent
- Find · Service Catalog
- Route · Enterprise Services
- Fulfil · Request Fulfillment
- HR case · People Services
- Coordinate journey · People Services
Stage 1 of 7 Reach
Employee Portal · iShield Connect
Employees reach the service center through the employee portal and the collaboration tools they already use, surfaced by iShield Connect.
- Decision
- The employee chooses how to start: ask, browse or follow up.
- Exception path
- Unsupported channels point employees to the portal.
- Recorded as
- Session in the employee portal
This journey shows how responsibilities are intended to divide between the platforms. It describes an operating model, not a pre-built integration between them.
Who does what in this solution
Each module keeps its own responsibility. Nexus modules link to their accepted module pages; modules from other platforms link to that platform.
| Module | Platform | Responsibility in this solution | Hands on to |
|---|---|---|---|
| Virtual Agent | iShield Nexus | Answers and routes conversationally, and hands off with context. | Requests to the catalog; conversations to people |
| Service Catalog | iShield Nexus | Presents requestable services from every department. | Requests to Request Fulfillment |
| Enterprise Services | iShield Nexus | Owns service definitions and the owners behind each catalog item. | Routing rules to fulfilment teams |
| Request Fulfillment | iShield Nexus | Approves and delivers requests. Listed in the existing Nexus narrative record. | Status back to the employee |
| People Services | iShield Nexus | Handles HR cases and coordinates employee journeys. | Journey tasks to IT and workplace teams |
How the platforms work together
This is a cross-product solution. Each platform keeps its own responsibility; none of them is presented as a module of another.
Why this composition
Cross-department SLAs only work when HR, IT and facilities share one routing engine and one SLA clock. People Services + Service Catalog + Virtual Agent give that backbone; Connect surfaces it inside the tools employees already use.
Anchors the solution's operating workflow, records and governance through the modules in the journey above.
Modules included across iShield
The complete published composition of this solution.
iShield Nexus
iShield Connect
Intelligence in explicit modes
Conversational answers and agent assist handle routine questions and hand off with context.
- Assistance drafts, answers or summarizes
- Recommendation proposes for a person to accept
- Predictive anticipates or flags
- Workflow-triggered runs only as configured and approved
| AI item | What it does | Mode | Source |
|---|---|---|---|
| Intent understanding | Recognizes what the employee is asking so the conversation takes the right route. | Assistance | Virtual Agent — Intent understanding |
| AI Agent Assist | Gives the person taking over a summary and suggested next steps. | Assistance | Virtual Agent — AI Agent Assist |
| Conversational search | Suggests catalog items from the employee's own words. | Recommendation | Service Catalog — Conversational search |
| HR answers | Drafts answers to HR policy questions from approved content. | Assistance | People Services — HR answers |
| Duplicate detection | Flags overlapping service definitions before they are published. | Recommendation | Enterprise Services — Duplicate detection |
Decisions, exceptions and who owns them
HR confidentiality and approval rules apply throughout.
Publish a service to the front door
- Accountable owner
- Department service owner
- Evidence recorded
- Service definition, owner and catalog item
- Exception path
- Items without an owner are held back.
Approve a request
- Accountable owner
- Named approver
- Evidence recorded
- Request, approval and fulfilment tasks
- Exception path
- Declined requests return with the reason.
Restrict an HR case
- Accountable owner
- HR operations
- Evidence recorded
- Case category and access restriction
- Exception path
- Access changes are logged.
Hand a conversation to a person
- Accountable owner
- Employee or service team
- Evidence recorded
- Transcript and summary passed to the person
- Exception path
- Unclear intent always routes to a person.
Core capabilities
The solution's published capabilities.
One front door
Single portal across HR, IT, facilities, legal, finance.
SLA accountability
Cross-department SLAs, breach alerts, exec scorecards.
Built around recognized practice
Mappings describe how the end-to-end operating model aligns with recognized practice. They are not attestations or certifications.
The front door applies one intake, approval and fulfilment discipline across departments: the service-management practices that IT already follows are extended to HR, workplace and finance services, while confidential matters keep their own handling rules.
| Framework | Practice | How the solution operates | Relationship |
|---|---|---|---|
| ITIL 4 | Service request management and service catalogue management, adapted for enterprise service management | Every department publishes requestable services with owners and approvals, and requests follow the same fulfilment discipline.Supports practices described in ITIL 4. ITIL is guidance, not a product credential. | Aligned practice |
| ITIL 4 | Service desk and knowledge management | Conversational answers draw on approved knowledge, and hand-offs give the service desk the full context.Approved by the owner for Virtual Agent in the M5 acceptance (7 Nov 2026). | Aligned practice |
| ISO/IEC 20000-1:2018 | Service catalogue and request management, used as a reference model | Catalog items, requests and fulfilment records can serve as evidence for an organization extending its service management system beyond IT.The requirements apply to the organization's management system, not to the software. | Compliance-supporting capability |
Regulatory context
Regulations and frameworks that organizations in this domain commonly work with. Listed as context for planning, not as a certification, attestation or out-of-the-box mapping.
What changes for the organization
Outcomes are described qualitatively. Figures are published only once evidenced.
One front door
Employees start every need in the same place.
Coordinated journeys
Onboarding and moves run as one plan across departments.
Less repetitive work
Routine questions are answered from approved knowledge.
Confidentiality respected
HR matters stay with named HR roles.
What sets this solution apart
Shared discipline, separate ownership
Every department uses the same intake and fulfilment model while keeping its own teams, approvals and rules.
Answers first, people when needed
The virtual agent resolves routine questions and hands off with the full transcript when a person should take over.
Journeys, not tickets
Life events such as onboarding are coordinated as one journey with tasks across teams.
Delivery and industry context
Planning information carried over from the solution record.
30 / 60 / 90-day value plan
Days 0–30 — Foundation
Stand up the iShield workspace, integrate sources of truth, ingest baseline data.
- Tenant provisioned in chosen region (KSA / UAE / EU / US)
- SSO + RBAC mapped to enterprise identity (Entra ID / Okta)
- Top 5 integrations connected and reconciled
- Baseline KPIs measured before any change
Days 31–60 — Activation
Turn on automation, AI agents and guardrails for the priority value stream.
- Workflows live for the top 3 use cases
- Link AI agents enabled with explicit guardrails and approvals
- Power-user enablement and admin training complete
- First measurable KPI improvement vs baseline
Days 61–90 — Scale
Industrialize, roll out to additional teams, prove ROI to the steering committee.
- Solution rolled out to additional business units / geos
- Executive dashboard with target vs actual outcomes
- Continuous improvement backlog established
- Signed ROI memo and renewal / expansion plan
Personas served
Illustrative industry scenarios
Representative situations by industry. Regulations named here are context, not certifications or commitments.
Energy, Oil & Gas
Unified Employee Service Center extended to OT estates via iShield Link OT bridge.
Public Sector (KSA Vision 2030 / UAE Digital Government)
Unified Employee Service Center delivered on sovereign cloud with NCA / TDRA alignment.
Healthcare
Unified Employee Service Center with HIPAA / NPHIES-aware data flows and PHI guardrails.
