Build a new-customer FAQ from recurring support questions
New customers ask the same questions in their first 30 days, and support teams answer them repeatedly. This prompt turns a list of those recurring questions into a structured FAQ that can live in onboarding emails or a help center.
You are a support content writer. Convert the following list of frequently asked questions from new customers into a polished, scannable FAQ document suitable for an onboarding email sequence or help center page.
Recurring questions collected from tickets (paste as a list): {{RECURRING_QUESTIONS_LIST}}
Product or feature area these questions relate to: {{PRODUCT_AREA}}
Target audience for the FAQ: {{TARGET_AUDIENCE}} (e.g., small business owners with no technical background, enterprise IT admins)
Tone: {{TONE_GUIDELINE}} (e.g., warm and simple, professional and direct)
Produce the FAQ using these steps:
1. Group related questions into 2 to 4 logical sections with short section headers.
2. For each question, write a plain-language answer of 2 to 4 sentences. Prioritize what the customer should do over how the system works internally.
3. Where an answer involves steps, format them as a numbered list.
4. Flag any questions whose answer depends on account type, plan tier, or configuration — mark these with a note like 'This depends on your plan — check your account settings or contact support.'
5. After the FAQ body, list up to 3 questions that appeared in the ticket data but could not be answered without more product information — so the team knows what to fill in later.
Edge cases: If the question list contains contradictory answers (suggesting the product behavior is inconsistent), note the conflict rather than inventing a single answer. {{RECURRING_QUESTIONS_LIST}}{{PRODUCT_AREA}}{{TARGET_AUDIENCE}}{{TONE_GUIDELINE}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{RECURRING_QUESTIONS_LIST}}{{PRODUCT_AREA}}{{TARGET_AUDIENCE}}{{TONE_GUIDELINE}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Writesonic
$16/moCheaper Jasper alternative with built-in fact-checking.
Writesonic targets the same use cases as Jasper at a lower price point. Botsonic (their chatbot product) and Audiosonic (voice) extend the suite.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.