teem.so

teem.so is a hosted widget that puts live chat, a feature request board, a help center, and a changelog inside your SaaS app, priced at $49 a month with a free trial. It fits teams that want one place for support and product feedback instead of stitching together separate chat, roadmap, and docs tools — and it's a poor fit if you need deep CRM integration or a fully automated support desk, since teem's stated model is that a person on your team answers every chat.

The four jobs the widget covers

teem bundles four functions that SaaS teams usually buy separately:

Because all four live in one widget, a user who asks a question in chat can be pointed to a help article, or nudged to vote on a related feature request, without leaving your product.

Answering support with a person, assisted by AI

The page describes the support model as "Answer from your AI. Your customer gets a person." In practice this means AI helps draft or suggest replies, but a human on your team sends the answer. For teams that don't want customers talking to a bot, this is the key selling point — you get AI leverage on response speed without handing the conversation off entirely.

The same AI assistance extends to content: one of the listed capabilities is "Your agent writes the help center," so draft help articles can be generated rather than written from scratch.

Closing the loop on feature requests

This is teem's most distinctive behavior. When a user votes for a feature request and you later ship it, teem emails everyone who voted. That turns the request board into a retention and communication channel rather than a graveyard of ignored ideas.

The workflow looks like this:

1. A customer posts or votes on a request in the widget.
2. Your team tracks demand by vote count ("Build what most customers want").
3. When the feature ships, teem notifies every voter automatically.

For bug reports, the page frames the same loop as "Fix bugs from the first message" — the first chat message becomes the starting point for the fix, and the changelog closes it out publicly.

Running it from a dashboard or an AI agent

teem can be operated two ways: from the teem dashboard, or through an AI agent. The site states you can "run it all from ChatGPT or Claude," and provides an install prompt you paste into Claude Code, Cursor, or Codex:

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

Two things to note from the page: teem ships as a hosted script, so you should not write your own widget, and your organization key appears on the install page after you sign up.

What to check before committing

• Pricing: $49/month is the stated price, with a free trial available. Confirm current terms on the pricing page, since the site references both "free trial" and "pricing" without listing payment platforms.
• Human-in-the-loop requirement: if you want fully automated first-line support, teem's model is explicitly the opposite.
• Install path: if you're using an AI coding agent, the install.md prompt is the fastest route; otherwise expect a standard hosted-script embed.

Start with the free trial and route one real support channel and one real feature request through it — that will tell you quickly whether consolidating chat, feedback, docs, and changelog into one widget matches how your team actually works.

teem costs $49 per month, and there is a free trial. That single price covers the whole product described on teem.so: live chat, a feature request board, a help center, and a changelog, all delivered inside one widget embedded in your app. If you are a SaaS team comparing all-in-one support tools, the relevant question is not just the number — it is what that number includes and what you have to do before you can judge it.

What the $49/month covers

According to the teem site, the plan bundles four things that are often bought separately:

The site's framing is "people-first, AI-enabled": you can answer from your AI while the customer still gets a person. It also states you can run everything from the teem dashboard or from an AI agent such as ChatGPT or Claude.

Is there a free trial?

Yes. The site offers a free trial and a "Start a free trial" call to action. The published material does not state the trial length, whether a card is required, or what happens at the end of the trial — so treat those as things to confirm on the signup page rather than assumptions.

What you need before the price means anything

The $49 is a subscription for a hosted product, not a self-hosted script. Two practical prerequisites come from the install instructions:

1. An organization key. The site says your organization key appears on the install page once you sign up. Without signing up, you cannot wire the widget to your account.
2. A place to embed the script. teem ships as a hosted script, and the instructions explicitly say not to write a widget yourself.

The install flow is agent-assisted. The site provides a prompt you can paste into Claude Code, Cursor, or Codex:

Install teem in this app. Read https://teem.so/install.md and follow it.
teem ships as a hosted script. Do not write a widget.

The expected result is that the agent reads the install document and adds the hosted script to your app, after which the widget appears in-app and your dashboard starts receiving chats and requests.

How to decide whether $49/month is worth it

Use the same dimensions you would apply to any support stack:

• Consolidation. If you currently pay for a chat tool, a feedback board, a docs site, and a changelog separately, one line item at $49 is easy to justify. If you already have most of these and only need chat, the bundle is less compelling.
• Team size and seats. The published pricing signal is a flat $49/month figure. The site material does not describe per-seat pricing, so if seat count matters to your budget, verify it before committing.
• The ship-notification loop. The distinctive mechanic is that shipping a requested feature triggers an email to everyone who voted for it. If closing that loop manually is a real cost for your team, this is the feature to evaluate first during the trial.
• AI-agent workflow. If your team already works inside ChatGPT, Claude, Cursor, or Codex, the agent-driven setup and dashboard control may reduce onboarding time. If not, you are paying for a capability you will not use.

