A technology firm has implemented a new ticketing system for managing customer support requests. However, the firm is facing challenges in effectively prioritizing and managing these tickets due to…

Question

Options

• APrioritize tickets based on the order of receipt
• BDevelop a dynamic prioritization model that assesses the impact and urgency of each ticket
• CStop recording requests during exceptionally busy times
• DLimit ticket submissions to reduce the workload on support staff

• A
  2% (1)
• B
  85% (39)
• C
  9% (4)
• D
  4% (2)

Explanation

Option B is correct because a dynamic prioritization model evaluates both the urgency (how time-sensitive the issue is) and impact (how many customers or business operations are affected), ensuring critical tickets rise to the top regardless of when they arrived - directly solving the core problem described.

Why the distractors fail:

• A (order of receipt) is exactly the flawed approach the firm is already suffering from - it ignores urgency entirely and treats a minor request the same as a system outage.
• C (stop recording during busy times) makes the problem worse by creating blind spots; unrecorded issues can't be tracked or resolved at all.
• D (limit submissions) doesn't fix prioritization - it just artificially suppresses demand while leaving existing customers underserved.

Memory tip: Think of an emergency room triage system - doctors don't treat patients in the order they walked in; they assess severity first. A dynamic prioritization model is IT's equivalent of triage. If you see a question about support queues going wrong, the answer almost always involves smarter assessment criteria, not fewer submissions or simpler ordering.

No community discussion yet for this question.