See the third contact before your customer gives up.
Support agents handle one conversation at a time. Flowlines connects recurring issues, affected users, and the exact sessions that show a relationship deteriorating.
01
The problem
A returning customer can rephrase the same request across several chats while every individual trace looks technically valid.
Request logs show that the agent ran. They do not show repeated frustration, abandonment, or which users keep encountering poor results.
02
What Flowlines surfaces
The Issues view separates behavior problems from reliability errors, including user frustration, abandonment, result quality, hallucination and trust, and looping or stuck behavior.
Open an issue to see the affected use cases, users, and original sessions.
03
Who needs attention
The Users view combines observed and repeat users, issue coverage, activity depth, cost per chat, and execution time.
Review new users, power users to learn from, highest-spend users, and the slowest experiences.
04
How you connect it
Use OpenTelemetry, read-only Langfuse or LangSmith polling, provider-side OpenTelemetry export, or a one-time public LangSmith trace import.
follow the repeat contact ↙
Repeat contactCustomers who came back with the same unresolved need
Last 7 days
Repeat contacts38Affected customers23Asked for a human7Still unresolved12
Flowlines