Two questions make up most of your HR traffic
"What is my leave balance" and "where is my payslip". Neither needs a person, and answering them consumes the time HR should spend on the ones that do.
The queries that stop arriving
They see their own numbers
The same balance HR sees, on their phone, without asking anybody.
Payslips they can fetch
Current and historical, downloadable, without a request and a wait.
Asking in plain language
Klokee turns "I need Friday off" into the actual application, drafted and ready to confirm.
Count them before you fix them
In a company of a hundred people, HR fields dozens of small requests a month. The overwhelming majority are lookups: a balance, a payslip, a joining date, a form.
None of them require judgement. All of them require an interruption, a search, and a reply — and they arrive by WhatsApp, at any hour, from people who are perfectly capable of looking the answer up if the answer were available to them.
Self-service only works if the data is trusted
This is the part that gets skipped. Publishing a leave balance that HR themselves do not believe is worse than publishing nothing, because now the wrong number is authoritative and the argument is louder.
The balance has to be computed by the engine from the actual policy, and it has to be the same number payroll uses. When there is only one number, there is nothing to dispute.
Plain language for people who do not use forms
A shop-floor employee will not find "attendance regularisation" in a menu. They will type that they forgot to punch out on Tuesday.
An assistant that turns that sentence into the correct request, drafted and shown for confirmation, reaches a population that self-service portals historically never did.
What is left is the work worth doing
When lookups stop arriving, what remains in HR's queue is exceptions, disputes, policy decisions and people who genuinely need help. That is a considerably better use of the same two people.
From an interruption to a lookup
They open the app
Balance, payslip, claim status and documents — theirs, current, without asking.
Or they just type it
Plain language in; a correctly drafted request out, ready to confirm.
Approvals move
Managers clear their queue from a phone, so requests do not wait on a desk.
HR handles exceptions
What is left needs judgement, which is what HR is for.
Cut the routine HR queries FAQs
Will employees actually use it?
Adoption follows trust in the numbers. If the balance shown is right, people check it themselves; if it is wrong once, they go back to asking. Getting the data right is the adoption strategy.
What about staff without smartphones?
Plan a fallback deliberately — a kiosk, a supervisor with access, or printed payslips on request. A rollout that quietly excludes the shop floor creates a two-tier system and does not reduce queries much.
Does HR lose visibility?
No. HR sees everything they saw before; what changes is that they are not the retrieval mechanism for it.
Can employees see historical payslips?
Yes, and that removes a whole category of request — the loan application, the visa file, the rental agreement that needs three months of payslips.
Which queries actually disappear?
Balance and payslip questions, mostly — the two that make up the bulk of routine HR traffic. They disappear only if the balance shown is right, which is why it is derived rather than typed.
Will employees actually use self-service?
They use it when it works on the phone they own, in their language, without an install. Self-service that assumes a laptop and English fails quietly.
See it on your own data
Fourteen days, no card, no consultant. Import your spreadsheet and watch it compute.