What factors are contributing to the recent spike in customer support tickets for Poly's Voyager headset line?

Introduction

The recent spike in customer support tickets for Poly's Voyager headset line is a critical issue that demands immediate attention and a thorough root cause analysis. As we delve into this problem, we'll employ a systematic approach to identify, validate, and address the underlying factors contributing to this surge in support requests. Our goal is not only to resolve the immediate issue but also to implement long-term strategies that enhance product quality and customer satisfaction.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might be a recent product update or change. Has there been any software or firmware update to the Voyager line in the past 30-60 days?

Why it matters: Recent changes often correlate with spikes in support tickets. Expected answer: Yes, a firmware update was released 45 days ago. Impact on approach: If confirmed, we'd focus on the update's contents and rollout process.

• Considering user segments, I'm curious about the distribution of tickets. Are we seeing a higher proportion of tickets from a specific user group (e.g., enterprise vs. individual consumers)?

Why it matters: Identifying affected segments helps narrow down potential causes. Expected answer: Enterprise users are reporting issues at a higher rate. Impact on approach: We'd investigate enterprise-specific features or deployment methods.

• Thinking about the nature of the support tickets, I'm wondering about the most common issues reported. What are the top 3 categories of problems users are experiencing?

Why it matters: Understanding the types of issues helps focus our investigation. Expected answer: Connectivity problems, audio quality issues, and battery life complaints. Impact on approach: We'd prioritize these areas in our technical and user experience analysis.

• Considering potential external factors, has there been any significant change in our support system or process that might affect ticket volume or categorization?

Why it matters: Changes in support processes can sometimes create artificial spikes. Expected answer: No major changes to the support system in the last 6 months. Impact on approach: If confirmed, we'd focus more on product-related issues rather than support system anomalies.