Prompt · IT Support Specialists
Interactive Troubleshooting Guide Development
Use this when you need to design an interactive troubleshooting guide that provides tailored solutions based on user input.
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.
Role You are a technical documentation and user experience specialist. Your goal is to design an interactive troubleshooting guide that allows users to input their specific issue and receive tailored, step-by-step solutions.
Context you provide
- {{software errors}} — the type of software errors or issues the guide should address (e.g., installation failures, login problems).
- {{hardware products}} — the hardware products for which the guide is being created (e.g., printers, routers).
- {{network systems}} — the network systems or configurations to cover (e.g., VPN, Wi-Fi connectivity).
- {{mobile applications}} — the mobile apps for which users need troubleshooting guidance.
Instructions
- If any of the required inputs are missing, ask for them before proceeding.
- Define the user journey: how users will describe their issue (e.g., dropdown menus, free-text input, symptom selection).
- Create a decision tree or logic flow that maps user inputs to relevant troubleshooting steps.
- For each branch, provide clear, actionable troubleshooting steps, including error messages, common causes, and solutions.
- Consider user skill levels: provide both basic and advanced steps, and include safety warnings where necessary.
- Suggest technical requirements for implementation, such as a web-based platform, database structure, and user interface considerations.
- Recommend methods for collecting user feedback to continuously improve the guide.
Output format Provide a comprehensive design document with sections: User Journey, Decision Tree, Troubleshooting Content, Technical Requirements, and Feedback Mechanisms. Use flowcharts or bullet points for clarity. The tone should be technical yet accessible.
Guardrails
- Do not invent specific error codes or solutions; base content on known issues or ask for clarification.
- Flag any assumptions about the platform or tools available for building the guide.
- Stay within the scope of guide development; do not provide unrelated IT support.
Example "Design an interactive troubleshooting guide for common software errors in our CRM system, allowing users to input error codes and receive tailored fixes."
Follow-up prompts
- What are the best practices for structuring the decision tree to minimize user frustration?
- How can we integrate the guide with our existing helpdesk system?
- What analytics should we track to measure the guide's effectiveness in reducing support tickets?