Feedback you don't read still costs you.Feedback you act on pays.
Sentriment reads every review, ticket, survey and sales call, groups them into themes and shows the monthly revenue (MRR) behind each one. It warns you which accounts are drifting toward churn, and shows which users love you, in their own words.
For SaaS product, support and growth teams.
No credit card · Set up in 5 minutes · 100% EU-hosted, GDPR-first
Analytics for what users do. Sentriment for what they say.
how it fits beside Mixpanel, Amplitude and PostHog →Follow one piece of feedback through all six steps.
- apiuser_8231 · 14:02
- received“checkout froze when I applied my coupon”
Every channel, one pipeline.
Send feedback from your backend, add a widget to your app, or connect the tools your feedback already lives in. Every source is read the same way, and what comes out lands where your team already works. Read the docs →
REST API
liveOne API call from any backend. Personal data is removed on arrival, and the feedback joins that user's record.
$ curl -X POST \
https://app.sentriment.com/api/v1/feedback \
-H "Authorization: Bearer sk_live_…" \
-H "Idempotency-Key: order-4231-note" \
-d '{
"text":
"checkout froze when I applied my coupon",
"userId": "user_8231"
}'Any language, one call
Send one piece of feedback or thousands. A retry never creates a duplicate (idempotency keys).
Users come with it
Pass your own user id and the feedback counts toward that user's health score.
Errors that explain themselves
Every failure says what went wrong and how to fix it, in the standard problem+json format.
Slack & email alerts
Spikes, regressions, and at-risk users, the moment they happen
Mixpanel & Amplitude sync
Health scores pushed onto user profiles. Cohort and campaign on them
GitHub & Linear issues
File from a theme; feedback linked to the fix
Daily digest
What changed overnight, every morning on your Insights page
Dashboard, API & webhooks
Query clusters programmatically, push events out
REST API
liveOne API call from any backend. Personal data is removed on arrival, and the feedback joins that user's record.
$ curl -X POST \
https://app.sentriment.com/api/v1/feedback \
-H "Authorization: Bearer sk_live_…" \
-H "Idempotency-Key: order-4231-note" \
-d '{
"text":
"checkout froze when I applied my coupon",
"userId": "user_8231"
}'Any language, one call
Send one piece of feedback or thousands. A retry never creates a duplicate (idempotency keys).
Users come with it
Pass your own user id and the feedback counts toward that user's health score.
Errors that explain themselves
Every failure says what went wrong and how to fix it, in the standard problem+json format.
Slack & email alerts
Spikes, regressions, and at-risk users, the moment they happen
Mixpanel & Amplitude sync
Health scores pushed onto user profiles. Cohort and campaign on them
GitHub & Linear issues
File from a theme; feedback linked to the fix
Daily digest
What changed overnight, every morning on your Insights page
Dashboard, API & webhooks
Query clusters programmatically, push events out
coming next
One pipeline, whatever the source
A review, a ticket, a sales call, a note from the widget and a row from a spreadsheet are cleaned of personal data, de-duplicated and scored the same way.
One person, one profile
Email joins a customer's Intercom chats, Zendesk tickets and in-app notes into one record with one health score.
History without the noise
Imported history counts toward themes and health scores, but never fires alerts or shows up as a spike.
- Exporting tickets to a spreadsheet
- Reading reviews by hand
- apiuser_8231 · 14:02
- received“checkout froze…”
- redacted3 identifiers → ⟨name:1⟩ ⟨email:1⟩ ⟨phone:1⟩
Personal data never reaches storage.
Personal data (PII) such as names, emails, phone and card numbers is swapped for labelled placeholders on the way in. The original text never touches the database, and the database is in Frankfurt. How redaction works →
Removed before storage
Placeholders like ⟨email:1⟩ replace personal data before anything is saved, so there is none to leak, to be ordered to hand over, or to end up in an AI model.
100% EU data residency
Database in Frankfurt, compute and backups in the EU. One thing leaves it: feedback text with the personal data already removed, sent to AI model providers in the United States for analysis, never for training.
Your data trains nothing
Feedback is processed to serve your dashboard, never used to train third-party models; every AI output records the model and prompt that produced it.
- Sending raw customer text to a US vendor
- A data-processing agreement that hopes for the best
# in-app widget
"refund me at sara.k@acme.io, card 4242 4242 4242 4242"
received…
# POST /api/v1/feedback
"Marta Ellis, call me on +34 612 04 88 91"
received…
- PII redacted
- EU-hosted
- GDPR-first
Right to be forgotten, built in
One call erases a user's feedback and identity everywhere. Themes recount and exports update. Deletion is a feature, not a ticket.
DELETE/api/v1/users/user_8231
204 No Content · cascade completed
4 identifiers removed · processed and stored in the EU · never used to train third-party models · erased in one call
- apiuser_8231
- redacted3 identifiers
- clusteredCheckout freezes on coupon · 42 reports · €4,180
See the revenue behind a complaint.
Every piece of feedback is read, de-duplicated and grouped by meaning into themes. Each theme carries the MRR of the accounts that reported it, so the roadmap argument is about money, not volume. See a theme →
Themes
last 30 days · 1,284 pieces of feedback
ranked by the MRR behind each theme · 1,284 pieces of feedback · last 30 days
Checkout freezes on coupon
▲ 340%€4,180
MRR behind this theme · 42 reports
“Coupon field just spins forever on my iPhone.”
“Cart freezes the second I apply SAVE20.”
42 reports cited · first seen 6h ago · checkout v4.2.1
Priced in MRR
The revenue behind a theme is the sum of what those customers pay, taken from the customer value your server already sends. No extra tracking.
Spikes surface within hours
A theme rising 340% in a day is flagged and summarised before the next review.
Quotes stay attached
Every count links back to the exact feedback behind it, so nothing is paraphrased away.
- Manual tagging in Zendesk
- Vote counts in Canny
- apiuser_8231
- clusteredCheckout freezes on coupon
- scoreduser_8231 · 23 · at risk
Catch churn while it is still preventable.
Each user gets an explainable health score from the tone and weight of what they send. A sustained decline fires an alert before the renewal call, not after it. How the score works →
Users at risk
score under 40 · change over 7 days
User at risk: user_8231
Slack · #cs-alertsscores recomputed nightly and on new feedback · synced to Mixpanel and Amplitude
0 to 100 · healthy from 70 · at risk under 40
why this score: 7 pieces of feedback · average tone −0.42 · frustration −6
Ranked by MRR
Risk is sorted by what the account pays, so the biggest exposure comes first.
Alerts where you work
Slack or email the moment someone drops into at-risk, with who, why and what they pay.
Synced back
Scores land in Mixpanel and Amplitude as user properties, so cohorts and campaigns can use them.
- Finding out at the renewal
- A churn dashboard that reports the past
- clusteredCheckout freezes on coupon
- scoreduser_8231 · 23 · at risk
- actedalert · #cs-alerts · filed SEN-142
Ask a question. Get a cited answer.
Ask in plain language across every source at once. The answer carries a verdict, a number and the quotes it rests on, and a tracked question re-answers itself on a schedule. Ask and tracked questions →
Cited and auditable
Every answer records the model and prompt version that produced it, so every claim in your dashboard can be checked.
Alerts that matter
Slack or email when a theme surges, a fixed issue returns, or a user drops into at-risk.
Out to where you work
File a theme to GitHub or Linear, get the daily digest, push events over webhooks or pull them from the API.
- The weekly 'what are users saying' deck
- Searching the support inbox
“We can't roll this out without SAML.”
“Okta or it's a non-starter for our security team.”
also in the box
Tell them it shipped
Mark a theme fixed and Sentriment drafts the note for everyone who reported it, ready to paste into your support tool or changelog.
A weekly worklist
What is new, spiking or biggest, with pin, mute and resolve in one place.
Search by meaning
Look for “slow” and also find “laggy”, “takes forever” and “just spins”.
Reports you can revisit
Any slice of your feedback as a saved chart, ready for the weekly review or the board.
every answer cites the feedback it rests on · tracked questions answer themselves again every week
- widgetuser_2210 · 09:41
- received“love the new editor!!”
- profiledproduct lead · Pro · 2.4×
Find the customers you should clone.
The same score that flags churn ranks your happiest accounts. Sentriment reads what they have in common, who does not fit, and the words they use, so you know who to find, who to stop chasing and what to say to them. Segments and traits →
Your best customers look like this
What your 14 happiest accounts have in common. The last column is how much more common each trait is among them than among all your users.
built from the customer details you already send with each user · nothing bought, nothing guessed
Users who love you
top 3 of 14 · by MRREngineering-led trials
Same size of company, different champion. Less happy, costlier to support, and waiting on something you have not built.
Not never. Not until SSO ships. Until then, open the conversation with the product team.
The words on your site are not the words in their mouths
Sentriment reads your own web pages, counts the phrases you use, and sets them beside the phrases your happiest customers use. Then it drafts the campaign.
the number is how many times each phrase appears in customer feedback · your homepage and pricing page, read against 38 pieces of praise
Your next campaign, drafted from their words
A headline, who to show it to, and a customer quote to back it.
Stops the copy-paste. Onboarding your team will actually enjoy.
from “stops the copy-paste” (23) and “onboarding was actually fun” (9)“onboarding was actually fun?”
a Pro customer (user_0873), word for wordpraise is grouped and counted like complaints · quotes are word for word · scores are recomputed every night
Your ideal customer, from your own data
The traits your healthiest accounts share, each with how over-represented it is, so the ideal profile is a finding, not a workshop.
The accounts that cost you
The same maths, inverted: the segment with the lowest health and the most feedback per euro, before sales spends another quarter on it.
Their words, your copy
Praise is counted phrase by phrase, so the headline, the audience and the proof quote come from customers, not from a meeting.
- Guessing your ideal customer profile
- Testimonials you have to ask for
- Copy written in a meeting
Measured
From raw quote to ranked theme in 8.7 seconds.
Three numbers the site publishes because they were measured, not promised. Every figure below is real; nothing is a projection.
- to the first theme
- 8.7s
- median, from raw feedback to a labeled, sentiment-scored theme, measured in production
- widget footprint
- 5.3KB
- framework-free, shadow-DOM isolated, one script tag
- hosted in the EU
- 100%
- data in Frankfurt, compute in the EU, PII redacted before storage
one real piece of feedback, straight through the pipeline
“Love the new dashboard, but the export button is impossible to find”
Actual output from our production pipeline, theme label and emotions included. 8.7 seconds, end to end.
You are not short on feedback. You are short on a way to read it.
Sentriment reads all of it, prices what hurts, and hands you the words of the people who love you.
sentriment.com · EU-hosted · GDPR-first · PII redacted before storage
FAQ
Questions, answered.
PII (emails, names, phone and card numbers) is redacted before anything is stored; the raw text never touches the database. Everything is hosted in the EU (data in Frankfurt), encrypted in transit and at rest, never used to train third-party models, and deletable via API at any time. SOC 2 is on the roadmap; the GDPR architecture is live today.