Explain browser console logs to everyday users
Get step-by-step, non-intimidating email templates that guide non-technical customers through capturing console logs and screen recordings.
You getEmail Subject Line Options, ready-to-Send Email Template and quick Troubleshooting Tip
Prompt
You are a customer experience writer who specializes in technical support communication. Create a reusable, non-intimidating email template explaining how non-technical customers can record a short screen video and capture browser console error logs.
- Use warm, patient, everyday language; explain briefly why these logs help solve their issue faster.
- Give exact, numbered instructions for the most common browsers (Chrome, Edge, Safari).
- Recommend free, zero-install tools for screen recording (e.g., built-in OS tools or free web recorders).
- Reassure the customer that these steps contain no personal passwords or financial details.
Output format:
- Email Subject Line Options (2 choices)
- Ready-to-Send Email Template (with clean section breaks for screen recording and console capture)
- Quick Troubleshooting Tip (one line on what to do if they get stuck following the steps)Example output
Copy this prompt directly into ChatGPT, Claude or Gemini without edits. You can follow up by asking to adapt the instructions specifically for Mac or Windows users if your customer base is heavily skewed.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Draft friendly reproduction questions for vague bugs
Generate painless, jargon-free troubleshooting questions to help non-technical users share the exact steps engineers need to reproduce bugs.
Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.
Handle a product warranty claim with clear next steps
Draft a courteous, complete customer support reply that requests required warranty proof and outlines clear timeline expectations.
Send a post-outage all-clear summary to users
Write a definitive post-incident email confirming full service recovery, outlining immediate next steps, and rebuilding user trust.
Turn vague feature requests into actionable workflow feedback
Extract underlying user problems, manual workarounds, and workflow impact from brief customer feature requests.
Explain a prorated bill or plan change clearly
Turn confusing mid-cycle invoice numbers into a calm, line-by-line explanation a customer can read in two minutes. Perfect for diffuse billing tickets.
- Turn technical release notes into plain customer updates
- Write a post-purchase email that cuts support tickets
- Analyze Customer Cancellation Reasons to Surface Preventable Churn Fixes
- Write a Customer Troubleshooting Guide for Specific Error Codes
- Draft a Feature Deprecation Notice for Your Customers
- Write Executive Escalation Email for At-Risk Customers