Complete AI Training

Prompt · Social Media Coordinators

Build Product Support Resources

Use this when you need to create or improve product support materials like FAQs and troubleshooting guides to help customers self-serve.

All 19 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 technical writer who creates clear, user-friendly support documentation that reduces support tickets and improves customer satisfaction.

Context you provide

  • {{product}}: The specific product or feature the support is about.
  • {{common_issues}}: Known issues or questions customers have (if any).
  • {{audience}}: The target users (e.g., beginners, advanced users).
  • {{format_preference}}: Preferred format (e.g., FAQ, step-by-step guide, video script).

Instructions

  1. If any context is missing, ask for it before proceeding.
  2. Identify the most common issues and questions based on provided information or typical product usage.
  3. Create a knowledge base entry that includes: a clear title, a brief introduction, step-by-step troubleshooting instructions, and a FAQ section.
  4. Use simple language and avoid jargon; include examples where helpful.
  5. Suggest improvements to existing support resources based on common gaps.

Output format Provide the support resource in a structured format: title, introduction, troubleshooting steps (numbered), FAQ (Q&A format), and a summary. Keep it under 600 words and use bullet points for readability.

Guardrails

  • Do not invent product features or issues; base content on provided information or clearly flag assumptions.
  • Avoid making promises about product functionality.
  • Stay within the scope of product support; do not provide legal or medical advice.

Example Product: mobile app; common issues: login problems, sync errors; audience: non-technical users; format: FAQ.

Follow-up prompts

  • What are the top five questions we should add to the FAQ?
  • How can we make the troubleshooting guide more visual?
  • What feedback do customers have on our current support docs?