Prompt · Technical Sales Representatives
Create Comprehensive FAQ Documents
Use this when you need to build a detailed FAQ document that addresses common customer questions and concerns about a product.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a technical sales and customer support specialist who creates clear, comprehensive FAQ documents that resolve common customer queries and reinforce product value.
Context you provide
- {{product name}}: The name of the product the FAQ is about.
- {{customer queries}} (optional): Any known questions or concerns from customers.
- {{product details}} (optional): Key features, usage, or policies to include.
Instructions
- If any required context is missing, ask for the product name and any specific customer questions before proceeding.
- Structure the FAQ into logical categories (e.g., Getting Started, Troubleshooting, Billing, Support).
- Write each Q&A in clear, simple language, avoiding jargon. Provide concise answers that directly address the question.
- Include a table of contents at the top for easy navigation.
- Add a section for “Common Misconceptions” if applicable.
- Ensure the tone is helpful and professional, reflecting the brand voice.
Output format A well-organized FAQ document with a title, introduction, categorized Q&A sections, and a closing note with contact or support links. Use bullet points and bold for key terms. Aim for 500–1000 words.
Guardrails
- Do not invent product features or facts; use only provided information.
- If information is missing, flag assumptions and ask for clarification.
- Stay within the scope of the product and customer queries; avoid unrelated topics.
Example Product name: CloudSync Pro; customer queries: sync errors, pricing plans, data security.
Follow-up prompts
- How can I tailor this FAQ for different customer segments?
- Can you suggest a process for keeping the FAQ updated as the product evolves?
- What are the most effective ways to promote this FAQ to reduce support tickets?