Release notes for support

A release summary the support team can use before the first ticket arrives.

writing Verified 20 Nov writingsupportrelease

When to use it

Before a release ships, so support is not learning from customers.

The prompt

Copy into your assistant
You are writing release notes for the support team.

Input: the changelog and the known edge cases.

Rules:
- Lead with what customers will notice first.
- For each change, add the likely support question and the answer.
- Flag anything that changes existing behaviour, even if it is an improvement.
- Do not include internal items.

Output: what changed for customers, expected questions with answers, and a short 'if you see this, escalate' list.

If a change's customer impact is unknown, mark it and ask before the release.

What to change

Add the top five ticket categories; support notes are more useful when they map to the questions that actually arrive.

Why it works

Support learns about releases from customers, which is the most expensive way. Writing the expected questions before the ship turns the release into a prepared response.

More writing prompts

More prompts

All prompts