Announcement examples — new features, product updates and more
Copy-paste examples for the announcements a product or a shop actually has to write: a new feature, a product update roundup, a price change and a temporary closure — plus where each one belongs in your UI, so it gets read.
- New feature announcement example
- Product update announcement example
- Price change announcement example
- Temporary closure / maintenance example
- Where to show announcements — the UI
New feature announcement example
Lead with what the reader can now do — not with how excited you are. Excitement is the reader's job; yours is to give them a reason.
## You can now schedule posts Write an announcement today, publish it next Monday. Pick a date and time when you save, and the post goes live on its own — no reminder needed. Scheduling is on every plan, starting now. You'll find it next to the publish button. Questions? Get in touch — we read everything.
The pattern: outcome in the title, one paragraph of how, one line of who gets it and where to find it. Everything else — the roadmap that led here, the internal name, the architecture — belongs somewhere users don't have to go.
Product update announcement example
For a batch of smaller changes, group them and let the list show momentum. One announcement per tiny change trains readers to ignore you.
## March updates **New** - Schedule posts to publish later - Pin an announcement to the top of your page **Improved** - Image uploads are about twice as fast - The editor keeps your draft if you close the tab **Fixed** - Dates were off by one day in some time zones No action needed for any of these — they're already live.
Price change announcement example
The one announcement where completeness beats brevity. Say what changes, when, for whom, and what happens if the reader does nothing — in that order.
## Pricing update on 1 May From 1 May, the Studio plan changes from $19 to $24 per month. **If you're already on Studio** — nothing changes until your first renewal after 1 May, and we'll email you two weeks before that renewal. **If you're on the free plan** — nothing changes at all. **Why** — storage and image delivery costs have roughly doubled since we set the current price. This keeps the service sustainable without ads. Not happy about it? Email us at support@example.com — we answer every message.
Temporary closure / maintenance example
Works the same for a shop closing for a holiday and a service pausing for maintenance: dates first, effect second, what to do third.
## Closed 12–15 August We're closed from Tuesday 12 August to Friday 15 August, back as usual on Saturday 16 August. Orders placed while we're away will ship in order from the 16th. Email stays open — replies may just take a day longer than usual. Thanks, and see you on the 16th.
Where to show announcements — the UI
The same announcement lands differently depending on where it appears. The placements that matter, and what each one is for:
- A permanent page — the home for every announcement. Linkable from support replies, indexed by search, readable after the banner is gone. Everything else should link back here.
- A banner or in-app popup — reach, not memory. Good for “something changed today”; useless a week later, because dismissing it is the whole interaction. Never make it the only copy of the announcement.
- A widget on your site — the middle ground: the latest few announcements, visible where people already are, linking to the page for the rest.
- Email / RSS — for the people who asked to be told. Send the note, link to the page.
The Latest covers the first and third of those with one publish — and the RSS half of the fourth: the announcement lands on your page, in your RSS feed, and in the embeddable widget on your own site at the same time. The examples above paste straight into the editor with their headings intact. Free to start, no credit card.