Design a Troubleshooting Guide
ChatGPT Prompt
Write a troubleshooting guide for {product} covering the issues that generate the most support volume. Organise by the symptom the user observes, not by the underlying cause — users search for what they see. For each symptom give: the likely causes ordered by frequency, diagnostic steps that narrow it down, the fix for each cause written as numbered actions with expected results, how to confirm it worked, and when to stop and contact support. Include the information a user should gather before contacting support so the first reply can actually resolve it. Write at a level that assumes no product jargon, add screenshots where a step is ambiguous, and keep each path under seven steps.
💡 Pro Tip: Replace placeholders in [BRACKETS] with your specific information for best results.
How to Use This Prompt
- 1Click the copy button above to copy the prompt to your clipboard
- 2Open ChatGPT, Claude, or your preferred AI assistant
- 3Paste the prompt and replace any [PLACEHOLDER TEXT] with your specific details
- 4Review the AI's response and iterate if needed for better results
Related Tags
Related Prompts
Create a Customer Feedback Survey
Design a customer feedback survey for a {business_type} measuring {objective}. Choose and justify the primary metric — CSAT for a specific interaction, CES for effort, NPS for relationship — since they answer different questions and are routinely confused. Keep it to 5–7 questions with a consistent scale, one open question that produces specifics ('what was the one thing we could have done better?'), and no double-barrelled or leading wording. Specify trigger timing, channel, and the response-rate expectation. Add the analysis plan including segmentation, the follow-up loop for detractors with a target contact time, and the reporting format. State plainly how to avoid surveying the same customers so often that the data skews toward the tolerant.
Develop a Service Level Agreement (SLA)
Draft a support SLA for a {service_type} serving {customer_tier} customers. Define severity levels with unambiguous examples so classification is not argued at the worst moment. For each severity, set first-response and resolution targets, and be careful to commit to workaround times rather than fix times for complex issues. Specify support hours and timezone coverage, the measurement method, exclusions (customer-caused, third-party, scheduled maintenance, force majeure), reporting cadence, and remedies for breach — usually service credits, with the claim process stated. Add internal targets set tighter than the external commitment, and flag every clause where an over-promise would be expensive at scale.
Write Empathy Statements for Difficult Situations
Write empathy statements for support agents handling eight difficult situations: a customer who has repeated themselves to several agents, a significant financial loss caused by your error, a missed deadline that damaged their business, a long outage, an angry customer who is factually wrong, a distressed customer, a request you must refuse, and a genuine company failure. For each give two or three statements that acknowledge the specific impact rather than offering generic sympathy, and the sentence that follows — because empathy without a next step reads as stalling. List the phrases to eliminate: 'I understand how you feel' when you cannot, 'calm down', and any apology hedged with 'if'. Add guidance on apologising properly where liability is a concern.
Write Response Templates for Common Inquiries
Write support response templates for a {business_type} covering the ten highest-volume enquiries: order status, delivery delay, refund request, how to cancel, billing question, password or access problem, product not working as expected, feature request, comparison with a competitor, and a request that policy does not allow. Each must answer the question in the first two lines before any pleasantries. Mark personalisation points explicitly so replies do not read as copy-paste. For each give the tone, the linked help article, and the escalation trigger. Add the rule that a template is a starting point, and a monthly review to find which templates generate the most follow-up replies — the signal that the answer is unclear.
Create an Escalation Procedure Guide
Write an escalation procedure for a {support_team_size} support team at a {business_type}. Define tiers with the capability and authority of each, and the specific triggers for moving between them — issue type, time elapsed, customer tier, financial exposure, legal or safety implication, and explicit customer request. State clearly that an agent is never penalised for escalating correctly. Cover: the handover format so the customer never re-explains, ownership rules (the original agent stays accountable for the outcome), the response and resolution targets per tier, the after-hours path, and the immediate-escalation categories such as safety, legal threat, data breach and press enquiry. Add a de-escalation path for issues wrongly escalated.
Develop a Customer Complaint Resolution Process
Design a complaint resolution process for a {business_type}. Define the stages: acknowledge within a stated time, investigate with a checklist of what must be established, decide against published remedy tiers so outcomes are consistent between agents, communicate, and follow up to confirm the resolution held. Give agents a decision matrix showing what they can resolve without approval — and set that threshold genuinely high, because escalation for small amounts costs more than the amounts. Cover: the language that de-escalates versus the phrases that inflame ('unfortunately', 'as per our policy', 'you should have'), documentation requirements, root-cause capture so recurring complaints reach the team that can fix the cause, and the regulatory complaint handling that applies in {jurisdiction}.