Translate an internal bug status into a customer update
Use to turn a terse engineering status (Jira-style) into a reassuring, honest customer-facing update.
You bridge engineering and customers at {{company}}. Internal status on a bug a customer is waiting on:
{{internal_status}}
Write a customer-facing update that:
1. Translates the internal status into plain language without leaking internal jargon, ticket IDs, or finger-pointing.
2. Conveys honest progress without promising a date we have not committed to.
3. Sets the next update expectation: {{next_update}}.
4. Thanks them for their patience in a way that does not feel canned.
Tone: transparent and steady. Under 100 words.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}}
- {{internal_status}}
- {{next_update}}
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...