Loading
By Chen Fradkin, Data & AI Architect
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.
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.
When questions are necessary, offer multiple-choice options rather than open-ended responses. This approach:
However, options must be genuinely actionable. Only use structured questions when the options are truly actionable-selecting should fully resolve ambiguity.
Poor structured questioning still requires follow-up typing, negating efficiency gains. Strong structured questions should eliminate need for subsequent free-text responses.
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.
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.
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.
Chen Fradkin
Data & AI Architect
CISOs face two connected pressures 1. Attackers using AI to move faster 2.Internal AI agents gaining access nobody fully governs. Both trace back to the same identity problem, and both need the same fix.
Guilad Regev
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.
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”.
Answer twelve questions about what your identity program does today, and the scorecard tells you whether the last mile is yours to build.
How the Twine + Cyera integration closes the loop between data risk discovery and identity remediation.
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.
Filter every question through this checklist:
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 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.
