Product feedback · Announcements

Say what's newto the people it's for.

Tore AI drafts the announcement from the change that shipped. You pick who hears it, and it lands as an in-app banner and an email from one draft.

Tore opens soon. Join the waitlist and we'll email you the day you can start.

app.tore.ai/beacon-data/announcements/new
Example data

Example: CSV export shipped in Beacon Analytics version 3.2. Tore AI drafts an announcement from the changelog entry. The audience is narrowed to Beacon Analytics customers on the Growth plan who asked for CSV export: 42 people. In-app banner reaches 42, email reaches 38 because 4 opted out of product email. The banner and the email are previewed side by side. Hana, a product lead, approves and sends it.

Tell the right people.Skip everyone else.

Announcements reach the customers a change is for, inside your product and in their inbox, from one draft.

Only who it's for

Narrow by product, plan and the request they asked for. The count updates as you go.

one blast to the whole list

Written once

One draft becomes the in-app banner and the email, each previewed before it goes.

a banner in one tool, an email in another

Nobody who asked is missed

The people behind a feature request or a bug report are found for you, straight from the request.

a spreadsheet of who wanted it

Never sent twice

Each person gets it once per channel, even if a send is retried or resent.

"sorry, you got this twice"

From a shipped changeto the people waiting for it.

The audience

Target the right people.

Build the audience from what Tore already knows about your customers: the product they use, their plan, and what they asked for. Add anyone else by name. You see exactly how many people each channel will reach before you send.

  • Filter by product, plan and feature request
  • Add named contacts by hand
  • The list freezes when you approve, so the people you approved are the people who receive it
announcements · audience
Example data
CSV export launch2,410 contacts
whereProduct is Beacon Analytics1,180
andPlan is Growth214
andAsked for CSV export42
Plus named contacts Tom at Northwind, Lena at Acme Corp
In-app44
Portal44
Email40
Slack6
Audience freezes when Hana approves

The channels

In-app and email from one draft.

Write it once. Tore shapes the same announcement into a banner inside your product, a post in your customer portal, an email and a Slack message. The quiet channels are on by default; email and Slack you switch on yourself, because they land in someone's inbox and can't be pulled back.

  • In-app and portal on by default, email and Slack when you choose
  • Each channel shows how many people it will reach
  • Busy week? Extra announcements roll into one digest instead of a pile of messages
announcements · send
Example data
Where it goes42 people
In-app bannerdefaultreaches 42 · shows on next sign-in
Customer portaldefaultreaches 42 · stays in their updates feed
Emailreaches 38 · can't be recalled once sent
Slackreaches 6 in shared channels · can't be recalled
Over this week's limit for 3 people: sent in their Friday digest

The thread

Tied to the changelog and the requests behind it.

An announcement starts from real work: a shipped change, a feature request, a known issue. Tore carries the thread from the request to the changelog entry to the people who asked, and it won't say "it's live" until the deploy is verified.

  • Starts from the changelog entry, the request or a known issue
  • Waits for a verified deploy before saying it shipped; a person can override, and that's on the record
  • People who ask after you've sent are flagged for a follow-up
announcements · history
Example data
  1. Request: Export reports to CSV42 people asked · Feature requests
    Aug 2
  2. Change mergedPR #618 · beacon/web
    Oct 27
  3. Deploy verifiedv3.2 is in production
    Oct 28
  4. Changelog entry publishedv3.2 · Export reports to CSV
    Oct 28
  5. Announcement sent to the 42 who askedin-app and email · approved by Hana
    Oct 28
3 more people asked for CSV export after you sent. Send them a follow-up?Send follow-up

Your words

The AI drafts it. A person approves it.

Tore AI writes the first draft from what actually shipped, in plain words your customers understand. Someone on your team picks the audience, asks for changes in plain words or edits it directly, then approves. Change the copy after approval and it needs approving again.

  • Drafted from the change, not written from scratch
  • Ask for changes in plain words, or take over the edit
  • Choosing who hears it stays with your team, and every step is on the record
announcements · review
Example data
Tore AI · draft 1
CSV export is here

You can now export reports as CSV files from the reporting area of the dashboard.

Request changes · HanaWarmer, and tell them exactly where the button is.
Tore AI · draft 2
CSV export is here

You can now export reports as CSV files from the reporting area of the dashboard. You asked, we built it. Open any report, pick Export, then CSV.

10:31Drafted by Tore AI 10:36Changes requested by Hana 10:39Audience set by Hana · 42 people 10:41Approved and sent by Hana

Tune it

Default channels In-app + portalAnnouncements per person, per week 2, then digestWho can approve Product leads
All AI controls →
4channels from one draft: in-app, customer portal, email and Slack
1message per person per channel, even when a send is retried
2quiet channels on by default; email and Slack are your call
0people added after you approve, unless you send a follow-up

You shipped it.Now tell the right people.

Targeted announcements, drafted for you and approved by your team, in the product and in their inbox.

You're on the list. We'll email you the day you can start.

Get early access when Tore opens. No spam.