Help Desk Software Help Desk General 5 — Questions and Answers
Question 1: A user submits a ticket about slow internet but the issue actually affects 50 other users in the same building. What type of situation is this?
- A low-priority personal issue
- A major incident requiring a broader response and communication plan (Correct answer)
- A standard ticket that should be handled in queue order
- A problem that should be automatically closed after 24 hours
Correct answer: A major incident requiring a broader response and communication plan
When a single reported issue reveals widespread impact across many users, it qualifies as a major incident and typically requires escalation, a war room, and proactive communication.
Question 2: Which of the following is an example of 'proactive support' in a help desk environment?
- Waiting for users to report problems before taking action
- Monitoring systems and alerting users about issues before they call in (Correct answer)
- Responding only to tickets submitted via email
- Closing tickets without contacting the user
Correct answer: Monitoring systems and alerting users about issues before they call in
Proactive support means identifying and communicating potential issues—using monitoring tools or alerts—before users are impacted enough to submit a ticket.
Question 3: What is the purpose of a 'post-mortem' or 'incident review' after a major outage?
- To assign blame to the agent who failed to prevent the outage
- To document what happened, why it happened, and what changes will prevent recurrence (Correct answer)
- To immediately delete all related tickets from the system
- To calculate financial penalties from the SLA breach
Correct answer: To document what happened, why it happened, and what changes will prevent recurrence
A post-mortem is a blameless analysis of a major incident that documents the timeline, root causes, and corrective actions to prevent similar events in the future.
Question 4: Which help desk feature allows a manager to listen to an ongoing support call without the customer or agent knowing?
- Call whispering
- Call barging
- Call monitoring (silent listen) (Correct answer)
- Call conferencing
Correct answer: Call monitoring (silent listen)
Silent call monitoring lets managers listen to live calls for quality assurance purposes without interrupting or alerting either the agent or the customer.
Question 5: What does 'time to first response' measure in help desk metrics?
- How long it takes to fully resolve a ticket
- How quickly an agent sends an initial acknowledgment or reply after a ticket is submitted (Correct answer)
- The total hours an agent works per day
- The time a customer spends on hold before being connected
Correct answer: How quickly an agent sends an initial acknowledgment or reply after a ticket is submitted
Time to first response (or First Response Time) measures the elapsed time between ticket creation and the agent's first meaningful reply, reflecting responsiveness.
Question 6: A help desk team notices that 40% of tickets this month were about the same password reset issue. What is the most effective long-term solution?
- Hire more agents to handle the volume
- Implement a self-service password reset tool and add a knowledge base article (Correct answer)
- Raise the SLA response time for password tickets
- Close all password tickets immediately without responding
Correct answer: Implement a self-service password reset tool and add a knowledge base article
Deploying a self-service password reset tool eliminates the root cause of the recurring ticket volume, while a knowledge base article guides users who still need help.
Question 7: In help desk software, what is the function of a 'parent-child ticket' relationship?
- It allows one ticket to be visible to multiple companies simultaneously
- It links a master ticket to related sub-tickets, enabling coordinated tracking of complex, multi-part issues (Correct answer)
- It automatically escalates any ticket created by a manager
- It prevents agents from closing a ticket without supervisor approval
Correct answer: It links a master ticket to related sub-tickets, enabling coordinated tracking of complex, multi-part issues
Parent-child ticket relationships let teams break a complex issue into sub-tasks tracked as child tickets under a master parent, keeping all related work organized and linked.
A user submits a ticket about slow internet but the issue actually affects 50 other users in the same building.
What type of situation is this?