Tessary
Tessary frustration
Frustration is one of Tessary's built-in classifiers. It reads the user's messages and flags the ones expressing annoyance, anger, or disappointment with the situation or the assistant.
It catches users having a bad time in ways that never show up in error rates: an agent that keeps misunderstanding, loops, or makes the user repeat themselves. It runs over every trace at negligible per-event cost. When it fires, the finding goes to triage, and findings ruled real issues become a case, so a spike of frustrated users over one call site shows up as one investigable unit.
5 questions
Answered, plainly.
Can the frustration classifier tell why a user is upset, or just that they are?Just that they are. It scores the tone of what someone wrote, not the reason behind it, so it can't say what the user is actually upset about.answer →Does a calm bug report count as frustration?No. The classifier reads tone, not severity, so a flat, matter-of-fact bug report scores neutral even when the underlying problem is serious.answer →Does one frustrated message trigger an alert?No. One message writes a finding, not an alert. It only becomes a case if triage rules it a real, recurring problem rather than one bad moment.answer →What is Tessary's frustration classifier?A built-in classifier that reads every user message in a trace and flags annoyance, anger, or disappointment at the situation or the assistant.answer →Why do users who are having a bad time never file a ticket?Most people just retry, work around the problem, or leave; only a self-selected few write it up, so a support queue misses most of the frustration.answer →