01 · Listen

We gather what they say — wherever they say it.

All your sources, one system

Six ways in, one processing chain — whatever your team uses today.

  • CSV upload from any tool that exports a file.
  • Zendesk, ClickUp, Jira with automatic sync.
  • Sightelle surveys — answers flow into the same themes.
  • Push API for your own system, with workspace keys.
Where it comes from

six sources → one chain → themes, trends, quotes

Sources and channels — one system

Sources: CSV upload, Zendesk, ClickUp, Jira, Surveys, Push API. Output channels: Slack, Microsoft Teams, Email, Webhook.

In
Out

Surveys that get heard

Design, share and measure — and every open answer becomes a signal in the same themes as your tickets.

  • Designer with branching, matrices, "up to N choices" and per-question scales.
  • NPS and CSAT with the right arithmetic — not misleading averages.
  • Public page with your branding, a printable QR, an answers webhook.
  • Anonymity by design: where you promise it, the schema guarantees it.
  • Survey from a description: write what you want to ask, the AI proposes the questionnaire, you approve.
  • Multilingual: translate questions per language and the same link serves everyone in their own.
Public survey page

How likely are you to recommend us to a colleague?

012345 678910
→ Next question, because you answered 9-10:
“What did you like most?”

Open a demo survey →

02 · Understand

Thousands of voices become a few themes with a name, a trend and a value.

Themes and trends

Every comment is automatically classified into themes that make sense for your business — and the dashboard shows them in three columns: what customers ask for, what holds them back, what they love.

  • Time series and spikes per theme, with "what moved" in every period.
  • Real quotes behind every number — never paraphrased.
  • Probable cause: your timeline events (deploys, changes) next to a theme’s rise.
Overview sample

Asking for

Integrations
Report exports
Per-role permissions

Holding them back

Support speed
Form data loss
Billing

What they love

New design
Reliability
Onboarding

Your own axes

Customers, products, types — and up to five dimensions of your own: priority, department, channel, whatever makes sense for you.

  • Filters everywhere: every screen answers for the subset you are looking at.
  • Customer value: themes weighted by ARR, not just by how many voices.
  • Dimensions fill from your sources — a CSV column, a ClickUp/Jira field, keys in the API.
Axes — signals per dimension sample
Products
Types
Customers

The sample’s axes. Your own dimensions sit next to them and become filters on every screen.

Who said it — and how much it weighs

Upload your customer list and every signal binds to its customer — even when the data has no email, from the structure of your tools.

  • A customer page: their themes, their trajectory, their words.
  • Value weighting: Volume, Revenue or Retention — you choose what matters most.
  • Happy customers: praise in the last 60 days and no risk flag — your list for reviews and testimonials.
  • Churn risk visible next to every name, before it becomes a loss.
Customer page sample

Delta Logistics

ARR €96,000At risk
486 signals · Jan – Sep 2026
WeightingVolume · Revenue · Retention

Events next to the trends

Record deploys, pricing changes, announcements — and the product places them next to every theme’s curve.

  • «Probable cause»: when a theme rises, you see which event preceded it.
  • Scoped events: a deploy that concerns one customer or one product is judged only there.
  • Before/after for every event — it shows, it does not judge.
  • Automatically from CI via the API, or by hand from the team.
Theme “Support speed” — 90 days illustration
Probable causeDeploy 4.2 came before the rise
03 · Act

The decision becomes work — and the work gets measured.

The home screen answers «what is new for me?»

Every member sees their own news — what a colleague saw stays new for them — and every theme carries the team’s decision.

  • A state per theme: to review, watching, parked, in progress.
  • Reawakening: a parked theme wakes on its own if signals return or the trend rises.
  • Roles that mean something: Owner, Lead, Member, Viewer — theme decisions belong to whoever holds them.
What changed — for you illustration
Support speedIn progress
Report export to ExcelTo review
Integrations with third-party systemsWatching
An API for billingParked
Reawakening “An API for billing”: 10 new signals — back on the list

From theme to work — and back

Sightelle does not stop at «we found a problem»: it tracks what happened to it, and tells you whether it worked.

  • One click → a ClickUp task with the theme’s details.
  • Closing the task becomes an event on the theme, and the theme moves to watching.
  • «Did they drop?» — a 14-day before/after comparison around the close, no guesswork.
  • Reappearance: if the complaints come back, the theme reopens by itself.
The cycle of one decision
01Theme
02Task
03Close
04Measure
14 days before the same counting rule on both sides · under 5 signals, no number 14 days after

Alerts on your own criteria

Not "something changed" — exactly what you defined as mattering.

  • Up to three conditions per rule (signals, scores, customers, ARR) over a 1/7/30-day window.
  • A daily cap and a morning digest: alerts respect your day.
  • A preview on history: see when the rule would have fired before you save it.
New alert rule illustration
Signals ≥ 20
AND Customer ARR ≥ €50,000
Window: 7 days · Recipient: product team
Preview on history

Each dot: a day the rule would have fired.

04 · Share

What was found reaches whoever decides.

The audit document

On your first completed upload, Sightelle generates a self-contained document with the findings — built to be forwarded to whoever decides, not to sit in a dashboard.

  • Self-contained HTML: opens anywhere, prints properly, loads nothing from the internet.
  • A frozen snapshot: what you sent does not change behind your back.
audit-sightelle.html
It generates itself on your first completed upload.

Self-contained — opens and prints anywhere, loading nothing from the internet.
Frozen snapshot

See a sample document →

Weekly report and channels

Every Monday, the week’s picture arrives where your team already works.

  • Email in each recipient’s language.
  • Slack and Microsoft Teams with numbers and a link — never customer words in an open channel.
Monday morning
Email

“Your week: N themes rising, N new.”
In each recipient’s language.

Slack · Teams

Numbers and a link — never customer words in an open channel.

05 · Foundations

What keeps the system standing, without you thinking about it.

Security and languages

Designed for customer data from the first line of code.

  • Emails, phone numbers and tax ids removed before any AI processing — the original stays with you.
  • Full workspace isolation and API keys with scoped permissions.
  • Export and deletion of your data whenever you ask.
  • MFA with an authenticator, optionally enforced for the whole workspace.
  • An activity log: who did what, for the day that question needs an answer.
  • Greek and English across the whole product — interface, emails, exports.
  • It understands Greeklish too — «to site einai arga» files next to «το site είναι αργό».
Before it goes to the model
“I called [phone] and gave them my [tax id], but I waited three days.”
The original stays in your database. Only the cleaned text goes to the model — and every call is logged.

Try it all, free

The free audit includes everything you need for a first full picture.

Start free