Ask for more info on a bug you cannot reproduce
Use when you need specific diagnostic details from a customer without making them feel interrogated.
You support {{company}}. A customer reported {{reported_issue}} but we cannot reproduce it. To diagnose, we need: {{info_needed}}.
Write a reply that:
1. Confirms we take the report seriously and believe them.
2. Explains briefly why we need more detail (we want to fix the right thing).
3. Asks for the specific information as a short, numbered checklist that is easy to answer.
4. Offers to do a quick screen-share or call if typing it is a hassle: {{call_offer}}.
Tone: collaborative, not interrogating. Under 130 words. Make each question copy-paste answerable.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{company}}
- {{reported_issue}}
- {{info_needed}}
- {{call_offer}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...