Skip to main content

Helpdesk Capability Overview

Summary​

The module has a broad domain foundation and a narrower user interface. Service capabilities exist for ticket operations, reference data, SLA policy, escalation, attachments, audit/timeline and reports; the administration UI exposes ticket work and read-only report output, while employee self-service exposes only submission and listing.

Audience​

Business owners, helpdesk administrators, service agents, product, QA, support and architects.

Business Purpose​

Distinguish verified usable capabilities from foundation endpoints and absent service-management features.

Actors​

Employees use the simple portal; agents use the administration worklist; administrators own tenant configuration; implementers connect downstream document and notification services.

Business Process​

The capability supports classify, open, assign, discuss internally, attach, change state, track SLA, escalate and report. Compatibility records and administrative reference-data operations also exist at the service boundary.

Responsibilities​

Product owners must determine which service-level capabilities receive supported UI. Implementers must verify routing and authorization. Agents must not assume that all service actions are exposed or guarded by the UI.

Business Rules​

The service accepts nine statuses, four priority levels, two SLA target types and append-only assignment/comment/attachment records associated with a ticket.

Integrations​

Document storage, lifecycle event delivery, notification recipient resolution and gateway forwarding are implemented. Workflow orchestration is not.

Limitations​

Category, priority and SLA maintenance are not exposed in the reviewed administration screen. Manual breach/escalation capabilities exist without reviewed UI controls. The report cards render service responses as raw structured content rather than purpose-built visualizations.

Requires Confirmation​

Supported production surfaces, compatibility routing mode, administrator access, scheduled SLA-check operation and event delivery deployment require confirmation.

Source References​

  • microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx

Reference Content​

The capability assessment above distinguishes verified domain foundation, exposed user actions and absent features.

See Also​

Keywords​

Helpdesk capabilities, ticket operations, service maturity, agent interface.

Revision Information​

Draft source-backed reference reviewed 2026-07-20; next quarterly review is 2026-10-20.