nábd Care
For organisations running SAP SuccessFactors. One place for employees to get answers, raise requests and complete life cycle activities. Clear ownership for HR.
Who it's for
You run SAP SuccessFactors, live or nearing go-live, and it does not matter which partner implemented it. Your tenant stays the system of record. Care reads employee data from it through nábd Core, the platform's shared foundation, and holds no second copy.
Core is included with the module; you do not buy it separately. The whole layer runs on SAP Business Technology Platform (BTP), SAP's own platform for extending its products, so nothing is added inside SuccessFactors that you would have to carry through an upgrade.
What it does
Help, tasks, equipment, learning and life cycle actions in one place, inside the flow of work rather than beside it. Articles surface as an employee types, so a question is answered before it becomes a request.
What you can see: how many requests were answered by an article before anyone in HR was involved.
Reusable journeys hand tasks to HR, IT, the manager and the employee without anyone assembling the list. Requests route by topic, entity, location or team, with no manual triage. When an approver is away, delegation and backup ownership keep work moving.
What you can see: how often a request was reassigned by hand.
Each request carries an owner, a priority and a response and resolution target. Work escalates before a commitment is missed, not after the employee chases. Sensitive HR and payroll cases carry restricted visibility and protected history.
What you can see: response and resolution against target, and where they slipped.
Onboarding runs from offer to day 90. Probation conversations are planned at 30, 60 and 90 days, with goals and feedback captured. Equipment is triggered by the life cycle, learning is assigned by role, and feedback is requested at the moments that matter.
What you can see: overdue activities, per journey.
You begin with the capabilities you choose and extend by priority, entity or maturity. There is no platform decision on day one, and the next journey inherits the connection, governance and data the first one uses.
What you can see: how the first journey is used before you decide on the next.
A tailored journey per exit type, with clearance across HR, IT, Finance and the manager. Access removal, equipment return, handover and approvals are governed to closure rather than assumed complete. Exit feedback is collected as part of it.
What you can see: clearance completion and on-time access removal.
The product
Care runs in Arabic and English. The knowledge base and the service catalogue are written in both, so an employee asks in the language they work in. The three views below are the ones an employee and an HR agent open most.
Screenshots show demonstration data.
The employee life cycle
Six journeys, each with an owner, a target and a record. What is lost today is lost in the handoffs between them, so the handoffs are what Care connects.
Equipment requests and preparation steps are triggered by the hire, with custody recorded from the first issue.
Offer to day 90, across HR, IT, the manager and the new hire. Paperwork, access, equipment and learning stay visible until complete.
Conversations at 30, 60 and 90 days, with goals, feedback and outcomes captured, so a confirmation decision rests on evidence.
Learning assigned by role, entity or journey. Renewal triggers and reminders arrive before mandatory training lapses, and completion is recorded.
Feedback requested around onboarding, exits and other key moments, with privacy settings that make candour possible.
Clearance across HR, IT, Finance and the manager, governed to closure: access removed, equipment recovered, handover done, approvals recorded.
The record of each journey stays with the employee's SAP SuccessFactors profile as the system of record. Nothing about a hire, a review or an exit lives only in an inbox or in one person's memory.
Questions
Care runs on the same nábd Core, so it inherits the connection to your tenant that nábd Pay already uses. There is no new integration project and no new vendor. The first decision is which journey to start with.
A call with the team that built nábd Care. Bring the request or the handoff that goes wrong most often, and we walk through how it runs with an owner and a record.