Reading Rephrases as Signal, Not Noise

Users who rephrase the same intent three times are rarely exploring for fun. They are hunting for a reply that matches what they meant. Assistant analytics that celebrate high turn counts can misread struggle as depth.

Tag rephrase clusters by intent where possible, and measure time-to-resolution alongside turn depth. A short successful path is usually healthier than a long looping one—even if the long path produces more events.

Instrument regenerate and edit actions explicitly. Without them, you cannot tell whether a second prompt was a new question or a frustrated rewrite of the first.

In UK product teams we work with, the fastest quality gains often come from fixing the top three rephrase loops—not from adding another aggregate satisfaction score.