Browse Problems
Discover prompting challenges and the community's best solutions.
Identify feature requests that multiple customers are asking for
5 customers this week mentioned 'bulk export'. 3 mentioned 'dark mode'. Need to aggregate these requests and surface: 'Bulk export: 5 requests this week, 23 total, high-value customers'.
Feature Request Aggregator
Example output
Route tickets to the right team based on technical complexity
Tier 1 support can handle password resets. Tier 2 handles API errors. Engineering handles database corruption. Need routing that understands: 'Error 500 when calling /api/webhooks' goes to engineering, not tier 1.
Technical Complexity Router
Example output
Extract actionable bug reports from rambling customer messages
Customer writes 3 paragraphs about their frustration. Buried in there: 'When I click Export on the Reports page, nothing happens'. Need to extract: feature, action, expected result, actual result - and ignore the emotional venting.
Bug Report Extractor
Example output
Generate context-aware auto-responses that don't sound robotic
Customer asks: 'Why was I charged twice?' Auto-response needs to: (1) acknowledge the specific issue, (2) explain next steps, (3) sound human. Generic 'We received your ticket' responses make things worse.
Context-Aware Auto-Response Generator
Example output
Detect SLA breach risk before the deadline hits
SLA says 'respond within 4 hours'. It's been 3 hours and the ticket is still unassigned. Need alerts that predict: 'This ticket will breach SLA in 45 minutes unless someone picks it up now'.
SLA Breach Predictor
Example output
Classify support tickets by churn risk, not just sentiment
Sentiment analysis says 'negative', but that's not enough. Need to know: Is this 'frustrated but fixable' or 'already decided to cancel'? Looking for prompts that detect churn signals like 'looking at alternatives', 'cancellation policy', or 'export my data'.
Churn Risk Ticket Classifier
Example output
Calculate lifetime value (LTV) that accounts for actual churn patterns
Generic LTV formulas assume constant churn. Real SaaS has: high churn in month 1, stabilization by month 6, enterprise customers who never churn. Need LTV calculations that use cohort-specific churn curves, not averages.
Cohort-Based LTV Calculator
Example output
Identify tax-deductible expenses from mixed personal/business transactions
Indie founders use personal cards for business expenses. Need to scan transactions and flag: 'This $47 Uber to the airport for a conference is deductible' vs 'This $47 Uber to the grocery store is not'.
Business Expense Deduction Identifier
Example output