Turn vague feature requests into actionable workflow feedback
Extract underlying user problems, manual workarounds, and workflow impact from brief customer feature requests.
You getCore Friction Analysis, customer Follow-up Email and product Ops Ticket
Prompt
Act as a customer support lead and product operations specialist. Analyze customer feature requests to uncover the root problem behind what they asked for.
- Identify the core job-to-be-done and the probable reason they requested this specific solution.
- Determine the manual workaround or friction the user is likely enduring right now.
- Draft a warm, two-question reply to the user asking clarifying questions about their actual workflow without committing to building the request.
- Summarize the insight into an internal ticket format for product teams.
Output format:
1. Core Friction Analysis (underlying problem vs. surface request)
2. Customer Follow-up Email (concise, polite, non-committal)
3. Product Ops Ticket (Summary, User Goal, Current Blocker, Impact Level)
Customer request is pasted below:Example output
Paste your customer's email, chat transcript, or ticket snippet directly below this prompt in ChatGPT, Claude or Gemini. If the initial message is extremely brief, ask the model to generate two distinct hypotheses about what the user might be trying to accomplish.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Decline an Off-Roadmap Feature Request with Workarounds
Drafts an empathetic, transparent customer response that explains why a feature is not planned and provides two actionable workarounds using existing tools.
Find the Themes in Customer Feedback and CSAT Comments with Real Counts
Returns a theme table with exact counts, a verbatim quote from your data, likely root cause and suggested owner, plus top actions and data gaps.
Triage pasted support tickets by urgency and topic
Sort raw incoming support tickets into prioritized queues by urgency, root issue, and recommended first-touch actions.
Analyze customer sentiment beneath translated tickets
Reveal hidden frustration, urgency, and underlying demands that machine translation tools flatten or misinterpret in foreign-language tickets.
Draft friendly reproduction questions for vague bugs
Generate painless, jargon-free troubleshooting questions to help non-technical users share the exact steps engineers need to reproduce bugs.
Explain browser console logs to everyday users
Get step-by-step, non-intimidating email templates that guide non-technical customers through capturing console logs and screen recordings.