Skip to content
Putting technology to work.
Insights to guide decisions and action.

Search articles

A Guide to Designing "Transparency UX" for AI Agents — 5 Requirements for Chatbot UIs Users Can Trust

Table of contents · 7 items

Why "Transparency UX for AI" Is Urgently Needed Now

Moving into 2026, enterprise adoption of AI agents is accelerating rapidly. Gartner predicts that by the end of 2026, 40% of enterprise applications will embed task-specific AI agents, representing a dramatic surge from under 5% the previous year.

Across customer support, internal help desks, and e-commerce shopping assistance, AI chatbots have increasingly interacted directly with users in all kinds of settings. Yet, along with widespread adoption, user distrust has come into sharp focus.

The Ministry of Internal Affairs and Communications' "2025 White Paper on Information and Communications" also reports that consumers feeling anxious about AI usage still constitute a majority. The primary drivers of distrust are the following three:

  • Black-box feeling — Not understanding why the AI arrived at a given answer
  • Sense of loss of control — Feeling that the AI is acting autonomously on its own
  • Anxiety over incorrect answers — The risk of making decisions without noticing mistakes

"Transparency UX" is the approach that confronts these issues head-on.


What is Transparency UX? Differences from Conventional UX

In conventional UI/UX design, the primary evaluation axes were operational efficiency, intuitiveness, and visual appeal. Optimizing button placement, shortening user flows, and reducing friction were the ultimate goals.

In contrast, AI agent UX adds an essential new dimension: "Can users understand, predict, and control system behavior?" This is the essence of Transparency UX.

In an article on agentic AI UX patterns published in February 2026, Smashing Magazine organizes the design patterns needed for agent UIs into three phases.

PhaseObjectiveDesign Focus
Pre-ActionSecuring consentDemonstrate what the AI will do beforehand and obtain user permission
In-ActionMaintaining transparencyVisualize processing progress, decision rationales, and confidence levels in real time
Post-ActionProviding a safety netOperation audit logs, undo features, and human escalation

While conventional UX pursued "usability," Transparency UX differs fundamentally in that it designs for "trustworthiness." Microsoft Design's agent UX guidelines also explicitly declare: "Trust is the most critical currency in UX, and users will only delegate autonomy to systems they can understand."


5 Transparency Design Principles Essential for AI Agents

Below, we explore the 5 transparency design principles that should be built into AI agent UIs, alongside concrete UI implementation examples.

1. Clearly State Capability Boundaries

The most fundamental and important principle is to inform users upfront about what the AI can and cannot do.

IBM's chatbot design guidelines also recommend "immediately notifying users that they are conversing with a chatbot, and communicating its purpose, capabilities, and limitations."

Concrete UI implementation examples:

  • Display a message at the start of conversation: "I am an AI assistant dedicated to customer support. I can answer questions about product usage and pricing. For contract modifications or refunds, I will connect you with our staff."
  • Permanently display an "AI in Assistance" badge in the chat window header
  • Explicitly state "This inquiry is outside my scope of support" for out-of-scope questions, offering alternative solutions

A common failure pattern is leaving AI capabilities vague and showing "Ask me anything." This inflates user expectations boundlessly, and the disappointment when the AI fails leads directly to diminished trust.

2. Visualize Processing Status in Real Time

By displaying what processing the AI agent is performing behind the scenes in real time, you eliminate the feeling of a black box.

AI search services like Perplexity display progress step by step—such as "Searching... → Organizing information... → Generating response..."—while listing referenced sources. This method applies directly to enterprise chatbots as well.

Concrete UI implementation examples:

  • Status indicators: Display phases such as "Thinking...", "Searching internal knowledge base...", or "Generating response..."
  • Progress bars: When referencing multiple data sources, visualize progress such as "Searched 2 of 3 databases"
  • Collapsible thought process: Provide the AI's internal reasoning in a collapsible section for users who wish to inspect details

By utilizing standard protocols such as MCP (Model Context Protocol), it is also possible to structurally reflect in the UI which external tools and data sources the AI is accessing.

