How teem Notifies Users When a Requested Feature Ships

Updated

teem closes the loop between a feature request and the release that fulfills it: when someone votes on a request in the feature request board and you later ship that feature, teem emails everyone who voted for it. This applies to requests tracked inside teem's widget, and the notification is automatic rather than something your team has to remember to send.

The feedback-to-release loop

teem bundles four tools into one in-app widget: live chat, a feature request board, a help center, and a changelog. The notification behavior sits at the junction of the request board and the changelog.

The flow works like this:

  1. A customer submits or votes on a request. Requests live on the feature request board inside the widget, and each one accumulates votes from users who want it.
  2. Your team ships the feature. When the work is done, the request is marked as shipped.
  3. teem emails every voter. Everyone who voted on that request gets an email telling them it's live.

The changelog is the public record of what shipped; the voter email is the personal follow-up. Together they turn a passive changelog into a targeted "you asked, we built it" message.

Why the voter email matters

Most changelogs are broadcast to whoever happens to read them. A voter email is different because it goes only to the people who explicitly asked for that specific thing. That has a few practical effects:

  • It confirms their feedback was heard. A user who voted weeks or months ago gets a direct signal that their input changed the product.
  • It re-engages churned or quiet users. The email is a reason to return to the app at the moment a feature they wanted becomes available.
  • It reduces manual outreach. Your team doesn't maintain a list of who asked for what and email them by hand; teem tracks voters and sends the notification when the request ships.

Running it from the dashboard or an agent

teem can be operated from its own dashboard or driven through an AI agent. The site describes running it "from your teem dashboard or with your AI agent," and offers an install path where you paste a prompt into a coding agent:

Install teem in this app. Read https://teem.so/install.md and follow it.

teem ships as a hosted script, so the guidance is not to write your own widget. Your organization key appears on the install page after you sign up.

On the support side, the site's framing is "Answer from your AI. Your customer gets a person." — meaning AI can help draft or route answers, but a person on your team answers every chat. The help center content can also be written by your agent.

What to check before relying on this

  • Votes must be collected in teem. The email goes to voters on the request, so requests tracked outside the board won't trigger it.
  • The request has to be marked shipped. The notification is tied to shipping the request, not to publishing a changelog entry alone.
  • Pricing and trial terms. The site references a free trial and a $49/month figure, with "free trial" and "pricing" as pricing signals. Confirm current terms on the pricing page before committing, since the source does not detail plan limits or payment methods.

If your goal is to show users that their feedback leads to real releases, the voter email plus the changelog is the mechanism that does it — provided requests and votes live inside teem.