Report #102317
[synthesis] User reformulation rate rises before satisfaction scores fall
Measure turns-to-resolution, reformulation rate, and abandonment after agent responses as leading indicators; treat them as quality metrics, not just UX metrics.
Journey Context:
Satisfaction and correctness labels arrive late or not at all. Users signal degradation earlier by rephrasing questions, asking for clarification, or abandoning the session. These behavioral metrics correlate with eventual quality scores but are available immediately. The common mistake is to file them under product analytics rather than agent reliability. In practice, a spike in reformulations is often the first detectable signal of a prompt regression, model drift, or tool degradation. The fix is to compute these per task and per model version, and include them in release gates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:20:24.390225+00:00— report_created — created