All articles
Artificial Intelligence

An AI Agent Without Context Is Just a Confident Stranger

An AI agent can sound smart and still get it wrong. After a frustrating airline chatbot experience, here’s why reliable enterprise AI needs three things beyond the language model: Knowledge (the right facts), Memory (what happened before) and Action (the ability to actually get things done). As models become commoditised, context engineering will be the real differentiator. We’re building this at ROVA AI with ROVA Cortex (enterprise memory) and the ROVA Knowledge Base. Because the real test of AI isn’t how well it talks, it’s whether it helps the customer reach the outcome.

NITIN GURUOct 15, 2026
An AI Agent Without Context Is Just a Confident Stranger

Why memory, knowledge and context are becoming the real differentiators in enterprise AI.

Recently, I contacted an airline to reschedule a flight.

Within moments, I realised I was interacting with an AI agent. It could converse naturally, respond quickly and keep the conversation going.

But there was a problem.

It kept referring to the wrong departure location.

I corrected it. I explained what I actually wanted to do. I pointed out that I had no upcoming flight from the location it kept mentioning.

Yet the agent continued giving me incorrect information.

Eventually, I stopped trying to explain myself and asked to speak to a human.

It was a frustrating experience. But as someone building AI agents, it also left me thinking about a much bigger problem.

We are getting remarkably good at making AI talk. We are still learning how to make it understand.

The illusion of intelligence

One of the most interesting things about today's AI is how convincing it can be.

It speaks fluently. It responds confidently. It can explain complex subjects, summarise documents and hold conversations that would have seemed impossible just a few years ago.

But fluency and correctness are not the same thing.

An AI agent can sound intelligent while working with incomplete information, misunderstanding a customer's situation or making assumptions that should never have been made.

In my airline experience, the problem wasn't simply that the AI gave me a wrong answer. It was that the conversation wasn't converging towards the correct answer, even after I repeatedly clarified my request.

That is a very different problem from making an AI model smarter.

A more articulate AI can still give you a more articulate wrong answer.

For businesses, this distinction matters enormously. When AI represents your brand in front of a customer, the customer doesn't evaluate the underlying model, the prompt or the architecture.

They evaluate the experience.

And they hold your business responsible for it.

Three things a reliable AI agent needs

I believe we need to look beyond the language model itself and think about the broader system that enables an AI agent to operate reliably.

There are three important ingredients.

1. Knowledge: Does the AI know the facts?

Imagine an airline AI agent that doesn't have access to accurate flight schedules, booking policies, fare rules or rescheduling options.

It may be an excellent conversationalist. But it cannot reliably help a passenger change a flight if it cannot access the right information.

The same applies across industries.

A healthcare AI agent needs reliable information about services, appointment procedures and relevant policies. A banking agent needs accurate product terms and transaction rules. A sales agent needs current product information, pricing and eligibility criteria.

This is where a well-managed business knowledge base becomes important.

It gives the agent a way to retrieve relevant information from approved business sources rather than relying entirely on what the underlying model may already know.

But knowledge alone isn't enough.

2. Memory: Does the AI remember what happened before?

Let's assume the airline agent has access to every flight schedule and rescheduling policy.

It can still fail if it cannot correctly identify the booking in question, remember the departure location the customer specified or retain the clarification made earlier in the conversation.

Knowledge tells the AI about the business.

Memory helps it retain relevant information about the customer and previous interactions.

That distinction becomes even more important when conversations span multiple channels.

A customer might call on Monday, send a WhatsApp message on Tuesday and return through the website on Friday. The business may have information about all three interactions, but unless the relevant information can be connected and retrieved, the next interaction can still feel like starting from scratch.

Customers don't think in channels, databases or sessions.

They think in relationships.

They expect the business to remember what they have already explained, what they need and what was promised to them.

3. Action: Can the AI do something useful with what it knows?

Even an agent with accurate knowledge and relevant memory can fail if it cannot act on them.

Knowing a customer's booking details isn't the same as successfully rescheduling the flight.

The agent may need to retrieve the booking, check current availability, explain the applicable rules, confirm the customer's choice and execute the change through the airline's booking system.

And if the requested change cannot be completed, it should explain why or escalate to a human.

This is the difference between an AI that produces a plausible response and an AI agent that helps deliver an actual outcome.

Knowledge informs the answer. Memory provides context. Actions turn that context into outcomes.

These capabilities must work together.

Why context is becoming the next competitive advantage

As AI models become more capable and widely accessible, businesses will increasingly have access to similar underlying intelligence.

The differentiator will not always be which model a company uses.

