Knowledge Management

FAQ Documentation Prompt

Every entry a "## Question?" heading with a self-contained answer — FAQs grouped by topic, phrased the way users actually ask.

Overview

FAQs fail when they're written from the company's perspective: headings nobody would type, answers that reference other answers. This setup generates FAQ pages with the format forced at the type level — every entry is a "## Question?" heading phrased exactly as a user would ask it, followed by a self-contained answer with no "see above" — organized into topic sections (General, Getting Started, Troubleshooting, Billing & Plans). Code blocks are allowed for the how-do-I questions that need them.

Workflow

Feed the question themes
List the questions (or ticket patterns) below the prompt; the page comes back grouped and formatted.
Check the question phrasing
"Phrase each heading exactly as a user would ask it" — headings users would type are headings search engines reward.
Enforce self-containment
No "see above" means every answer survives being deep-linked — which is how FAQ answers are actually consumed.

Why This Works

The "## Question?" format is forced by a type rule, not left to chance
Self-contained answers match deep-link consumption
Topic grouping keeps hundred-question FAQs navigable

Best for

Support teams converting ticket patterns into docs
FAQ pages that double as SEO surface
Products whose users search before they ask

Not for

Classifying incoming questions into categories — that's the Data Classification Prompt
Summarizing support conversations — that's the Structured Summary Prompt

Use cases

Building the product FAQ from support ticket themes
Keeping every answer self-contained and linkable
Phrasing questions the way users type them into search

Customize This Resource

Opens this setup in Markdown Output Builder. Generate to get the full markdown prompt — then adjust the sections, table rules, and consistency level.

Open in Markdown Output Builder

Prompt Template

TASK
Build the product FAQ page from common customer questions.
Produce a new markdown document — there is no source text to summarize.

DOCUMENT
The document is an FAQ.
- Format every entry as a "## Question?" heading followed by its answer paragraph.
- Phrase each heading exactly as a user would ask it.
- Keep every answer self-contained — no "see above".

DOCUMENT STRUCTURE
Start with one "# " title line, then use exactly these sections, in this order:
## General
Basic questions about what it is.
## Getting Started
Setup and first-use questions.
## Troubleshooting
Something-went-wrong questions.
## Billing & Plans
Pricing and account questions.

MARKDOWN RULES
- One "# " title at the top; every section below it is a "## " heading.
- Use markdown lists for enumerations — no walls of prose.
- No HTML tags — pure markdown.

TABLE RULES
- Do not use tables — present comparisons as nested bullet lists.

CODE RULES
- Use fenced code blocks with a language tag when code clarifies the point.

CONSISTENCY RULES
- Use every section defined above, in the order given.
- Do not add new top-level sections — put extra material inside the closest existing section.

OUTPUT RULES
- Return only the markdown document — no preamble, no closing commentary.
- Start directly with the "# " title line.
- Do not wrap the document in code fences.

Related Resources

Explore more resources that work well with this one.