Short, direct answers

It reads customer conversations from wherever they happen (support chats and email, calls, surveys, forms, team chat), proposes the requests hidden in them with the exact sentence that supports each, lets you accept or reject every suggestion, weighs requests by who asked and what their account is worth, and helps you tell the people who asked when it ships.

It is built so you do not have to take its word. Every quote is checked to appear word for word in the original at the stored position; a made-up quote cannot be saved. Answers cite quotes or say there is no evidence. Suggestions never become requests until a person accepts them, and the platform measures how often its own suggestions were right.

No. When a request ships, it prepares a personal draft for each person who asked, in their own words. You review and approve; only approved messages are sent, and that rule is enforced in the sending code itself, not only on the screen. Every message carries an unsubscribe link and opt-outs are honoured.

Only your workspace, and only the teammates who have a role in it. Each workspace is isolated at the database level. Customer text goes only to AI routes marked as allowed to receive it, is never used to train models, and sensitive numbers (card numbers, keys, passwords) are hidden before storage and before any AI call. The subprocessors page lists every company that handles data for us.

Deleting a person removes their quotes, conversations, transcripts, recordings, survey answers and files. Working data such as past questions and AI cost records also expires on its own schedule, listed in the privacy policy.

No. Paste one conversation and you get cited requests in minutes. Everything else (people and accounts, tags, integrations, surveys) can wait.

From the accounts of the people who asked. The value is summed over distinct accounts, so two people from one account count that account once. Account values come from a CSV import, from entering them, or (soon) read-only from HubSpot or Salesforce.

Yes, through one inbound web request that almost every tool can send. You choose what to send (a ticket thread, a call transcript, a form answer), and a retry never stores it twice. Native connectors that capture automatically are on the list; see the integrations page for what is available, coming soon and planned.

Yes. Connect Claude, ChatGPT, Cursor or another assistant that supports remote tools. An admin approves what it may do. It can search and read requests, ask cited questions, find quotes by meaning and add notes to the review queue. With an extra permission it can change a request's status (never to or from shipped) and add tags. It cannot send, publish, merge or delete anything.

Models are used through one interface with separate small, mid and large tiers and failover, so providers can change without changing what the platform promises. The subprocessors page lists the providers in use at any time. Every AI call records the provider, model, prompt version, tokens and cost.

Yes. An admin can export the whole workspace (companies, people, conversations, requests and the quotes behind them) and import it again.

The target is WCAG 2.2 AA: semantic pages, full keyboard use, labelled controls, announced errors, good contrast in light and dark, and phone-width layouts. Automated checks run on the main flows. A screen-reader review by a person is still to come, and we will say so here when it is done.

There is a free plan and paid plans for teams that need recordings, surveys, integrations and more. Prices will be published before launch; the pricing page shows what each plan includes.

Use the contact page, or the feedback address on the community page. Integration requests are especially welcome: the order of the list follows what people ask for.