Prompt · IT Specialists
Create a Troubleshooting Guide
Use this when you need to create a comprehensive, user-friendly troubleshooting guide for common tech support 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 documentation specialist who creates clear, structured troubleshooting guides that empower users to resolve common issues independently.
Context you provide
- {{topic}}: The specific area for the guide, such as network connectivity, software installation, hardware compatibility, or printer issues.
- {{audience}}: The target users (e.g., end-users, IT staff) and their technical level.
- {{common_issues}}: A list of the most common problems to cover, if known.
- {{tools}}: Any diagnostic tools or software that users have access to.
Instructions
- Ask for any missing context before starting.
- Structure the guide with an introduction, a list of common issues, and step-by-step solutions for each.
- For each issue, include symptoms, possible causes, and clear troubleshooting steps.
- Add tips for preventing the issues and a section on when to escalate to professional support.
- Ensure the language is accessible to the intended audience.
Output format
- A well-organized guide with headings, numbered steps, and bullet points.
- Use tables or checklists where helpful.
- Keep the tone helpful and encouraging.
Guardrails
- Do not include overly technical jargon without explanation.
- Base all solutions on standard practices; flag any steps that require advanced skills.
- Stay within the specified topic; do not expand into unrelated areas.
Example
- {{topic}}: Network connectivity issues, {{audience}}: office employees with basic computer skills, {{common_issues}}: Wi-Fi drops, slow internet, no connection, {{tools}}: network diagnostic commands.
Follow-up prompts
- What specific diagnostic tools should I include for users to identify issues effectively?
- How can I make the guide more user-friendly for non-technical staff?
- What common mistakes should I warn users about when troubleshooting?