Employee self-service: what should not need an HR ticket

Employee self-service should cover routine transactions a person can complete without waiting on HR: viewing payslips, applying for leave, checking balances, punching or viewing attendance, and reading assigned SOPs. HR tickets — email, chat, or a queue — should remain for exceptions, policy judgments, and corrections that change the system of record. If every payslip download and every casual leave day is a ticket, HR is the bottleneck, not the control.

This is an operating split, not a product lander for an unpublished helpdesk suite. Dayzen HRMS is hire-to-exit people operations; employees can self-serve payslips, leave, assets, and SOP reads where those modules are used. There is no live helpdesk feature page to treat as a current product surface. Dayzen PMS means Project Management System, not performance management.

Routine transactions versus exception tickets

A routine transaction has a known path, a known owner (often the employee), and an outcome the system can record without HR interpreting policy in the moment. An exception needs a human to judge, reconstruct, or override.

Usually self-service	Usually an HR (or named owner) ticket
Download this month’s payslip; view past payslips you are allowed to see	Payslip looks wrong after freeze — needs payroll investigation
Apply for leave; see balances and approval status	Leave that breaks policy, negative balance exceptions, or backdated leave after cutoff
Punch / mark attendance; view your own timesheet	Regularisation after the published close, or a device failure affecting many people
Read an assigned SOP and acknowledge	Policy does not exist yet; you need a written exception
See assets assigned to you; request a return handshake if the process is published	Lost or damaged asset, or an assignment that was never recorded
Update low-risk contact details if your RACI allows it	Name, employee ID, department, manager, status, bank or statutory identifiers

Who may edit which profile fields is owned by who updates employee profiles. Self-service reduces tickets; it does not hand employees the keys to identity or pay-critical data. Should employees edit their own salary or employee ID? No. They can request a correction; HR or a defined owner applies it with a trail.

Payslips without a “please send PDF” culture

Payroll calculation and payslips only cut HR load if employees can retrieve their own documents after release. A shared drive of passworded PDFs, or a monthly “HR please send mine,” recreates the ticket pile.

Set expectations in onboarding:

• When payslips release relative to payday (your choice — publish it).
• Where to open them (the employee login, not a personal WhatsApp).
• What to do if a number looks wrong: raise an exception with period, component, and screenshot of the payslip line — not a vague “salary issue.”

Calculation is still not filing and not bank credit. Employees asking “has PF been deposited?” may need finance or a consultant, not another HR screenshot of the payslip. Keep that distinction so self-service does not become a statutory helpline HR cannot actually answer.

Leave and attendance: the highest-volume routines

Most growing teams drown here first. Leave management should let employees apply, see balances, and watch approval state. Managers approve in the same system. HR chases breaches of SLA, not every casual leave.

Attendance should let employees see their own punches and, where policy allows, submit regularisation before the monthly close. After close, regularisation is an exception because it threatens LOP and payslips. That monthly order is the monthly HR operating loop, not a self-service slogan.

Publish the employee-facing rules

1. How to apply leave (including who approves if the manager is on leave).
2. Until when a punch can be regularised without HR.
3. What sandwich, restricted holiday, or half-day rules mean in one page of plain language.
4. What happens if they apply after freeze.

If those rules live only in a founder’s head, every case becomes a ticket. Self-service software cannot replace unpublished policy.

Self-service is the path for the known case. Tickets are the path for the case your policy did not already decide.

SOPs and assets: read and see, do not invent a second desk

Assigned SOP reads belong in self-service: open, read, acknowledge. That is how you know a joiner saw the attendance rule before they break it. HR should not forward PDF policies one by one unless the person cannot access the system (contractor without login, or a genuine access outage).

Assets assigned to the employee should be visible to them. “What laptop do I have?” should not require an HR search. Lost, damaged, or never-issued kit is an exception: someone must update the record and, at exit, Full & Final still needs a true assignment list. Self-service visibility does not replace the asset owner’s job; it stops the routine question.

What still needs a human queue

Keep a thin exception path. You do not need to pretend it is a full ITSM suite. Email with a subject convention, a shared mailbox, or an internal form is enough if you classify the request:

• Data correction: wrong spelling, wrong bank after a documented change, duplicate record suspected.
• Policy judgment: unpaid leave exception, late joining documents, dispute about LOP after freeze.
• Access: cannot log in, cannot see a payslip that should exist.
• Lifecycle: transfer, location change, exit paperwork that is not a self-serve form.

Route by owner. Payroll exceptions should not sit in a generalist pile for a week. Identity corrections should hit the system of record, not a side spreadsheet — see what a system of record means. Lifecycle events follow the employee management process, not a chat thread that never updates fields.

Do not stand up a “helpdesk module” in your buying deck unless you will actually operate one. An unpublished feature URL is not a process. The commercial home for connected people operations remains Dayzen HRMS.

Manager self-service is not the same as employee self-service

Managers need team queues: pending leave, open regularisations, who is in today. That is still self-service — for the manager role — not an HR ticket per approval. Managers should not see company-wide compensation or other teams’ identity documents. Visibility design belongs with who should see what in an HR system.

If managers approve only on WhatsApp, you have not implemented self-service. You have implemented a rumour that HR must later type into the system. The ticket volume will stay high because the system is not the place work happens.

Rolling it out without a big-bang portal speech

Growing Indian companies often announce “employee portal” and then keep processing everything in email. Roll out by transaction, not by slogan:

1. Payslips first — high demand, low policy ambiguity.
2. Leave apply and approve second — needs manager habit.
3. Attendance view and in-period regularisation third — needs cutoff communication.
4. SOP acknowledgements and asset lists when those modules are actually in use.

Measure ticket types for two months. If “please send payslip” does not fall, employees cannot find the login or do not trust it. If “please apply leave for me” does not fall, managers are still the informal path. Fix the habit before you buy another channel.

Standalone tools make this worse when each login has a different employee list. That conflict pattern is standalone HR tools versus a connected HRMS. Self-service on top of three identities is three portals and more tickets.

---

A working rule you can put in the employee handbook

Use this language and fill the system name:

Use [system] for payslips, leave, your attendance, assigned SOPs, and assets showing against you. Message HR only for corrections, policy exceptions, access problems, or lifecycle events. After attendance and leave freeze, late changes are exceptions, not a second self-service path.

That rule is useful even if you never mention a vendor. Software helps when identity is one record and the monthly loop is public. Software cannot retire tickets that are actually unpublished decisions. Keep HRMS as the connected product; keep tickets rare and classified; keep helpdesk landers out of the story until they exist.

Watch for three ticket types that look like self-service failures but are policy failures. “Apply leave for me because the app is confusing” is training and a one-page leave SOP. “Mark me present; I was at the client site” is an attendance type you never configured, so every outdoor day becomes an exception. “HR, what is my leave balance after the sandwich days?” is a rule you never wrote down, so employees will not trust the number on screen. Fix the rule, then point people back to the screen. Adding a human queue in front of an unclear rule only trains everyone to skip the system.

Founders in small teams often remain the informal helpdesk: a WhatsApp ping that bypasses freeze dates. If the founder will still override LOP in chat, publish that as an exception path with the same close rules, or stop pretending self-service is live. Employees copy the real path, not the handbook paragraph.