
How to Talk to Humans: The Art of Asking Questions
Key takeaways
- The first thing a user sees should be results, not a question.
- Agents should research and narrow options independently before asking anything.
- Structured, multiple-choice questions reduce ambiguity and parsing errors compared with free text.
- Offering options demonstrates the agent understood the problem, which builds trust.
- Question design is a product decision, not an implementation detail, it determines whether an agent feels like a colleague.
Table of contents
- Introduction
- 1. Do the Homework First - Then Come With Questions
- 2. Structured Questions > Free Text
- What Is a Good Option?
- Batching: Watch for Dependencies
- 3. Let the UI Do the Asking
- 4. Spend Your Question Budget Wisely
- Before Your Agent Asks, Ask Yourself These Questions
- Bonus: Your Agent’s Voice Matters
- The Questions Worth Asking
By Chen Fradkin, Data & AI Architect
Introduction#
Interacting with poorly designed AI agents can be frustrating. Users often encounter a barrage of questions before accomplishing anything: “What’s your role? Which department? What system?” This creates a fundamental challenge for AI agent builders: agents need information to function effectively, but excessive questioning makes users feel like they’re completing forms rather than collaborating.
The quality of an AI agent depends not just on its knowledge, but on how and when you ask. Great agents function as collaborators, not interrogators.
1. Do the Homework First - Then Come With Questions#
AI agents should demonstrate competence before requesting information. Research, narrow options, and eliminate dead ends independently. Only then should agents ask questions they genuinely cannot resolve alone.
The example contrasts two approaches: a junior executive assistant asks numerous preference questions, while a senior assistant examines calendars and past trips, then presents two targeted options. Both gather information, but the experienced approach requires less user effort.
The first thing they see isn’t a question-it’s results.
2. Structured Questions > Free Text#
When questions are necessary, offer multiple-choice options rather than open-ended responses. This approach:
- Reduces ambiguity
- Minimizes parsing errors
- Builds trust by demonstrating agent understanding
- Speeds interaction
However, options must be genuinely actionable. Only use structured questions when the options are truly actionable-selecting should fully resolve ambiguity.
What Is a Good Option?#
Poor structured questioning still requires follow-up typing, negating efficiency gains. Strong structured questions should eliminate need for subsequent free-text responses.
See it in action.
Batching: Watch for Dependencies#
Agents should batch independent questions into single interactions, minimizing round-trips. Sequential questions requiring dependency resolution may necessitate additional exchanges, but agents should still bundle independent clarifications together.
3. Let the UI Do the Asking#
The most effective questions emerge through purpose-built interfaces rather than conversation. Instead of explicitly asking five questions, agents should surface task workflows with intelligent pre-filled defaults.
Users review and adjust rather than formulate from scratch. The user is still answering questions…but they don’t feel like questions. They are fields in a flow, pre-filled with the AI Agent’s best guess.
4. Spend Your Question Budget Wisely#
Treat each question as a withdrawal from user patience. Structured questions requiring one click carry minimal cost. Open-ended questions demand cognitive effort and incur higher costs. Questions demonstrating the agent wasn’t listening destroy trust entirely.
Before Your Agent Asks, Ask Yourself These Questions#
Filter every question through this checklist:
- Should the agent solve this independently?
- Does the agent already possess necessary information?
- Can multiple questions combine?
- Is this truly unavoidable?
Bonus: Your Agent’s Voice Matters#
Tone varies by preference, but robotic system-log language fails. Collaborative phrasing-using contractions, “I found” rather than “results found,” invitational questions-creates colleague-like interactions rather than transactional ones.
The Questions Worth Asking#
The goal is never zero questions…Instead, the goal is zero unnecessary questions. Users should think “good thing it asked” rather than “why doesn’t it know this?”
Every unnecessary question shifts interactions toward burden. Well-placed questions create magic.
Chen Fradkin
Data & AI Architect
Frequently asked questions
Related content
NewsTwine’s Co-Founder Justin Woody Interview with On Security
Twine Security Co-Founder Justin Woody joins the On Security podcast to explain why AI Digital Employees, not more tools, are now essential in cybersecurity.
NewsTwine’s Co-Founder Nadav Erez Interview at the AWS Summit
Twine CTO Nadav Erez joined Noa Zilberman at AWS Summit Tel Aviv to share why Twine’s IAM customers “won’t go back to the old way”.
InsightsBuild vs Buy Agent Calculator for Identity
Answer twelve questions about what your identity program does today, and the scorecard tells you whether the last mile is yours to build.
InsightsTwine + Cyera: From Detection to Resolution
How the Twine + Cyera integration closes the loop between data risk discovery and identity remediation.
NewsTwine’s CEO Benny Porat on the Identity at the Center Podcast
Twine Co-Founder and CEO Benny Porat joins Jim McDonald to explain how Alex, Twine’s AI Digital Employee for IAM, closes the execution gap.
InsightsYour JIT Access Program Is Probably a Break-Glass Program
The 2:00 AM emergency is not where just-in-time access breaks down. It is where you find out it broke down months ago. What agentic AI actually changes, and what it does not.

Netanel Fisher