flowful.ai
Back to blog

How to stop an AI agent from making things up

AI agents invent answers when they lack context. How to give yours the right context, keep a human in the loop and test its answers.

Published
How to stop an AI agent from making things up

“What if it makes something up?” is the question business owners ask us most about AI agents. The short answer: an agent makes things up when it lacks context. ChatGPT and Claude know nothing about your company until you connect them to your data.

Key takeaways

  • It is all about context. An agent invents answers when it lacks information, not because the technology is broken.
  • ChatGPT alone does not know your company. Connected to your documents and live data, the same model gives useful answers.
  • When context runs out, the agent should say so, and pass the question to a person.
  • Keep a human in the loop. Where mistakes are costly, the agent drafts and a person edits and sends.
  • Testing shows the gaps. Every wrong answer points to context the agent was never given.

Why AI agents make things up

A model is built to write fluent, plausible text. It has never read your return policy, but it knows what return policies usually say, so it writes one.

The same customer question, "Can I return a sale item after 30 days?", answered two ways by the same model. Without context it has nothing to read, so it writes what return policies usually say: all items can be returned within 60 days for a full refund. With your context, it reads the returns policy (sale items: 14 days, store credit only) and answers from it, citing the policy as its source

The stakes are real: in 2024 a Canadian tribunal held Air Canada to a bereavement fare policy its chatbot had invented.

Give it two kinds of context

Two kinds of context. Your documents (FAQ, policies, catalogue) change rarely and go into a knowledge base, searched before every answer. Live data (stock, orders, slots) changes every day and is read from your systems through a live connection, never guessed. Both feed one AI agent, which checks them before answering

  • Documents: before each answer, the agent searches your knowledge base and answers from the passages it retrieves. This is called RAG, retrieval-augmented generation. Answers are only as good as your content. If two pages give different opening hours, the agent will pick one, so cleaning up is part of the project.
  • Live data: if a number or a date could change tomorrow, the agent reads it from your systems. It never makes it up.

When context runs out, say so

Left to itself, a model would rather say something than nothing. A well built agent checks first, and when neither your documents nor your systems have the answer, it says “I don’t know” or hands the conversation to your team, transcript included.

A customer question goes to the AI agent, which checks first and ends in one of four safe outcomes: live data read from your shop, CRM or calendar; an answer from your FAQ with the link; a sensitive case handed to your team with the transcript; or "I don't know" plus a next step. A dashed frame around the whole flow reads: tested before launch, conversations reviewed after

Keep a human in the loop

Where a wrong answer would cost you, the agent should draft and a person should decide. That is why Email Automation and TicketFlow draft replies by default: your team edits or approves each one before it goes out. Every edit also tells you what to add to the agent’s context.

The human-in-the-loop flow, the default in Email Automation and TicketFlow: an email or ticket comes in, the AI drafts a reply from your context, your team edits or approves it, and a person sends it. A dashed arrow runs from the team back to the draft: each edit adds to the agent's context

Test to find the gaps

Before launch, run fifty real questions through the agent. After launch, read the conversations. Each wrong answer tells you what to add.

The test loop in four steps: ask 50 real questions, awkward ones included; check every answer against your sources; spot the gap, since a wrong answer means missing context; add it, as a document, live data or a handoff rule. A dashed arrow returns to the start: repeat after every change, then on real conversations

What does not work on its own

FixWhat it doesWhy it is not enough
”Do not invent anything” in the instructionsMakes the model more cautiousA sentence cannot supply missing information
Turning down the “temperature”Makes answers more consistentAn agent can be consistently wrong
A newer, bigger modelHallucinates less oftenIt still fills the gaps

The model is not the problem, the context is

You can use ChatGPT today. But it has never read your policies or your customer history, so it can only answer in general terms. We build on the same models, and our job is connecting them to your company data and tools, then running the agents:

Your company data on the left (documents such as FAQ, policies and catalogue; business tools such as CRM, shop and ERP; email and calendar) feeds AI agents built on ChatGPT, Claude and other models, connected and run by us. On the right, the agents serve employees through an internal chatbot, and customers through a web chatbot, a phone receptionist and TicketFlow for support tickets

For employees, that means an internal chatbot. For customers, a web chatbot, an AI phone receptionist and TicketFlow.

Tell people they are talking to an AI

Since 2 August 2026, the EU AI Act requires AI agents that talk to people to say so from the first interaction. Our EU AI Act guide for SMEs covers the rest.

Conclusion

An agent that makes things up was asked to answer without the context to do it. Connect it to your data, let it say “I don’t know”, keep a person on the decisions that matter, and keep testing.

That is the work we do. To see what it would take for your business, book a discovery call.

Which task eats most of your week?

Book a 30-minute call. We'll tell you whether a package covers it or it needs a custom build.

Get in touch