The employee self-service desk: address proofs, salary certificates, investment declarations and every "can HR please" request raised from the portal, tracked to closure, and answered once with a document instead of four times with an email.
Why it exists
The HR helpdesk exists whether or not you install one — it just runs on shoulder-taps, WhatsApp messages and forwarded emails until you do. Employee services software gives every request a form, an owner and a status: letters, ID cards, insurance queries, address proofs, IT assets, certificate attestations — whatever your catalogue offers. The employee raises it in the app; someone accountable resolves it; both can see where it stands.
The catalogue is yours. Each service defines what information the request needs, who fulfils it, and how long it should take. Requests that need sign-off route through the same approval engine as everything else in Kuzhu, so a request for a salary advance letter and a request for a new laptop follow their own configured chains without anyone maintaining two systems.
What HR gets back is the queue in one place — with ageing, so the request quietly stuck for nine days is visible before the employee escalates it. What management gets is the pattern: which services are requested most, where the time goes, and which branch generates four times the queries, which is usually a policy communication problem wearing a ticketing costume.
The outcome
“HR answers each question once, in a system, instead of daily in an inbox.”
Feature by feature
Start
01
Request catalogue you define — letters, certificates, corrections, queries
02
Investment declarations and proof collection for TDS, with windows and reminders
03
Auto-generated letters from your own templates where no human is needed
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Define the services employees can request — letters, cards, queries, equipment — each with its form fields, owner and expected turnaround.
From the app, with the details the form asks for. No format confusion, no "please share details" round-trips.
Services that need approval flow through your configured chains before fulfilment; the rest go straight to the owner’s queue.
The owner resolves, attaches the output — a letter, a confirmation — and the requester is notified in the same thread.
Ageing and volume reports show what is slow and what is frequent, which is where the next process fix comes from.
Worth a closer look
Buyer questions
2 answers
The answer
A large share of HR requests are letters — address proof for a lease, salary certificate for a bank, visa letters, experience letters. Because services connects to the document engine, these generate from templates with the employee’s real data, on your letterhead, with the register recording issue. Turnaround drops from "next week" to the time it takes someone to click approve.
The answer
Expected turnaround per service plus visible ageing does most of what a formal SLA regime does, without the ceremony. The queue sorts by how overdue things are; the monthly report shows resolution time by service and by owner. When a category consistently blows its time, the fix is usually in the process, and now there is data to argue it with.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Terms used here
Investment declaration
An investment declaration is the employee's statement at the start of the year of the deductions and exemptions they plan to claim, so TDS can be computed correctly; proofs follow in January.
Employee self-serviceESS
Employee self-service lets employees see and act on their own HR data (payslips, leave, attendance, declarations, letters) from a portal or app without asking HR.
Anything you put in the catalogue: letters and certificates, HR queries, IT and equipment requests, insurance questions, ID cards — each with its own form and owner.
Yes. Any service can route through an approval chain first, using the same workflow engine as leave and expenses.
Yes — raised, in progress, resolved, with the conversation and any attachments in one thread in the app.
Yes. Letter-type services pull from document templates, filling the employee’s data on your letterhead, ready for sign-off and issue.
The queue shows ageing against each service’s expected turnaround, and reports break resolution time down by service and owner.
Works best beside
Other people modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us