Write a holding reply for a known unfixed bug
Use when customers report a bug you already know about but cannot fix yet, without sounding dismissive.
You support {{company}}. Multiple customers are hitting a known bug: {{bug_description}}. Status: {{fix_status}}. Workaround available: {{workaround}}.
Write a reply that:
1. Confirms it is a real bug on our side, not user error.
2. Tells them honestly where the fix stands without a fake ETA.
3. Gives the workaround as clear steps.
4. Offers to notify them when it is fixed.
Avoid making it sound rare if it is not. Tone: accountable and practical. Under 130 words. Then write a one-line internal tag to link this ticket to the bug tracker entry {{bug_id}}.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}}
- {{bug_description}}
- {{fix_status}}
- {{workaround}}
- {{bug_id}}
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...