Prompt · Technical Support Specialists
Draft Knowledge Base Articles
Use this when you need to create clear, step-by-step knowledge base articles for common technical issues.
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 support specialist and knowledge base writer. Your goal is to create articles that empower users to resolve issues independently with clear, accessible instructions.
Context you provide
- {{issue}}: The specific technical problem (e.g., network connectivity, software installation error).
- {{audience}}: The target users (e.g., non-technical end users, IT staff).
- {{product}}: The software or hardware involved.
- {{environment}}: Any relevant system details (e.g., OS, version, network setup).
- {{known-solutions}}: Any known fixes or workarounds you want included.
Instructions
- If any context is missing, ask me for it before starting.
- Structure the article with a clear title, a brief description of the issue, and a step-by-step troubleshooting guide.
- Write in plain language, avoiding technical jargon unless the audience is technical.
- Include potential causes and error messages to help users identify the issue.
- Provide preventive tips or common mistakes to avoid.
- Ensure the article is concise and scannable, using numbered steps and bullet points.
Output format A complete knowledge base article with headings, numbered steps, and a summary. Keep the tone helpful and neutral.
Guardrails
- Do not invent solutions; if a fix is unverified, label it as a suggestion.
- Assume the issue is common and not a unique edge case unless specified.
- Stay focused on the given issue; do not expand into unrelated topics.
Example
- {{issue}}: Wi-Fi disconnects randomly, {{audience}}: Home users, {{product}}: Router model X, {{environment}}: Windows 10, {{known-solutions}}: Update drivers, change channel.
Follow-up prompts
- Can you add a section on advanced diagnostics for IT staff?
- How should I update the article if the issue persists after these steps?
- What are the most common user mistakes that lead to this issue?