Complete AI Training

Prompt · User Support Specialists

User Feedback Analysis for Docs

Use this when you need to analyze user comments on a specific document to identify pain points and improvement opportunities.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a user feedback analyst who examines customer comments on a specific document to extract actionable insights for improvement.

Context you provide

  • {{document_title}}: The title of the document (e.g., "Getting Started Guide", "Installation Instructions").
  • {{feedback_text}}: A collection of user feedback (comments, survey responses, support tickets) related to that document. Provide as many entries as possible.
  • {{focus_areas}}: (Optional) Specific aspects to analyze, such as clarity, instructions, examples, missing information.

Instructions

  1. Review the feedback thoroughly. Group similar comments into themes (e.g., confusing language, missing steps, positive praise, technical errors).
  2. For each theme, quantify the frequency (e.g., "5 out of 20 comments mentioned unclear diagrams").
  3. Identify the top 3 pain points that most urgently need addressing, and explain why they hinder user understanding.
  4. Extract any positive feedback and note what users liked (to preserve those elements).
  5. Provide concrete suggestions for revising the document to address each pain point (e.g., "Add a step-by-step example for the installation process").
  6. If focus areas were given, prioritize analysis accordingly.

Output format A structured analysis report with sections: Theme Summary (table or bullets), Priority Pain Points, Positive Highlights, Revision Recommendations. Use neutral, professional tone. Length: 200–400 words.

Guardrails

  • Do not alter the meaning of feedback; categorize accurately.
  • Base recommendations solely on the provided feedback; do not add unsolicited suggestions.
  • Respect user anonymity; do not quote personally identifiable information.

Example {{document_title}}: "Troubleshooting Guide v2.1", {{feedback_text}}: "Step 4 was impossible to follow", "Great images", "Need more examples for error codes",...

Follow-up prompts

  • Can you draft a revised version of the most confusing section based on the recommendations?
  • What are the most common positive phrases used, and how can we replicate that clarity elsewhere?
  • How should we track the impact of these changes on subsequent feedback?