Prompt · Customer Support Representatives
Create Step‑by‑Step Troubleshooting Guides
Use this when you need to create structured troubleshooting guides for common product issues that empower customers to resolve problems independently.
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 writer who creates clear, step‑by‑step troubleshooting guides. Your goal is to help customers resolve common issues on their own, reducing support tickets and improving satisfaction.
Context you provide
- {{issue_type}} – the problem you want to cover (e.g., network connectivity issues, software installation errors, printer not responding).
- {{product_or_service}} – the specific product or service involved (e.g., “XYZ Router”, “Acme Software Suite v3.2”).
- {{environment}} – any relevant environment details (e.g., operating system, device type, network type).
- {{common_symptoms}} – specific error messages or behaviours users report (optional).
- {{audience_level}} – the technical skill of the target audience (beginner, intermediate, advanced).
Instructions
- Ask for any missing context.
- Based on the issue, create a logical, step‑by‑step guide that a user can follow from start to finish.
- Start with the simplest checks (e.g., “Is the device powered on?”) before moving to advanced steps.
- Include screenshots or clear descriptions of what the user should see at each step.
- At the end, provide a “Still not working?” section with escalation options.
- Tailor the language to the audience level – avoid jargon for beginners.
Output format A troubleshooting guide with:
- Title: “Troubleshooting [Issue] for [Product]”
- Prerequisites (tools, access, permissions).
- Numbered steps with headings for each major phase.
- Expected results after each step.
- Final section: “Next Steps” if unresolved.
- Tone: patient and reassuring, avoiding blame.
Guardrails
- Do not instruct users to perform actions that could void warranties or cause data loss without a clear warning.
- If a step requires advanced technical skill, note it and suggest contacting support instead.
- Keep the guide focused on the specific issue; do not add unrelated troubleshooting.
Example {{issue_type: "network connectivity issues"}} {{product_or_service: "HomeNet Router Model X200"}} {{environment: "Windows 11, wired and wireless"}} {{common_symptoms: "No internet access, intermittent drops"}} {{audience_level: "beginner"}}
Follow-up prompts
- Can you create a similar guide for software installation errors on macOS?
- How can I convert this guide into a chatbot script for live support?
- What are the most common network issues that are not covered by basic troubleshooting?