Analyze Support Cases to Build a Product Roadmap

Explore your support cases by product line and identify where you should focus your development efforts to have the greatest impact on customers.

QUERY:

Pull all support cases for [PRODUCT_NAME] from [TIME_PERIOD]. Do not limit yourself to tops, twenties, and tens, but actually pull all the data for [PRODUCT_NAME] support cases.

Goal: Establish a comprehensive baseline by gathering all support cases for a specific product to understand overall volume and identify initial patterns.

QUERY:

Focus on specific feature improvements. What [FEATURE_NAME] are they related to? What are the configurations by [FEATURE_NAME]? Give me example tickets and the number of tickets per configuration.

Goal: Identify specific feature problems that can be resolved through simple default setting changes, focusing on high-volume, low-complexity issues.

QUERY:

For [FEATURE_NAME], export an example case for [FEATURE_NAME] [SPECIFIC_ISSUE], show the problem, identify the exact fix, and outline the development work required to update it.

Goal: Transform identified problems into actionable development specifications with effort estimates and business impact quantification.

QUERY:

Going back to your original analysis, rank all work from low effort/high impact, medium effort/high impact, and high effort/high impact.

Goal: Organize all identified opportunities into an actionable roadmap that balances development effort against business impact.

Teams:

Product Management

Sources:

Dynamics 365 HubSpot Pipedrive Salesforce Zoho CRM

Watch:

Ready to get started?

Download an MCP Server
Related Prompts:

Sales Data Hygiene & Product Roadmap Intelligence

View Prompt

Database Table Mapping and Relationship Discovery

View Prompt

Competitive Win/Loss Analysis by Quarter

View Prompt