It may be how effectively that company connects AI to its business knowledge, customer history, operating systems, rules and workflows.

Consider two businesses using similarly capable AI models.

The first deploys an agent that answers questions using general instructions.

The second gives its agent access to approved business knowledge, relevant customer history and the tools needed to complete tasks within defined boundaries.

When a customer returns with a question about a previous interaction, the first agent may ask the customer to start again.

The second can retrieve the relevant context, understand what has already happened and continue the interaction appropriately.

The difference isn't necessarily the intelligence of the model.

It's the quality of the system around it.

This is why I believe context engineering will become as important to enterprise AI as model selection. Businesses will need to think carefully about what information an agent can access, what it should remember, when that information should be retrieved and how it should influence decisions.

More data is not automatically better. More memory is not automatically better either.

The goal is to make the right information available at the right time, with the right permissions and enough context to support the right action.

What we're building at ROVA AI

These are some of the questions we are exploring as we build ROVA AI.

We are developing two complementary capabilities.

ROVA Cortex - Enterprise Memory for AI

The idea is to give AI agents persistent customer and business context across conversations, channels and interactions. Instead of treating every interaction as an isolated event, agents can retrieve relevant history and use it to inform what happens next.

ROVA Knowledge Base

The goal is to help businesses organise and make their information accessible to AI agents, including content from documents, policies, FAQs, manuals, images and other supported sources. This gives agents a more grounded way to retrieve business-specific information when responding to customers.

These capabilities address different problems, but their value increases when they work together.

Cortex addresses the question: What relevant context should the agent remember?

The Knowledge Base addresses the question: What reliable business information should the agent use?

Connected to the right systems and tools, an agent can use both to make better-informed decisions, take appropriate actions and recognise when human intervention is necessary.

This is an evolving area of our product development, and there is still substantial engineering work involved in making these systems reliable in real-world environments.

But the direction is clear.

We need to move beyond AI that merely generates responses towards AI that operates with relevant context, reliable information and well-defined boundaries.

The real test of AI isn't how well it talks

My airline experience reminded me of something important.

A customer shouldn't need to understand AI architecture to get good service. They shouldn't need to know whether an agent has memory, whether a knowledge base is connected or whether the right information was retrieved.

They should simply experience a business that understands their request and helps them move forward.

That is the standard we should be working towards.

Not AI that sounds human.

Not AI that answers every question confidently.

But AI that knows what information it needs, remembers what matters, acts within its boundaries and admits when it needs help.

Because ultimately, the measure of an AI agent isn't how convincing its conversation sounds. It's whether it can reliably help the customer achieve the intended outcome.

And that requires more than intelligence.

It requires context.

Cheers,

Nitin Guru

Recommended reads

View all →
When AI Agents Start Talking to Each Other
Artificial IntelligenceOct 15, 2026

When AI Agents Start Talking to Each Other

What if booking a cardiology follow-up took one request instead of three calls? That’s the promise of AI agents talking to each other, but agents built by different companies are islands. A2A (Agent2Agent) is an open protocol that gives them a shared language: an Agent Card to discover each other, tasks that can pause and resume, and results handed back, all while each organisation keeps its internal data private. The hard parts aren’t the protocol: trust, permission, accountability and context. A common language only helps if the agent knows the business, remembers the customer and can act within clear limits. That’s what we’re building at ROVA AI with Cortex and the Knowledge Base.

Read article
When Agents Build a Backchannel: AI Security Is Now an Engineering Problem
Artificial IntelligenceOct 15, 2026

When Agents Build a Backchannel: AI Security Is Now an Engineering Problem

AI is moving from saying things to doing things, and security has to move with it. From AI-designed viruses that worked in a lab, to agents that built a hidden backchannel, to “mind viruses” that spread through agent memory, the safety question is no longer “what did the AI say?” but “what was it allowed to do?” Hospitals solved this long ago with role-based access, sign-offs and audit trails. Five practical principles for agents: least privilege, isolation, treating memory as untrusted input, verifying before executing, and logging and capping everything. At ROVA AI, security runs through knowledge, memory and action.

Read article
We Cut Our LLM Bill by 80% - And Never Touched the Model
Artificial IntelligenceSep 15, 2026

We Cut Our LLM Bill by 80% - And Never Touched the Model

This article explains how ROVA AI reduced its LLM costs by nearly 80% without switching to a cheaper model or compromising quality. The savings came from shorter prompts, concise structured outputs, prompt caching, avoiding unnecessary model calls, and batching non-real-time tasks. The key lesson: AI costs depend less on model choice and more on efficient token architecture.

Read article