Build a Step-by-Step Troubleshooting Guide for Customer Issues

You are a senior customer support engineer with expertise in creating diagnostic troubleshooting guides. Build a comprehensive troubleshooting guide for the following issue: [ISSUE DESCRIPTION e.g., 'Customer cannot log into their account']. This guide is for [AUDIENCE e.g., support agents / end-user customers / IT administrators] using [PRODUCT/SERVICE NAME] on [PLATFORM(S) e.g., Web, iOS, Android, Windows]. Follow this detailed framework: 1. **Issue Title**: Write a clear, descriptive title that matches how [AUDIENCE] would describe the problem. 2. **Symptoms**: List 3-5 specific symptoms or error messages a user might experience, such as: - Error codes: [COMMON ERROR CODES if known] - Visual indicators (e.g., spinning loader, blank screen) - Behavioral descriptions (e.g., 'page redirects to...') 3. **Root Cause Overview**: Briefly explain 2-4 possible root causes for this issue in plain language. Rank them from most common to least common. 4. **Diagnostic Decision Tree**: Create a structured decision-tree flow using this format: - Step 1: Ask a diagnostic question (e.g., 'Is the user seeing error code [CODE]?') - If YES → proceed to Solution A - If NO → proceed to Step 2 - Continue for at least 4-6 decision points covering the major root causes. 5. **Solutions**: For each identified root cause, provide a detailed solution that includes: - A descriptive label (e.g., 'Solution A: Clear Browser Cache') - Numbered sub-steps (3-7 steps each) - Platform-specific variations where relevant for [PLATFORM(S)] - Expected resolution time - Verification step to confirm the issue is resolved 6. **Escalation Criteria**: Define clear conditions under which this issue should be escalated, including: - When to escalate to [TIER 2/ENGINEERING TEAM] - What information to collect before escalating (e.g., logs, screenshots, account ID) - SLA or priority level recommendation: [SLA GUIDELINES] 7. **Prevention Tips**: Include 2-3 proactive recommendations customers can follow to avoid encountering this issue in the future. 8. **Internal Notes** (if for support agents): Add any context about known bugs, recent deployments [RECENT CHANGES], or temporary workarounds that are not customer-facing. Format the guide with clear headings, numbered lists, and visual separators. Use bold for key actions and italics for notes or warnings. Target length: 800-1200 words.