This set builds vocabulary for structured ticketing and service-level support workflows.
0 / 5 completed
1 / 5
At standup, a dev mentions a unique identifier automatically generated whenever a customer submits a support request, used to track it through resolution. What is this called?
A support ticket is the core unit of work in a helpdesk platform, generated automatically when a customer submits a request and tracked through statuses like open, pending, and resolved until it's closed. This structured tracking ensures no request gets lost and gives the team visibility into outstanding issues. Ticketing is the foundational concept underlying most customer support software.
2 / 5
During a design review, the team wants tickets automatically assigned to the agent with the lightest current workload. Which capability supports this?
Automated ticket assignment, or load balancing, distributes incoming tickets across available agents based on factors like current workload, preventing one agent from being overwhelmed while another sits idle. This automation improves both response time and fairness in workload distribution. It's a standard efficiency feature once a support team grows beyond a single agent handling everything manually.
3 / 5
In a code review, a dev configures a rule automatically closing a ticket if the customer doesn't respond to a follow-up question within seven days. What does this represent?
An automated ticket lifecycle rule closes stale tickets after a defined period of customer inactivity, keeping the queue from accumulating tickets that are effectively abandoned but still counted as open. This automation keeps reporting metrics, like average resolution time, meaningful rather than skewed by tickets no one is actually working on. Such rules are commonly paired with a reopen option if the customer responds later.
4 / 5
An incident report shows a critical ticket breached its response-time SLA because no one was alerted as the deadline approached. What practice would prevent this?
Configuring a SLA breach warning to alert the team as a deadline approaches, rather than only after it's already missed, gives agents a chance to prioritize the ticket before the commitment is broken. Checking compliance only retroactively means the miss has already happened by the time anyone notices. Proactive alerting is a standard feature in helpdesk platforms built around service-level commitments.
5 / 5
During a PR review, a teammate asks why the team tracks every customer request as a structured ticket instead of just handling them ad hoc through email replies. What is the reasoning?
Handling requests purely through ad hoc email replies makes it easy for something to slip through the cracks and impossible to systematically measure response times or workload, while structured tickets provide built-in tracking, SLA enforcement, and reporting. This structure becomes increasingly valuable as request volume and team size grow beyond what one person can track from memory. Small teams handling very low volume may not yet feel this need as strongly.