Can the frustration classifier tell why a user is upset, or just that they are?

The classifier on its own says only that a user is unhappy with the assistant; the why comes from root cause analysis on the case, which groups the frustrated conversations by what the agent did.

Scoring is narrow on purpose. It reads one user message with the four before it, and answers one question: is this person unhappy because of the assistant? That’s enough to count frustrated conversations per call site, and not enough to explain them.

When a call site’s rate rises and a case opens, you can run RCA on it. It reads the conversations the finding cites and writes a report of causes, each naming what the agent did, the conversations that show it, where in your code or prompt it comes from when a change lines up with it, and a suggested fix. Causes are grouped by the agent’s behavior, not by what users said.

The limit: a report can come back with no cause found, and it says so rather than inventing one.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y