How do I tell when users are frustrated with my agent?

By the time frustration reaches a survey or a cancellation, it's too late to act. But it's visible much earlier in the conversation itself: the user rephrases, repeats, corrects the agent, escalates tone, or abandons the session.

Flowlines groups user frustration separately from reliability errors. The issue detail shows what happened, why it matters, the suggested next step, and the sessions where the pattern occurred.

Abandonment is the strongest version of the same signal: the user leaves mid-task. Flowlines lists abandonment as its own behavior issue, attached to the use cases, users and sessions where it fires, so you can inspect what happened in the turns before the exit.

The Users view adds activity and issue-free context, so you can see whether a problem is isolated or recurring for someone who depends on the agent.

Which frustration signals are reliable?

1. The same request rephrased three or more times.
2. Explicit negative feedback, such as saying the answer is wrong.
3. Abandoning a task in the middle of a multi-step flow.
4. Asking for a person or for support.
5. Coming back later with the same request. Confirm any automated frustration signal by reading a sample of sessions.