Skip to main content
Hands-on lab

Resolve a service desk ticket: triage, document, and close

Triage and resolve a canned shared-drive access ticket by recording the reported symptoms, ordered troubleshooting steps, resolution, escalation decision, and user confirmation.

Steps

  1. 1

    Priya Raman in Accounting phoned the service desk. After changing her Windows password this morning she can no longer open the shared Accounting drive, and she is repeatedly prompted to sign in. She can still work from local copies for now, and no one else has reported the problem. Triage and resolve the ticket. Priority rubric: P1 = many users affected or a critical system down with no workaround; P2 = one user fully blocked with no workaround, or a small group; P3 = one user with a workaround and routine business impact. Steps you took, in order: confirm she can sign in to the laptop; check the account is not locked out; re-enter the stored credentials and re-map the drive. Record the resolution, decide whether first-line resolved it within scope (so whether it needs escalation), confirm the fix with the user, and close the ticket. She confirmed by phone that the shared drive opens. The free-text notes (description, progress note, and resolution notes) are not scored. Source: RTJ KB A+ Core 2 C2-4.1 (Documentation / ticketing and support-system information management). Derived from the cited RTJ knowledge-base source; not derived from certification items. The invented ticket window control labels and layout are [verify]. Last verified: 2026-10-16.

What you should see

The ticket is categorised as shared-drive access, prioritised P3, documented with the two reported symptoms and three ordered steps, resolved with updated stored credentials and no escalation, confirmed by phone, and closed as resolved.

Study the concept