Why has the average response time for Mews's customer support tickets increased by 40% in the last two weeks?

Introduction

The recent 40% increase in average response time for Mews's customer support tickets over the past two weeks is a critical issue that demands immediate attention. This surge in response time not only impacts customer satisfaction but also has potential ripple effects on overall product performance and business metrics. To address this challenge, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term fixes and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might have been a recent product update or system change. Has Mews rolled out any new features or updates in the last month?

Why it matters: Recent changes could directly impact support ticket volume and complexity. Expected answer: Yes, a major update was released three weeks ago. Impact on approach: If confirmed, we'd focus on analyzing the update's impact on user experience and support needs.

• Considering the metric specifics, I'm curious about the ticket volume. Has there been a significant increase in the number of support tickets during this period?

Why it matters: A surge in ticket volume could explain longer response times if staffing hasn't adjusted. Expected answer: Ticket volume has increased by 25% in the same period. Impact on approach: This would lead us to investigate both capacity issues and potential product problems causing the increased tickets.

• Thinking about team dynamics, I'm wondering if there have been any recent changes in the support team structure or staffing levels?

Why it matters: Staff changes or shortages could directly impact response times. Expected answer: No significant changes in the support team. Impact on approach: If confirmed, we'd focus more on process inefficiencies or external factors affecting performance.

• Considering potential data anomalies, has there been any change in how response time is measured or reported in the last month?

Why it matters: Ensures we're comparing apples to apples and not chasing a non-existent problem. Expected answer: No changes in measurement or reporting methods. Impact on approach: Confirms the issue is real and not a data artifact, allowing us to focus on operational causes.