AI agents now act on users' behalf inside products. Here's what that means for UX designers, brand trust, and conversion in Southeast Asia.
Agentic AI has crossed a threshold that most design teams haven’t caught up to yet: the interface no longer just responds — it initiates. That changes the design contract with users in ways that go well beyond adding a chatbot widget to your checkout flow.
From Tool to Actor: The Shift Nobody Budgeted For
For most of UX history, interfaces were obedient. You clicked; something happened. The causality was visible, reversible, and legible. As Aurélie Radom observed in UX Design magazine, AI coding agents have revived an older interaction model — describe an outcome, and the system decides which steps to take. The design problem that returns, wearing new clothes, is a classic one: What did the system understand? What has it changed? Can I stop it?
This isn’t hypothetical. Grab’s superapp already surfaces algorithmically sequenced offers without explicit user request. Shopee’s personalisation engine pre-filters search results before a query is complete. These systems act on behalf of users constantly — but most of the underlying UX was designed when the interface was still passive. The gap between what the system does and what the user believes it’s doing is where trust quietly erodes.
From a data architecture standpoint, this problem has a familiar shape: a pipeline that writes to production without surfacing its intermediate states. You’d never deploy that. Yet many product teams ship agentic features with exactly that invisible execution model baked into the UX.
Explainability Is a Design Surface, Not a Legal Disclaimer
The Nielsen Norman Group’s AI UX study guide makes a point that cuts through the hype: AI tools are most useful when practitioners understand both their capabilities and their failure modes. That principle applies downstream to the users of AI-powered products too. Explainability isn’t a compliance checkbox — it’s a conversion lever.
Consider what happens when a Southeast Asian shopper on Lazada sees a recommendation carousel that feels uncannily accurate. One of two things occurs: they feel understood and convert, or they feel surveilled and bounce. The difference is often a single design decision — whether the system communicates why it made that suggestion. A line like “Because you viewed this brand last week” is 11 words that can move a trust metric measurably.
Tokopedia has experimented with surfacing recommendation rationale in-product. The key implementation consideration: this data has to flow from your pipeline cleanly. If your ETL layer doesn’t preserve the attribution signal alongside the recommendation output, your designers have nothing to surface. Explainability as a UX feature requires explainability as a data architecture requirement — specified upfront, not retrofitted.
The Override Layer: Designing for When the Agent Gets It Wrong
Every agentic system will misfire. The design question is whether your interface treats that as an exception or as a first-class scenario. Most current implementations treat it as the former — a buried feedback link, a support ticket flow, an unhelpful “Why did I see this?” modal that leads nowhere actionable.
In high-stakes contexts — an AI-moderated user research session inside your product, an autonomous campaign optimisation tool, a personalised pricing engine — the cost of a miscommunication between system intent and user expectation compounds fast. Marvin’s Live Intercept approach, which runs AI-moderated interviews inline during a session, surfaces this tension directly: the AI is acting on the user’s experience in real time, and the design has to make that agency legible without making it alarming.
For Southeast Asian markets specifically, the cultural dimension matters. Research consistently shows higher sensitivity to perceived loss of control in transactional contexts across the region’s digital commerce users — likely correlated with lower baseline trust in automated systems compared to markets with longer e-commerce histories. An aggressive agentic UX that works in a German B2B SaaS context may read as predatory on a Thai consumer platform. The override and transparency layer isn’t just good UX practice; it’s market-specific risk mitigation.
Practically, this means designing three explicit states for any agentic feature: acting, acted, and undo available. These aren’t modal interruptions — they’re inline, low-friction status signals. Think of them as the commit log your users actually see.
Scaling Agentic UX Across a Design System
The organisational challenge is that most design systems were built around static component libraries — buttons, cards, form fields. They weren’t built to express system states, uncertainty, or autonomous action. As agentic features proliferate across an app or platform, the absence of a shared design language for AI behaviour creates inconsistency that users feel even if they can’t articulate it.
Building an “AI interaction layer” into your design system — a set of components and patterns specifically for communicating agent status, confidence levels, and override options — is now a genuine product infrastructure investment, not a nice-to-have. For teams managing multi-language interfaces across Bahasa, Thai, Vietnamese, and English, this layer also needs to accommodate the text expansion that comes with translated explanatory copy. A 12-word English explainability string can become 22 words in Bahasa Indonesia. If your component wasn’t designed with that variance in mind, the transparency feature you built breaks the layout it was supposed to improve.
Timeline reality: retrofitting agentic UX patterns into an existing design system typically takes two to three sprints of dedicated systems design work before a single production component ships. Teams that treat it as a feature request rather than a system initiative consistently underdeliver.
Key Takeaways
- Design the override and status-visibility layer for AI agents before shipping the agent — users need to see what the system changed, not just what it recommended.
- Explainability copy requires clean attribution data from your pipeline; if your data architecture doesn’t preserve the “why,” your UX can’t surface it.
- Southeast Asian user contexts demand higher-trust agentic UX patterns — aggressive autonomous behaviour that works elsewhere will underperform, or actively damage, conversion here.
The deeper question agentic interfaces are forcing on the industry is one that data and design teams need to answer together: at what point does a helpful system become one that users feel they’re no longer operating, but merely supervising? The answer isn’t universal — it shifts by market, category, and user cohort. The organisations building the infrastructure to understand that boundary in real time, rather than assuming it, are the ones that will hold user trust as AI agency expands.
At grzzly, we work with digital teams across Southeast Asia on exactly the intersection of data architecture and UX strategy that agentic AI is making urgent — helping brands build the pipeline and interface layers that make intelligent systems legible, trustworthy, and measurably effective. If your product is accumulating AI features faster than your design system and data infrastructure can support them, that’s a conversation worth having. Let’s talk
Sources
Written by
Chunky GrizzlyDesigning the foundational plumbing — data warehouses, lakehouse models, and ETL pipelines — that separates organisations with genuine intelligence from those drowning in dashboards.