Skip to content

CHANGELOG · RELEASE 7 · 18th March 2026

Run more than one product? Each gets its own stream of feedback.

A product line, a few teams or a handful of initiatives, each kept separate.

Most teams do not run one product. They run a product line, a few teams, a handful of initiatives. The feedback for all of it arrives in one pile.

Projects give each stream its own container. Slack channels map to a project, so signal routes correctly the moment it lands. Clustering respects the boundary. A billing request stays out of the way of a dashboard feature.

Open a project and the priorities you see belong to it.

Beta.

How to use it

Most teams do not run one product. They run a product line, a few teams, a handful of initiatives, and the feedback for all of it arrives in one pile. Projects give each stream its own container. Slack channels map to a project, so signal routes correctly the moment it lands, and clustering respects the boundary. A billing request stays out of the way of a dashboard feature.

  1. Create a project for each product line.
  2. Map its Slack channels, so new signal routes itself.
  3. Open the project. The priorities you see belong to it.

Also in this release

Sidebar

Navigation stays visible on every page. Ask Annsa and your avatar sit 1 click away.

Surveys

5 survey types, each for a different moment. Per-survey analytics show what is landing.

Get your agents in a row.

Try Annsa