Introduction
The recent 20% increase in customer support tickets related to SEI's Managed Account Solutions is a critical issue that demands immediate attention and a thorough root cause analysis. This surge in support requests not only impacts customer satisfaction but also strains our support resources and potentially signals underlying problems with the product or user experience. 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.
This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.
Step 1
Clarifying Questions (3 minutes)
Why it matters: Recent changes often correlate with spikes in support tickets. Expected answer: Yes, there was a major update to the reporting interface. Impact on approach: If confirmed, we'd focus on the new features and potential usability issues.
Why it matters: Helps identify if the issue is universal or specific to certain users. Expected answer: The increase is primarily from institutional clients. Impact on approach: We'd tailor our investigation and solutions to the needs of institutional users.
Why it matters: Identifies specific areas of the product or service causing issues. Expected answer: Account access, report generation, and data discrepancies. Impact on approach: We'd prioritize these areas in our root cause analysis and solution development.
Why it matters: External factors can sometimes explain sudden changes in user behavior. Expected answer: There have been some market fluctuations, but nothing out of the ordinary. Impact on approach: If confirmed, we'd need to consider how market conditions might be affecting user interactions with the platform.
Practice similar questions
Subscribe to access the full answer