nábd Care · employee services

Employee services, end to end.

The HR service delivery and employee experience layer for SuccessFactors customers. HR cases routed and resolved. Assets assigned, tracked, returned. Onboarding and offboarding orchestrated across HR, IT, and facilities — all connected to your SF tenant.

Who nábd Care is for

HR teams who answer questions, manage assets, and orchestrate joiners and leavers.

You are running SuccessFactors. Your HR team handles a constant flow of employee queries — leave balances, payslips, document requests, policy questions. Your operation tracks assets across employees — laptops, phones, access cards, software licences. Joiners and leavers cross HR, IT, and facilities every time.

Today, you do this with email, spreadsheets, or a heavyweight ticketing system that doesn't know your HR data. nábd Care is the alternative — built around your SuccessFactors tenant.

The product

One employee. One year. One operational fabric.

Service desk, asset lifecycle, joiners and leavers — handled on one surface. The work HR teams do every day, sitting on top of your SuccessFactors tenant of record.

care.nabd.app
nábd Care · My Onboarding view — probation progress, training milestones, and tasks for a new joiner.

Onboarding

care.nabd.app
nábd Care · Inbox with active ticket conversation and SLA tracker.

Inbox

care.nabd.app
nábd Care · Course chapter view from the internal Raptors 101 curriculum.

Learning

Captured from production at 1440 × 900. No mock data.

Capabilities

Service desk, assets, joiners and leavers.

HR service delivery

Cases routed, tracked, and resolved.

A ticketing surface for HR — connected to your tenant, governed by SLA.

  • Employee case management

    Tickets raised by employees, routed to the right HR team, tracked to resolution against an SLA.

  • HR knowledge base

    Self-service answers to common queries — policy lookups, leave rules, document procedures.

  • Approval workflows

    Document requests, certificate generation, signature routing — captured and signed off.

  • Performance metrics

    Case volumes, resolution times, satisfaction — visible to HR leadership.

Asset lifecycle

Assigned. Tracked. Returned.

Every laptop, phone, access card, and software licence accounted for across tenure.

  • Asset register

    Every asset assigned to employees, tracked through tenure with cost visibility.

  • Assignment workflows

    Issuance routed at hire and on transfer. Approvals captured. Acceptance signed off.

  • Return at exit

    Offboarding triggers reclamation. No assets unaccounted for at termination.

  • Cost visibility

    Per-employee cost of equipment and licences — feeding total compensation and finance reporting.

Onboarding & offboarding

Joiners and leavers, orchestrated.

The complete journey across HR, IT, facilities, and managers — gated and signed off.

  • End-to-end orchestration

    Offer-acceptance to day-one productivity — across every team that owns a step.

  • Task choreography

    Each role's actions sequenced, dependencies enforced, deadlines tracked.

  • Day-one readiness

    All assets issued, accesses provisioned, paperwork signed before the new hire arrives.

  • Offboarding completion

    Knowledge transfer, asset reclamation, access revocation, paperwork — all gated and signed off.

Architecture

Reads lifecycle events from Core.

Care reads employee data, organisational structure, and lifecycle events from nábd Core — the shared data layer underneath the suite. Core syncs in real time from your Employee Central tenant and other authoritative sources.

A new hire entered in EC propagates into Core within minutes; Care reads that signal and triggers its onboarding orchestration. A transfer routes to Care's asset reassignment workflow. A termination closes case management and triggers offboarding. SuccessFactors stays the single source of truth; Care extends the operational layer on top of it.

See how Core works

Choosing the right fit

SF Onboarding and nábd Care solve different problems.

Both are right answers — for different shapes of operation. Here is how to choose.

SAP SuccessFactors Onboarding

SAP standard

SuccessFactors customers whose onboarding scope is HR data capture and pre-hire paperwork.

  • Onboarding centred on HR-owned tasks and documentation
  • Asset management handled outside of SuccessFactors, by IT systems
  • HR queries handled informally — email, instant message
  • Lifecycle events governed module by module
  • Already a deep SuccessFactors deployment with minimal cross-team orchestration needs

nábd Care

Cross-team layer

SuccessFactors customers who need one orchestration layer across HR, IT, and facilities.

  • Onboarding must orchestrate HR, IT, and facilities as one connected experience
  • A complete asset lifecycle is needed — assigned at hire, tracked, returned at exit
  • HR needs a ticketing surface with case routing, SLA tracking, and a knowledge base
  • Joiner, mover, leaver run as one continuous orchestration
  • Cross-team handoffs are where time and quality leak today

Raptors implements both. If SuccessFactors Onboarding fits the requirement, our SF practice deploys it. If the broader employee experience layer is needed, Care extends the tenant.

Next step

One operational layer. Across the whole employee experience.

Walk through your joiner-mover-leaver flows with the team that built Care. See how the three domains connect on your tenant.