If an AI lets you clear up confusion your own way, do people pick one favorite method — or mix and match?
What clarification strategies do users naturally prefer when given flexible repair options?
This explores what people actually do when an AI system lets them choose how to clear up a misunderstanding, instead of forcing one fixed way to clarify. It also asks which kinds of clarification people find useful.
This explores what people actually do when an AI system lets them choose how to clear up a misunderstanding, instead of forcing one fixed way to clarify. The most direct evidence points to a surprising answer: people don't settle on one preferred strategy. In the PleaSQLarify study, the system turned ambiguous database requests into visible choices that users could explore. Participants used several different ways of fixing the misunderstanding, often within a single session, and clarification took between two and eight turns. The design lesson is that interfaces should support many ways of resolving ambiguity, not pick the 'right' one Can systems surface ambiguity instead of guessing user intent?.
When people do get asked a question, the type of question matters. Questions that target a concrete gap ('What type of monitor?') consistently beat open requests to restate a goal ('What are you trying to do?'). The reason is that people engage when they can see how their answer will improve the result Which clarifying questions actually improve user satisfaction?. That fits PleaSQLarify's approach of showing the ambiguity directly: in both cases the user is handed something concrete to react to, not asked to explain themselves again.
The less obvious finding is that people often don't want to be asked at all. In a Wizard-of-Oz study of computer-use agents (participants believed they were using an AI that a hidden researcher was actually running), users wanted the agent to quietly resolve low-stakes ambiguity, like which menu to click. They wanted it to stop and check before high-stakes actions like payments. What set their tolerance was the stakes, not how ambiguous the request was When should agents ask before acting on ambiguous commands?. Conversation analysis offers a more formal version of the same idea. Human speakers insert short side-exchanges into a conversation to clarify intent or narrow scope before going on. AI agents that chain tool calls silently skip this step and drift away from what the user meant When should AI agents ask users instead of just searching?.
There is also a quieter problem: much of human clarification doesn't look like a question. Research based on Clark's model of communication levels (attention, hearing the signal, meaning, action) finds that most clarifications are statements, and they are often carried by gaze, gesture or tone, not by wording. Systems that detect clarification by looking for question syntax miss most of it Why do clarification requests look different at each communication level?. So 'what users prefer' may partly be a measurement artifact: we count the repairs our systems can see.
Finally, be careful about trusting preference as the target. People report satisfaction even when they are still confused, and continued engagement tracks real understanding better than a satisfaction score Does user satisfaction actually measure cognitive understanding?. A similar gap appears with reasoning formats: users liked planning-style explanations, but simpler chain-of-thought traces helped them catch errors better Do people prefer the reasoning formats that help them verify?. The repair strategy people reach for and the one that actually fixes the misunderstanding may not be the same. The corpus has little direct evidence comparing preferred and effective repair strategies, so that question remains open.
Sources 7 notes
PleaSQLarify reduced clarification steps to two to eight turns by ranking ambiguities by information gain and letting users explore alternatives visually. Twelve participants used multiple repair strategies, suggesting interfaces should support flexible disambiguation rather than forcing one path.
Clarifying questions that target concrete information gaps ("What type of monitor?") consistently beat those that ask users to rephrase their needs ("What are you trying to do?"). Users engage most when they can foresee how answering improves results.
A Wizard-of-Oz study of 20 participants found users prefer agents to automatically resolve low-stakes UI ambiguity like navigation choices, but to pause and request confirmation before high-stakes actions like payments. Stakes, not ambiguity itself, determined user tolerance for autonomous agent behavior.
Tool-enabled LLMs drift from user intent through silent tool chaining. Conversation analysis reveals insert-expansions—clarifying intent, scoping responses, enhancing appeal—as a formal framework for proactive user consultation that prevents misunderstanding instead of recovering from it.
Research maps clarification mechanisms to four levels of communication—attention, signal, meaning, action—each grounded in a different modality (socioperception, hearing, vision, kinesthetics). Most clarifications use declarative form, not questions, making them invisible to systems that detect by syntax alone.
Show all 7 sources
STORM shows users express satisfaction despite internal confusion, especially when unaware of knowledge gaps. Sustained engagement correlates with actual self-understanding, not immediate satisfaction ratings.
A controlled study found participants preferred planning and decomposition formats, yet simpler chain-of-thought traces better supported error detection, trust calibration, and interpretability. The favored formats increased false alarms and unwarranted trust.
Papers this line draws on 8
The research behind the notes this line reads — ranked by how closely each paper relates.
- Clarify When Necessary: Resolving Ambiguity Through Interaction with LMs
- Knowing but Not Showing: LLMs Recognize Ambiguity but Rarely Ask Clarifying Questions
- HumanAgencyBench: Scalable Evaluation of Human Agency Support in AI Assistants
- Clarifying the Path to User Satisfaction: An Investigation into Clarification Usefulness
- Referential ambiguity and clarification requests: comparing human and LLM behaviour
- Mapping the Design Space of User Experience for Computer Use Agents
- PleaSQLarify: Visual Pragmatic Repair for Natural Language Database Querying
- WHEN TO ACT, WHEN TO WAIT: Modeling Structural Trajectories for Intent Triggerability in Task-Oriented Dialogue