A desk whose numbers
mean something.
Most service desks can be configured to look good. Attainment targets are settings, resolution is a status an agent can set, and a request the routing rules cannot place ends up in a queue nobody owns.
This one is built the other way. A ticket that cannot be routed is refused at creation. An agent resolves and only the requester closes. The SLA clock stops whenever the ball is in the employee's court.
And because it runs inside your HR tenant, a payroll query reaches someone who can see the payslip.
An employee desk, not an ITSM suite
Clear architectural boundaries: purpose-built for workforce employment queries, not enterprise IT infrastructure.
| This is | This is not |
|---|---|
| Where employees raise payroll, leave, document, facilities and HR queries | IT service management with asset discovery, CMDB and change management |
| A queue your HR operations team works, with routing and SLAs | External customer support or a helpdesk for your clients |
| Part of the same tenant as the employee record, the payslip and the document vault | A standalone desk you integrate with your HR system |
"If you need full ITSM, use an ITSM product. If you need a customer support desk, use a support product. This is for the queries your own employees raise about their own employment — which is a narrower job, and one that benefits enormously from being next to the data."
Most desks can be made to look good. This one resists it.
Service desk metrics are unusually easy to flatter, and everybody in HR operations knows it. Three design decisions here make the common flattery impossible rather than discouraged.
An unroutable request is refused at creation
A ticket the routing rules cannot place is refused when it is raised, rather than created and left invisible in a queue with no owner.
The alternative — accept everything, sort it out later — is how a desk accumulates a shadow backlog that nobody reports because nobody can see it. Refusing at creation forces the routing gap to be fixed rather than absorbed.
An agent resolves. Only the requester closes.
An agent can mark a ticket resolved. The ticket closes when the employee accepts that it was.
This is the single most common way a service desk reports well and performs badly: attainment measured on agent-set statuses. Here a desk cannot report full attainment on tickets nobody actually fixed, because the agent does not hold the closing action.
The SLA clock runs in working time, and pauses when the ball is theirs
The clock measures working time, not wall-clock time, so a Friday evening ticket is not automatically breached by Monday morning.
And it pauses whenever the request is waiting on the employee — for a document, a clarification, or an approval. An SLA figure that includes four days waiting for the employee to send a bank statement is not a measure of anything.
Ask any desk vendor you are evaluating whether an agent can close their own ticket, and whether the SLA clock keeps running while the requester is thinking. The answers tell you what their attainment percentage actually measures.
Teams as queues, with the assignment model you actually want
Different queues need different assignment behaviour. A payroll queue is not a facilities queue.
| Assignment Model | When you use it |
|---|---|
| Pull | Agents take the next item themselves — works where the team is small and self-managing |
| Round-robin | Even distribution across active team members, regardless of load |
| Least-loaded | Assignment by current open volume rather than by turn |
| Named owner | Specific categories that always route to a designated subject-matter specialist |
WIP limits per agent
Caps how much any one agent can hold open simultaneously, ensuring a queue cannot be cleared simply by distributing tickets into individual invisibility.
Three-level taxonomy
Organises categories with precision — so a payroll query regarding a Professional Tax deduction routes differently from a bank account update, without spawning unmanageable top-level queues.
Configurable escalation matrix
Time-based and tier-based escalation paths trigger automated alerts to queue leads before an SLA threshold breaches, maintaining operational accountability.
The query is about a payslip. The payslip is right here.
The most common employee queries are about pay, leave, documents and statutory records. In a standalone desk, every one of them is a context-switch: the agent reads the ticket, opens the HR system, finds the employee, finds the record, comes back.
1 · The agent can see the record
Subject to their own permissions — the desk does not bypass the authorisation model. An HR operations agent with payroll view rights sees the payslip; one without does not.
2 · Documents come from the vault
A document request is fulfilled from the governed document store, with confidentiality tier, retention and audit trail already attached — rather than an agent emailing a file from a folder.
3 · No integration to maintain
No third-party connector, no webhook synchronization lag, and no field-mapping to re-test whenever either system upgrades or alters its database schema.
4 · Permissions are the same permissions
One authorization model — persona, module, verb, data scope — governs both. An agent's access to a payslip through the desk is exactly their access to it everywhere else.
A standalone desk with a perfect integration still has two permission models, two audit trails and two sources of truth. This has one of each.
Some tickets must not be visible to the person's own manager
A desk inside an HR system will receive grievances, POSH complaints and queries an employee does not want their reporting line to see. That is a design requirement, not an edge case.
Granular isolation for statutory & sensitive grievances
When an employee raises a ticket under a sensitive category (e.g. POSH complaints, workplace harassment, or formal grievances against leadership), the platform applies strict isolation rules:
Manager Visibility Excluded
The reporting manager and departmental hierarchy are strictly excluded from viewing the ticket, queue updates, and ticket history.
Dedicated Committee Intake
Routes directly to designated roles — such as the POSH Internal Committee presiding officer or Head of IR — bypassing regular HR operations queues.
Isolated Search & Audit
Sensitive ticket content is excluded from general desk search indexes and operational dashboards, maintaining end-to-end confidentiality.
* Honest architectural boundary: The system authenticates the employee against their HR identity record. It does not provide unauthenticated anonymous intake. For whistleblower disclosures requiring full anonymity, dedicated third-party statutory whistleblower mechanisms should be used.
Contextual answers before a ticket is created
The queries that reach your team should be the ones that need a person.
Articles surfaced at the point of raising a ticket deflect repetitive questions before submission — and because the desk sits in the HR tenant, an article can point directly at the employee's own record (e.g. state leave entitlement or PF UAN passbook) rather than offering a vague generic explanation.
An article explaining maternity benefit eligibility dynamically references the employee's tenure and applicable state Act, eliminating repetitive back-and-forth inquiries.
Measures whether an employee abandoned ticket creation after reviewing a targeted article, distinguishing genuine resolution from unaddressed frustration.
Meet the workforce where it already is
Accessible channels ensure every tier of the workforce can raise queries without operational friction.
Web & Mobile Portal
Fully responsive browser experience across desktop and mobile. No forced app downloads consuming worker phone storage.
Email Inbound Intake
Inbound emails to dedicated queue addresses automatically create tickets with full reply-threading back to the employee's inbox.
Supervisor On-Behalf Intake
For deskless plant and site workers without email, site supervisors can raise requests on their behalf with complete identity audit trails.
WhatsApp (Roadmap)
Direct WhatsApp intake and status notification for blue-collar and facility workforces is currently in active testing on the near-term roadmap.
Honest limits on employee service desk
Clear architectural boundaries prevent misaligned expectations and maintain operational trust.
- ✕This is not IT service management — No asset discovery, no configuration management database (CMDB), no change or release management, and no incident–problem–change lifecycle. If your IT function needs ITSM, they need an ITSM product.
- ✕This is not customer support — No external customer contacts, no multi-brand support portals, and no client-facing SLA contracts. This desk is strictly internal for employees.
- ✕We will not match a dedicated desk on breadth — ServiceNow, Freshservice, and Zoho Desk have far more surface area, deeper third-party integration catalogues, and mature BI reporting. We compete on measurement honesty and being in the same database as the payslip — not on feature count.
- ✕Reporting is operational, not analytical — Reports cover active queue volumes, working-time SLA attainment, ageing, and agent load with standard CSV export. We do not provide an embedded business intelligence or OLAP slice-and-dice layer.
- ✕No CSAT or satisfaction survey — We focus strictly on operational resolution and requester sign-off rather than subjective star-rating surveys.
- ✕No complex automation or workflow builder beyond routing — Assignment rules, dry-run simulation, WIP limits, and escalation matrices are purpose-built; we do not provide an open-ended Zapier-style workflow canvas.
- ✕Native mobile apps are in progress — Accessible today via modern mobile-first web browsers. Native app store binaries are in active development.
- ✕India only — Deliberately aligned with Indian statutory records, state establishment structures, and domestic workforce operations.
- ✕No unauthenticated anonymous intake — Every ticket is linked to authenticated employee identity for statutory governance; third-party anonymous whistleblower lines should handle anonymous disclosures.
Direct answers to operational questions
Everything HR and IT leaders ask when evaluating our internal employee service desk.
See it against the desk you already run.
Bring a week of your current desk's tickets to the demo — the categories, the volumes and the attainment figure you report. We will walk through how the same week would be measured here, including the tickets that would have been refused at creation and the hours that would not have counted against your SLA.
It is a more useful comparison than a feature grid, and it usually changes what the attainment number means to you.