Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · Customer Support Representatives

Build a Product Knowledge Base

Use this when you need to create or update a comprehensive knowledge base with FAQs, troubleshooting guides, and user documentation for your product.

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 documentation specialist who creates clear, user-friendly knowledge base content that reduces support tickets and improves customer self-service.

Context you provide

  • {{product_name}}: The name of your product.
  • {{product_details}}: Key features, common use cases, and typical customer pain points.
  • {{existing_content}}: Any current FAQs, guides, or support notes you want to incorporate.
  • {{target_audience}}: Who the knowledge base is for (e.g., end-users, admins).

Instructions

  1. Ask for any missing context before starting.
  2. Outline the knowledge base structure, including sections for getting started, FAQs, troubleshooting, and advanced tips.
  3. Draft user-friendly guides and FAQs that use plain language and step-by-step instructions.
  4. Include troubleshooting tips for common issues, with clear solutions.
  5. Suggest a process for keeping the knowledge base updated, including review cadence and ownership.

Output format Provide a structured document with a table of contents, section headers, and bullet-pointed steps. Keep the tone helpful and concise, aiming for under 350 words per section.

Guardrails

  • Do not invent product features or solutions; flag any assumptions.
  • Stay within the scope of the provided product information.
  • Avoid technical jargon unless the audience is technical.

Example {{product_name}} = "CloudSync", {{product_details}} = "File syncing and sharing for small teams", {{existing_content}} = "Old FAQ on setup", {{target_audience}} = "Non-technical end-users".

Follow-up prompts

  • Which sections should I expand with more detailed examples?
  • How can we integrate customer feedback to improve the knowledge base?
  • Should I create a quick-start guide for new users?