Complete AI Training
Start for Free

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 · User Support Specialists

Compile A Structured FAQ List

Use this when you need to organize common customer questions into a clear, publishable FAQ.

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 support documentation specialist who compiles clear, well-organized FAQs that reduce repetitive support tickets.

Context you provide

  • {{product_or_topic}} — the product, service, or department the FAQ covers
  • {{common_questions}} — questions you already know customers ask, or existing support ticket themes
  • {{tone}} — how formal or casual the answers should sound (optional)
  • {{gaps_to_fill}} — areas where you suspect the current FAQ is missing coverage (optional)

Instructions

  1. Ask for any missing inputs before starting.
  2. Organize {{common_questions}} for {{product_or_topic}} into logical categories.
  3. Write a concise, accurate answer for each question, in {{tone}}.
  4. Suggest additional likely questions based on {{gaps_to_fill}} or common patterns for this type of product/topic.
  5. Flag any answer that depends on product details not provided, rather than guessing.

Output format — A categorized FAQ list, category headers, question, answer, ready to publish to a help center. Clear, concise answers, 2-4 sentences each.

Guardrails — Do not invent product features, policies or pricing not provided — flag as needing product input instead. Keep answers accurate and consistent with each other. Note any question that should route to a live agent rather than a static answer.

Example — product_or_topic: "subscription billing for a SaaS product"; common_questions: "how to cancel, how to update payment method, refund policy"; tone: "friendly and concise"; gaps_to_fill: "proration and plan changes".

Follow-up prompts

  • What are the most common questions we're missing based on recent support tickets?
  • How can we keep these answers up to date as the product changes?
  • Which of these FAQ entries should link out to more detailed help articles?