3. Present the Rationale Behind AI Decisions

When an AI provides an answer or recommendation, concisely showing "why it reached that conclusion" is key to building trust. Smashing Magazine terms this the "Explainable Rationale pattern."

The first question that comes to a user's mind is, "Why did the AI decide this?" Preemptively answering this question alleviates anxiety regarding autonomous AI decisions.

Concrete UI implementation examples:

  • Rationale cards: Display sources beneath the response, such as "This answer is based on: (1) Product Manual v3.2 (2) FAQ #42"
  • Confidence indicators: Display the AI's level of certainty, such as "Confidence: High" or "Confidence: Moderate (additional details would allow a more accurate response)"
  • Comparative presentations: When multiple options exist, provide alternatives as well, such as "We recommend Plan A, but Plan B is also worth considering"

Displaying confidence is particularly crucial. A UI where the AI can honestly communicate that it "does not know" contributes significantly to long-term trust building.

4. Provide Control Points for Users

As AI acts more autonomously, designing control points where users can intervene, edit, and halt actions becomes increasingly vital. Microsoft's agent UX principles recommend mechanisms that allow "customizing agent settings, controlling on/off states, and reviewing the actions of agents operating in the background."

Concrete UI implementation examples:

  • Approval steps: Always insert a confirmation asking "Proceed with these details?" prior to critical actions (e.g., confirming an order or modifying a reservation)
  • Autonomy slider: A UI allowing users to adjust the AI's autonomy level in stages, such as "Confirm everything / Confirm critical actions only / Fully autonomous"
  • Pause and abort buttons: Controls to stop long-running processes at any time
  • Feedback buttons: A feedback mechanism for each response to indicate "Helpful / Needs improvement"

As discussed in our debate on no-code and low-code in the AI agent era, balancing AI autonomy with human control is a foundational theme in business process design.

5. Fall Back Gracefully Upon Errors

AI makes mistakes. What matters is designing how it behaves when an error occurs ahead of time.

In Smashing Magazine's framework, design patterns for the Post-Action phase include "Action Audit & Undo" and "Escalation Pathway."

Concrete UI implementation examples:

  • Honest error messages: "We apologize, but we could not find sufficient information to answer this question accurately. Would you like to be connected with a staff member?"
  • Undo functionality: A UI allowing users to undo actions executed by the AI (e.g., sending emails or updating records) within a given window
  • Action logs: A dashboard where users can review the historical record of all actions taken by the AI
  • Seamless human escalation: A mechanism that hands over the conversation history intact to a human operator

In the end, an AI that admits mistakes and immediately offers recovery options wins far more user trust than an AI that conceals errors.


Key Implementation Takeaways for AI Agent Transparency UX by Industry

While the five principles of Transparency UX are universal, the focal points differ by industry.

Industry & Use CaseMost Critical PrincipleConcrete Implementation Takeaways
Customer supportFallback upon errorsClarifying scope of coverage, displaying response confidence, seamless handover to human operators
E-commerce (shopping assistance)Presenting AI decision rationaleDisplaying "reasons for recommending this product," automatic comparison table generation, price change alerts
Internal help deskVisualizing processing statusCiting referenced internal documents, real-time application status display
Financial and insurance consultationClearly stating capability boundariesDisclaimers such as "Not investment advice," strict definition of scope based on regulatory compliance
Medical and healthcareUser controlPersistent display of "For informational purposes only," escalation paths strictly prompting physician consultation
Real estate and booking servicesUser controlApproval steps before executing binding agreements, undo functionality for modified terms

A common thread across all industries is that the broader the scope of an AI's autonomous actions, the more rigorous the Transparency UX design must be. The required level of transparency differs fundamentally between a simple FAQ answering bot and an agent executing booking changes or payment transactions.


Implementation Checklist for AI Agent Transparency UX

Use this checklist when integrating Transparency UX into your company's AI agents. It is designed for pre-launch design reviews.

