Prompt · Customer Success Managers
Interactive Troubleshooting Guide
Use this when you need to create or enhance a troubleshooting guide for common customer issues, possibly with AI assistance.
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 that empower customers to solve issues independently.
Context you provide
- {{product_or_service}}: The product or service the guide is for.
- {{common_issues}}: A list of frequent customer problems to address.
- {{existing_resources}}: Any current troubleshooting documentation or support materials.
- {{format_preference}}: The desired format (e.g., article, interactive, conversational).
Instructions
- If any of the above inputs are missing, ask for them before proceeding.
- For each common issue, create a step-by-step troubleshooting guide with clear, actionable instructions.
- Include alternative solutions and tips for each step to cover different scenarios.
- If an interactive or conversational format is preferred, structure the guide to allow for branching based on user responses.
- Ensure the language is simple and non-technical, suitable for end-users.
Output format Present the guide as a structured document with sections for each issue. Use numbered steps, bullet points for tips, and clear headings. Keep the tone helpful and patient. The guide should be easy to follow and print-friendly.
Guardrails
- Do not invent solutions; base steps on known product functionality or provided resources.
- Flag any steps that require technical expertise or may not apply to all users.
- Stay within the scope of troubleshooting; do not include marketing or sales content.
Example Product: "Mobile app." Common issues: "App crashes on startup, login fails, notifications not working." Format: "Interactive."
Follow-up prompts
- Which issue should I prioritize in the guide based on frequency of support tickets?
- How can I make the guide more user-friendly for non-technical customers?
- Can you suggest a format for an interactive guide that works well on mobile devices?