What factors are contributing to the recent 20% increase in customer support tickets related to FreshBooks's time tracking functionality?

Introduction

The recent 20% increase in customer support tickets related to FreshBooks's time tracking functionality is a concerning trend that requires immediate attention. To address this issue, 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 be a recent product update. Has there been any significant change to the time tracking feature in the last 30-60 days?

Why it matters: Recent changes often correlate with support ticket spikes. Expected answer: Yes, a UI refresh was implemented. Impact on approach: If yes, we'd focus on the changes made and user adaptation.

• Considering user segments, I'm curious about the distribution. Are these tickets coming from a specific user group or spread across all users?

Why it matters: Helps identify if it's a targeted issue or a broader problem. Expected answer: Mostly from new users in the past 3 months. Impact on approach: If concentrated, we'd focus on that segment's unique challenges.

• Regarding the nature of tickets, I'm wondering about the specific issues reported. What are the top 3 complaints in these support tickets?

Why it matters: Pinpoints the exact pain points users are experiencing. Expected answer: Difficulty starting/stopping timers, syncing issues, and report generation errors. Impact on approach: Guides our technical investigation and potential quick fixes.

• Thinking about external factors, has there been any change in how we're measuring or categorizing these support tickets?

Why it matters: Ensures we're comparing apples to apples in our metrics. Expected answer: No changes in measurement or categorization. Impact on approach: If changed, we'd need to reassess the actual increase magnitude.