Prioritization

Prioritizing support tickets is crucial for any customer service team, especially in a fast-paced environment like a gaming company. A well-defined prioritization system ensures that you address the most critical issues first, manage player expectations, and allocate your resources effectively.

Here is a comprehensive guide on how to prioritize support tickets, using a framework based on Impact, Urgency, and Player Value.

The Core Prioritization Framework: Impact & Urgency

This is the most common and effective method for prioritizing tickets. It involves a simple matrix that helps you classify every incoming ticket.

1. Impact

How many players are affected by the issue?

• High Impact: A problem affecting a large number of players or the entire game server. This could be a major bug, a server outage, a widespread payment processing failure, or a security vulnerability.

• Medium Impact: An issue that affects a group of players or a specific in-game feature. This could be a bug in a specific quest, a problem with a particular character class, or an issue with a regional leaderboards.

• Low Impact: A problem affecting only a single player. This is typically an account-specific issue, a minor UI bug, or a general question.

2. Urgency

How quickly does the issue need to be resolved?

• High Urgency: The player is completely blocked from playing the game or using a core feature. The issue is time-sensitive (e.g., a time-limited event bug).

• Medium Urgency: The player can still play, but their experience is significantly degraded or a feature is not working as intended.

• Low Urgency: The issue is a minor inconvenience, a general question, or a feature request. The player can wait for a response without a major negative impact on their game experience.

The Prioritization Matrix

Combine Impact and Urgency to assign a priority level:

Example Priority Levels for a Gaming Company:

• P1 - Urgent: The game server is down. A major bug is preventing all players from logging in or completing the tutorial. A security breach has been reported.

• P2 - High: A specific in-game item is not working, affecting all players who own it. A regional server is experiencing severe lag. A bug in a time-limited event is preventing players from earning rewards.

• P3 - Normal: A single player's account is locked. A payment failed for a specific player. A minor visual bug is present in a rare cosmetic item.

• P4 - Low: A player has a question about game lore. A player is requesting a new feature. A minor typographical error is found in a quest description.

Additional Factors for Prioritization

While Impact and Urgency are the foundation, other factors can help you fine-tune your prioritization system.

1. Player Value

• VIP/High-Value Players: Players who have invested significant time or money into the game. Their issues should be given extra weight to ensure their continued loyalty.

• Streamers/Content Creators: Public-facing players whose experience directly impacts your brand reputation and community.

2. Ticket Age

• Stale Tickets: Tickets that have been open for an extended period without a response. You should have a process to automatically escalate these tickets to prevent player frustration. This is sometimes referred to as a "SLA Breach."

3. Support Channel

• Live Channels: Issues reported via live chat or in-game messaging often have a higher expectation for a fast response than those sent via email.

• High-Volume Channels: If a bug is reported frequently across multiple channels (e.g., in-game chat, Discord, and a ticket form), its priority should be increased.

4. Recurring Issues

• Repeat Bugs: If a ticket reports a bug that has been reported multiple times by different players, it should be flagged for a higher priority and potentially escalated to the development team for a permanent fix.