A reasonable trial plan

1. Sign up and locate your organization key on the install page.
2. Run the install prompt in your coding agent, or add the hosted script manually if you prefer.
3. Confirm the widget renders in your app and that a test chat reaches your dashboard.
4. Post one feature request, vote on it yourself, then mark it shipped to see whether the notification email behaves as described.
5. Check the help center and changelog surfaces before the trial ends.

If steps 3–5 work without manual patching, the $49/month is buying you a working loop rather than a demo. If any of them require work the site does not mention, that is your signal to ask before converting.

teem ships as a hosted script, so you install it by adding a snippet to your app rather than building a widget yourself. You need a teem account first, because your organization key appears on the install page only after you sign up. Once the script is in place, live chat, the feature request board, the help center, and the changelog all render inside your app from one widget.

What you need before starting

• A teem account. The install page and your organization key are available after sign-up.
• Access to your app's front-end code, or an AI coding agent that can edit it for you.
• Your organization key, which you copy from the install page.

teem's site offers a free trial, so you can complete the install and evaluate the widget before committing. Pricing is listed at $49 a month.

Install with an AI agent

teem supports installation through ChatGPT, Claude, Claude Code, Cursor, or Codex. The site provides a prompt you paste into your agent:

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

The expected result: your agent reads the install instructions, adds the hosted script to your app, and wires in your organization key. teem's own guidance is explicit that the agent should not write a widget — the script is hosted, so the agent's job is integration, not implementation.

If your agent asks for the key, paste the organization key from your teem install page.

Install manually

1. Sign up and open the install page to copy your organization key.
2. Add the teem hosted script to your app, following the instructions at https://teem.so/install.md.
3. Include your organization key so the widget connects to your workspace.
4. Load your app and confirm the widget appears.

The expected result is the same as the agent path: one widget inside your app that carries support, feedback, and changelog.

Verify the install

After the script loads, check that the widget opens inside your app and that it shows your workspace's content rather than an empty or error state. An empty widget usually means the organization key is missing or wrong; a widget that never appears usually means the script did not load on the page you are testing.

What you get once it is running

• Live chat — a person on your team answers every chat, with AI assistance available. As teem puts it: "Answer from your AI. Your customer gets a person."
• Feature request board — customers vote, and when you ship a request, teem emails everyone who voted for it.
• Help center — your agent can write it.
• Changelog — release notes live in the same widget.

You can run all of this from the teem dashboard or through an AI agent such as ChatGPT or Claude.

Common snags

• Skipping sign-up. The organization key is only on the install page after you register, so there is no way to complete a working install without an account.
• Letting the agent build a widget. teem is a hosted script; a custom widget will not connect to your workspace.
• Testing on the wrong page. If your app loads scripts per route, confirm the snippet is present on the page where you expect the widget.

teem.so is a hosted widget that puts live chat, a feature request board, a help center, and a changelog inside your SaaS app. It's aimed at SaaS teams that want customer support and product feedback in one place rather than spread across separate tools. The site lists it at $49 a month and offers a free trial, so you can evaluate it before committing.

What's actually in the widget

The pitch is consolidation: four customer-facing surfaces, one install.

• Live chat — a person on your team answers every chat, per the site's description.
• Feature request board — customers submit and vote on ideas.
• Help center — documentation that your AI agent can write, according to the page.
• Changelog — where you announce what shipped.

The loop that ties these together is the notification behavior: when you ship something someone requested, teem emails everyone who voted for it. That closes the gap between "we logged your request" and "here it is," which is usually where feedback boards lose credibility.

How you run it

Two paths, both described on the site:

1. The teem dashboard — manage chats, requests, and content directly.
2. An AI agent — run it from ChatGPT or Claude. The page also provides a prompt you can paste into Claude Code, Cursor, or Codex to install teem in your app.

The install itself is a hosted script, not something you build. The site is explicit about this: "teem ships as a hosted script. Do not write a widget." Your organization key appears on the install page after you sign up.

Where the AI fits

The framing on the page is "Answer from your AI. Your customer gets a person." That's a specific division of labor worth noting: AI handles the drafting and the help-center writing, while a human stays on the other end of the chat. If your concern with AI support tools is customers getting stuck in a bot loop, this positions against that.

What to check before signing up

• Pricing details — $49/month is stated, but confirm what's included at that tier and what the free trial covers.
• Install requirements — read https://teem.so/install.md before pasting the agent prompt, so you know what the script touches.
• Email behavior — the voter-notification feature is the core differentiator; verify how it handles voters who have since churned or unsubscribed.

If you're a small SaaS team currently paying for a chat tool, a feedback board, and a docs site separately, teem's value proposition is replacing three line items with one. If you only need chat, the bundle is more than you're asking for.

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.