Helpdesk: organising employee IT support and tracking requests

A helpdesk gives employee requests an owner, status and clear outcome. Without it, tasks disappear among calls and personal messages. Ticketing works only with operating rules: a request form alone neither sets priority nor solves the user’s problem.

Distinguish incidents from routine requests

Broken access to a working system and a new workstation request need different actions. Incidents focus on restoration; requests deliver an agreed service. Track recurring root causes separately rather than concealing them through daily closure of identical tickets.

Set priority by impact and urgency. A departmental outage differs from an inconvenient setting on one device. Staff should know the rules so marking everything urgent does not become the only way to get a response.

Collect essential information without secrets

A request needs the service, symptom, onset time and work impact. Note whether it recurs and who is affected. Do not request passwords or complete customer databases in a general field; sensitive material needs an agreed secure transfer method.

Several channels may accept messages, but retain the outcome in one shared record. A ticket needs an owner during handoffs. The employee should see the next step rather than repeatedly explain the history to a new person.

A ticket does not replace access approval

For example, an employee may request a financial folder. Submitting a ticket does not establish entitlement to its contents. The helpdesk obtains the data owner’s approval, performs the action and retains confirmation without exposing secrets.

Use agreed workflows for onboarding, role changes and departure. They connect equipment, accounts and permissions. Closing the request should confirm completion of the required list, including removal of unnecessary access.

Assess outcomes and recurrence

Responding and resolving are different events. Report timing, approval waits, reopened cases and delay reasons. Do not substitute fast closure counts for quality when the user still cannot work.

Add verified solutions to a plain-language knowledge base. Instructions should match the current environment and contain no administrative secrets. Review recurring requests and choose changes that remove causes and reduce support demand.

Sources and further reading

• Atlassian: service request management
• Atlassian: incident management
• OWASP: authorisation checks

• Related subservice: Helpdesk and user support
• Explore this service area