Create a Technical Troubleshooting Email for Customer Support Teams

Act as a technical support engineer for a [PRODUCT_TYPE] product. A customer named [CUSTOMER_NAME] has reported the following technical issue: [ISSUE_DESCRIPTION]. They are using [OPERATING_SYSTEM/PLATFORM] version [VERSION_NUMBER] and their account type is [ACCOUNT_TIER]. Write a clear, structured troubleshooting email that guides them through diagnosis and resolution. The email must be understandable by someone with a [TECHNICAL_SKILL_LEVEL] level of technical expertise. Structure the email as follows: 1. **Acknowledgment & Context**: Briefly acknowledge the issue and explain what likely causes it in plain language (1-2 sentences). 2. **Pre-Troubleshooting Checklist**: List 2-3 quick things the customer should verify before starting the main steps (e.g., software version, internet connection, browser cache). 3. **Step-by-Step Troubleshooting Guide**: Provide 4-6 numbered steps with: - Clear, action-oriented instructions (start each step with a verb) - Expected outcome after each step - What to do if the expected outcome doesn't occur - Screenshots or visual descriptions where helpful (describe what they should see) 4. **Alternative Solution**: If the primary troubleshooting path doesn't work, provide one alternative approach or workaround. 5. **Data Collection Request**: If the issue persists, specify exactly what diagnostic information you need from the customer — be precise (e.g., "Please send a screenshot of the error message" rather than "Send us more details"). 6. **Closing with Availability**: State your availability for a [SCREEN_SHARE/CALL] session if they prefer live assistance. Constraints: - Avoid technical jargon unless necessary; define any technical terms used - Use formatting (bold, numbered lists) for scannability - Include a subject line formatted as: "[TICKET_NUMBER] — Troubleshooting: [BRIEF_ISSUE]" - Total length: 200-350 words