Benefits should appear when they matter.
Help employees understand what support exists, whether it applies, and what to do next — without making them search through policy PDFs.
Life event → Relevant benefits → Policy → Eligibility → Employee choice → Controlled action
The problem
A long catalogue hides the one benefit that matters this month.
The decision
Which benefit applies, am I eligible under the organisation’s rule, and what do I do?
How it works
- The organisation defines the benefit, the eligibility note, and the employee action.
- ESI surfaces it when the employee starts a relevant journey or asks.
- Private life context is used for matching only if the employee allows that use.
- Starting a journey does not tell the employer the underlying life event.
What the organisation sees
The benefit catalogue it published, and claims or applications the employee actually submits.
What stays private
Why the employee looked, and any money or health detail that was not part of the claim.
The relocation pilot publishes a small benefit set, links an approved policy, and accepts one request. It is not payroll, claims processing, or a benefits wallet.
Explore. Select. Innovate.