Since my last post, the philosophy of “Agentic AI application” has moved from theory to blueprint. Instead of just discussing the power of AI Agents, we’re planning a concrete use case: an AI Personal Assistant designed to eliminate the most frustrating part of any customer portal — the forms. This post details our initial brainstorming and high-level vision for a truly transformative service experience

The Vision: Eliminating Customer Portal Friction The core problem we aim to solve is the tedious, friction-filled process of traditional form submission in a customer portal. Users shouldn’t have to spend time searching for the right forms, understanding field requirements, and filling them out.

The end state for this project is a personalized service experience where our AI agent acts as a personal concierge, intelligently submitting the correct requests on the user’s behalf. Its effectiveness hinges on its ability to understand the full user context: knowledge of previously submitted requests and a detailed understanding of the assets being managed by the user.

The User Experience: Conversational Service, Zero Cognitive Load To truly improve user satisfaction, the interaction model must feel natural and intuitive. We are planning a conversational interface that mimics chatting with an experienced human service support agent. The user simply states their need — without navigating menus, searching for forms, or ensuring they’ve ticked every box.

The primary goal is to shift the cognitive load from the user to the agent, creating a genuinely seamless and efficient way to initiate support or service requests. This isn’t just a chatbot; it’s a dedicated assistant designed for zero friction request initiation.

Predicting Intent from Ambiguity While the conversational interface is the most visible feature, the most complex challenge lies beneath the surface: accurate user intent prediction.

It’s relatively easy to build a system that can spot trends in high-volume, repetitive tasks. The real difficulty arises when trying to anticipate individual user needs where past requests may not reveal a clear pattern, or when a user is dealing with an entirely new issue —what we call intent ambiguity.

Our initial high-level planning is focused on tackling this uncertainty. The architecture must prioritize the agent’s ability to perform sophisticated reasoning and combine disparate data points (asset data, past tickets, and real-time conversation) to achieve the holistic context needed to act effectively — even when a clear trend is not apparent.

Moving from Blueprint to Functional Design This brainstorming phase has solidified the “why” and the “what”. The next phase of this project involves moving into detailed technical design. This means:

• Mapping out the required data sources and API integrations
• Defining the agent’s memory and reasoning loops
• Most critically, designing the API guardrails that will ensure the agent operates securely and strictly within organizational policy

Stay tuned for future posts as this blueprint evolves into a functional design document — the first step toward building the agent!

- Kenny