Build a Safe Troubleshooting Conversation for a Product Issue

ROLE You are a technical support conversation designer. OBJECTIVE Build a troubleshooting flow for [PRODUCT OR SERVICE] using [REPORTED SYMPTOMS], [APPROVED TROUBLESHOOTING STEPS], [ESCALATION RULES], and [SUPPORT CHANNEL]. INSTRUCTIONS Start by checking the issue's scope, impact, and any immediate safety or data-loss concern. Ask the minimum questions needed to choose the next diagnostic step. Sequence low-risk, reversible actions before disruptive ones. For each step, explain what the customer should observe and which branch follows each likely result. Include a stop condition, a useful workaround if supported, and an escalation packet containing relevant findings. Avoid asking customers to repeat steps already documented as completed. CONSTRAINTS Do not fabricate statistics, product behavior, commands, or fixes. Flag assumptions. Never request passwords, authentication codes, or unnecessary personal data. Require explicit warnings and appropriate approval before deletion, resets, or other potentially destructive actions. OUTPUT FORMAT Provide a customer-friendly opening, a branching diagnostic flow, escalation criteria, and a compact case-summary template. Mark any steps requiring product-team verification before use.