A+ Ticketing Systems and Documentation Best Practices

1. Which best practice applies to closing a support ticket?

Close immediately without user confirmation

Verify the issue is resolved and document the final resolution before closing

Keep tickets open indefinitely for reference

Close tickets only after one week regardless of resolution

2. How do service level agreements (SLAs) relate to ticket management?

They have no connection to ticketing systems

They define response and resolution time targets that ticketing systems help track and enforce

They only apply to management decisions

They are only for billing purposes

3. Which is a best practice for maintaining confidentiality in ticket documentation?

Include all personal information visible to anyone accessing the system

Avoid documenting sensitive details altogether

Document necessary information securely and restrict access to authorized personnel only

Share ticket details freely with all staff members

4. What should be included in a ticket's 'impact assessment' field?

The technician's salary information

How the issue affects the user's work, productivity, or business operations

Only the user's complaints

Nothing; this field is optional

5. How does proper ticket documentation contribute to IT service quality?

It doesn't; documentation is purely administrative

It enables faster resolution, reduces repeat issues, and improves user satisfaction through better tracking

It only benefits management reporting

It increases the cost of IT support

6. What is a 'knowledge base article' in the context of IT documentation?

A personal diary of technician experiences

A documented solution or procedure for common issues available to technicians and users

A marketing document for the IT department

A confidential file not to be shared

7. Which communication should always be documented in a support ticket?

Only successful resolutions

All interactions between technician and user, including calls, emails, and meetings

Only negative feedback from users

Technician gossip about the issue

8. What is the role of a ticket's 'assigned to' field in a ticketing system?

To randomly distribute workload

To identify which technician is responsible for resolution and tracking accountability

To prevent users from contacting the technician directly

It serves no operational purpose

9. When a ticket is reopened by a user, what should the technician do?

Immediately close it again without investigation

Review previous documentation and investigate why the issue persists

Ignore the reopening and treat it as a new ticket

Charge the user additional fees

10. What is the primary benefit of categorizing tickets by issue type?

It makes searching and filtering tickets easier for future reference and trend analysis

It has no practical benefit

It determines how much the user pays

It automatically resolves all tickets in that category

11. When opening a support ticket, what is the primary purpose of documenting the initial problem statement?

To create a permanent legal record for the organization

To establish a clear baseline for troubleshooting and tracking resolution progress

To ensure the technician bills maximum hours to the client

To satisfy government compliance requirements

12. Why is it important to add notes to a ticket during troubleshooting?

To keep the user confused about the process

To ensure continuity if another technician takes over or the issue recurs

Notes should never be added to tickets

Only the final note matters; intermediate notes are unnecessary

13. What does a 'ticket status' field typically indicate?

Whether the user is satisfied with the technician

The current stage of the ticket (open, in progress, resolved, closed)

The user's job title

How much the user is being charged

14. When documenting a technical issue, which detail is most critical for future reference?

The technician's mood during the call

Specific error codes, system information, and reproducible steps

Only the user's name and department

The user's personal background information

15. What is the significance of maintaining accurate ticket timestamps?

It allows tracking response time, resolution time, and service level compliance

It is purely for administrative record-keeping with no operational value

It helps determine which technician to blame for delays

Timestamps are optional in modern ticketing systems

16. Which practice helps prevent duplicate tickets in a support system?

Creating multiple tickets for the same issue to ensure coverage

Searching existing tickets before opening a new one

Assigning all tickets to the same technician

Closing tickets immediately without resolution

17. In ticket documentation, what should be recorded when a user requests a callback?

Only the user's name

Preferred contact time, phone number, and reason for callback

Nothing; callbacks should not be documented

Only the issue description

18. What is the purpose of a ticket escalation process?

To punish technicians for not solving issues quickly

To route unresolved issues to higher-level support or specialists

To increase the ticket's priority artificially

To close tickets without actually solving the problem

19. A ticket's priority level should be assigned based on which factor?

How long the user has been waiting

Impact to business operations and urgency of resolution

The user's department or seniority level

The technician's personal preference

20. Which of the following is a critical element when documenting a ticket's resolution?

Vague descriptions to protect company secrets

Step-by-step actions taken, results observed, and solutions implemented

Only the final outcome without intermediate steps

Technician's personal opinions about the user's technical competence

A+ Ticketing Systems and Documentation Best Practices Quiz