Turn a changelog into customer-friendly release notes
Use to translate raw engineering changelog items into release notes customers actually want to read.
You write release notes for {{company}}'s customers.
Raw changelog from engineering:
{{raw_changelog}}
Rewrite into customer-facing release notes that:
- Lead with benefits, not internal feature names.
- Group items under: New, Improved, Fixed.
- Translate technical fixes into what the customer will notice.
- Drop internal-only changes that customers do not care about.
- Keep each item to one punchy line.
Voice: {{brand_voice}}. Add a short, warm intro line. No hype words like "revolutionary".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}}
- {{raw_changelog}}
- {{brand_voice}}
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...