Skip to content
Agent Factory
Library
Building4 min readReviewed Aug 2026

UI/UX Patterns Users Trust

Approval flows, edit-before-send, and audit logs that make agents feel safe to adopt.

Draft mode first

Default to draft mode: the agent suggests actions, the user approves, edits, or rejects. This is not a limitation - it is the feature that gets enterprise deals signed. No VP approves a tool that sends emails autonomously on day one.

The autonomy progression: (1) all outputs require approval, (2) low-risk actions auto-execute (internal notes, data lookups), high-risk require approval (external emails, financial changes), (3) most actions auto-execute with exception review, (4) full autonomy with monitoring. Most customers spend 2-4 months at each stage.

Build approval UX that is fast, not bureaucratic. One-click approve, inline edit, and 'approve all similar' batch actions. If approving an agent draft takes longer than doing it manually, users stop using the agent.

Show your work

Every agent output should include evidence: citations to source documents, links to API records, diffs showing what changed, and a step timeline showing what the agent did and in what order.

'Based on Refund Policy v2.3, Section 4.1, this customer is eligible for a full refund' beats 'This customer is eligible for a refund.' The first is verifiable in 10 seconds. The second requires blind trust.

Step timelines are especially powerful for complex tasks: '1. Retrieved customer account (0.3s) → 2. Searched 847 policy documents (1.2s) → 3. Found matching clause in Policy #442 (0.8s) → 4. Verified eligibility criteria met (0.5s) → 5. Drafted refund response (2.1s).' Users who see this process trust the output.

5 more sections in this article

  • Easy override
  • Designing the uncertain state
  • The states nobody designs
  • Make the audit trail the interface
  • Worked example: the ticket triage agent

This is Pro content

Get Agent Factory Pro - a one-time payment for lifetime access to full articles, complete build prompts, and everything new.

Use it

The parts of the library that put this article to work.

8 more build prompts reference this article.

Published 27 July 2026. Last reviewed 17 August 2026. We re-read this library on a schedule and date every article, so you can see for yourself how current it is.