HR platform for Uzbekistan
eNPS & Employee Happiness Index (EHI)
Talantiq measures loyalty and engagement with eNPS pulse surveys and rolls them into an employee happiness index (EHI): drivers with their contribution, segments, trends and alerts — on the same data as the rest of the platform.
- Regular eNPS and happiness (EHI) readings instead of one-off surveys
- Each engagement driver's contribution and delta from the last wave
- Segments, trends and benchmark under access rights
- Anonymity and invite anti-fraud for honest, un-gamed responses
eNPS and the happiness index (EHI)
Short eNPS pulse surveys count the share of promoters and detractors, while the happiness index (EHI) rolls team sentiment into one number. Both are computed per survey wave rather than once, so you see the trend, not a single-day snapshot.
Engagement drivers and their contribution
Responses break down into engagement drivers (manager, recognition, workload, growth and more), each with its contribution to the overall index and its delta from the previous wave. You see not just 'how much' but 'what exactly' moves happiness up or down.
Segments, trends and benchmark
Results slice by department, location and other segments under access rights (RBAC/ABAC), and compare against past waves and a benchmark. Trends and CSV export track the effect of your changes.
Anonymity and invite anti-fraud
Personal invites prevent ballot stuffing and repeat responses, and results show only in aggregate — nothing is revealed below the anonymity threshold. Alerts fire when the index or a driver drops below a threshold.
FAQ
How anonymous are employee responses?
Results appear only in aggregate: below the anonymity threshold no breakdown is shown, and personal invites don't tie a response to a person in reports.
How is eNPS different from the happiness index (EHI)?
eNPS measures willingness to recommend the company as an employer, while EHI rolls sentiment and engagement drivers into one index. Both are computed per wave and show a trend.
Where do segments come from and how does this connect to other modules?
Segments (departments, locations, tenure) come from the org structure on the platform shared data — no separate list upload; access to slices is limited by RBAC/ABAC.