Clearly stating capability boundaries

  • Is it explicitly stated at chat initiation that the user is interacting with an AI?
  • Are both supported and out-of-scope areas communicated specifically?
  • Are alternative solutions provided for inquiries outside the scope of support?

Visualizing processing status

  • Is it displayed in real time that the AI is currently processing?
  • Is the user informed about which data sources are being referenced?
  • Are progress indicators displayed for long-running processes?

Presenting Decision Rationale

  • Are sources cited that substantiate the answer?
  • Is the AI's confidence level conveyed in some manner?
  • When multiple options exist, are alternatives also presented?

User control

  • Is a confirmation step provided prior to executing critical actions?
  • Can users adjust the AI's level of autonomy?
  • Can processing be paused or stopped at any time?
  • Is a feedback mechanism provided?

Fallback upon errors

  • Are honest messages displayed when errors occur?
  • Is there a mechanism to undo AI actions?
  • Is an escalation path to human operators secured?
  • Is the AI interaction history handed over to human operators?

Frequently asked questions (FAQ)

Will introducing transparency UX lower conversion rates?

People often worry that being upfront about an AI's limitations will drive users away, but the opposite effect has actually been reported. Clearly stating the boundaries of its capabilities properly manages user expectations, boosting satisfaction and trust within the covered scope. As a result, conversion rates via chatbots actually tend to improve.

Is transparency UX necessary even for small-scale chatbots?

Yes. Even for a simple chatbot that only handles FAQ responses, at minimum you should incorporate three elements: clearly stating that it is an AI, explaining the scope of coverage, and providing an escalation path to humans. Since smaller scales involve lower implementation costs, we recommend addressing this at an early stage.

How should the effectiveness of transparency UX be measured?

As key metrics, we recommend tracking four items: chatbot task completion rate, customer satisfaction (CSAT), human escalation rate, and repeat usage rate. Comparing these metrics before and after introducing transparency UX allows you to evaluate the impact quantitatively.


Conclusion — Trust in AI agents is built through UI

As the adoption of AI agents accelerates, we have entered an era where business outcomes hinge not just on "whether the AI is competent," but also on "whether the AI is trustworthy." And trust is built not by technical prowess alone, but through UI/UX design.

Let us recap the five transparency design principles discussed in this article.

  1. Clearly state capability boundaries — Properly manage expectations
  2. Visualize processing status in real time — Eliminate the black-box feeling
  3. Present the rationale behind AI decisions — Proactively answer the "why"
  4. Provide user control points — Strike a balance between autonomy and control
  5. Fail over gracefully during errors — Design for resilience against mistakes

These principles apply to AI tools in general, including business utilization of ChatGPT, but it is vital to build them in from the design phase, particularly when operating AI agents across customer touchpoints.

At GleamHub, we assist with UI/UX design for web services, including AI agents. In addition, in our proprietary AI automated response service, "Telmia," we incorporate the transparency UX principles discussed in this article into our implementation, delivering chatbot experiences users can trust. If you have concerns regarding the introduction or design of AI agents, please feel free to contact us.

Share this articleXFacebook
Rui Teruya

Former corporate league baseball player and founder of an IT venture. Founded the company with the drive to ride the fast-moving waves of the world and deliver truly valuable services to society.

Turn this article's theme into your company's next step

Starting from what you want to achieve with your website.

We organize user goals, required features, and ongoing maintenance structures to determine the first steps in development and improvement.

  • Website objectives
  • Features and usability
  • Post-launch operations
Consult on web development and improvements

You can consult with us from the initial conceptual stage. Details from this article will be carried over to the inquiry form.

Receive the latest articles via email · Read the web production guide
Free download

Complete Guide to Web Production: Costs, Vendor Selection & Traffic Acquisition [2026 Edition]

We have compiled cost benchmarks, vendor selection criteria, and traffic acquisition strategies into a PDF.

The PDF and newsletter emails are currently in Japanese.

You will also be subscribed to our newsletter. You can unsubscribe at any time.