How do I raise an HR request?
HR requests go through the internal support desk, where a request is filed under a category, given a subject and a description, and becomes a numbered ticket somebody is assigned. Eight categories exist in one live instance, covering admin and HR, attendance, benefits, equipment, leaves, policies, payroll questions and everything else.
The category is not filing for its own sake. It decides who picks the request up.
An equipment request and a leave question go to different people, and a desk without categories makes somebody triage every message before anything moves.
Eight is a deliberate number. Enough to route, few enough that a person choosing one does not hesitate. The categories are managed rather than fixed, so a company adds or removes them.
Payroll appears as a category, and it is worth being precise about what that means. Employees ask pay questions, so the desk gives them somewhere to go. The category routes the question to whoever handles pay.
The form takes a subject, the detail and up to five attachments at ten megabytes each. A screenshot is usually worth three paragraphs.
Once submitted, the request gets a number and a status the requester can follow. Statuses go beyond open and closed, and one live instance shows an on-deck state for queued work.
A request that needs a decision still starts here. The ticket holds the ask and its status while the decision is made, so nothing is lost in a chat thread.
Put the specific ask in the subject line. "Laptop replacement, build times" reaches the right person faster than "question", and the subject is what the queue displays.
Related questions
Can I attach files to a request?
Yes, up to five files at ten megabytes each. Screenshots and photographs usually resolve equipment questions faster than a description.
Are the eight categories fixed?
No. Categories are managed from the administration side, so a company adds, renames or removes them to match how its own requests arrive.
Can I see the status of my request?
Yes. A request carries a number and a status the requester can follow, which is the point of routing it through the desk rather than a message.