100-150 CCST ยท Troubleshooting and device commands
Help desk, ticketing and documentation
Ticket handling, prioritisation, policies and procedures, escalation, and accurate and complete documentation.
Key points
- A ticket records who reported the issue, the symptoms, steps tried, priority and outcome.
- Priority depends on business impact and number of users affected.
- If you cannot solve it within your role or policy, escalate to the next tier.
- Complete, accurate notes let others continue the work and build a knowledge base.
Practice questions
Which ticket should normally be handled first?
- A request to change a desktop wallpaper
- A question about printer colours
- A request for a new mouse
- The whole office cannot reach the internet
Show answer
Answer: D. The whole office cannot reach the internet
Priority follows business impact and the number of people affected. A site-wide outage outranks a single cosmetic request.
Which details belong in a good ticket record?
- The user's contact details and a clear description of the symptom
- The user's password in plain text
- The troubleshooting steps already tried
- Your opinion on whose fault it was
- The final resolution
Show answer
Answer: A. The user's contact details and a clear description of the symptom, C. The troubleshooting steps already tried, E. The final resolution
Contact, steps taken and resolution make the ticket useful to others. Passwords must never be stored in plain text and blame opinions are not facts.
Documentation is only needed for tickets you could not resolve.
Show answer
Answer: False
False. Resolved tickets are documented too, so the same issue can be solved faster next time and trends become visible.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
