
You have built your AI agent, added your documents and set your rules. Now comes the nervous part: letting real customers talk to it. This tutorial is for business owners who want to know, before launch day, whether their agent gives correct answers and stays safe under pressure. You will learn what the launch check does, how to read the result, and how to fix what it finds.
Chatting with your agent yourself is a good start, but you only ask the questions you already thought of. Customers ask things you didn't expect, and a few people will try to push the agent into saying things it shouldn't.
The launch check does both kinds of testing for you, in one go, without any customer seeing a thing.
It runs in two parts.
1. Realistic customer questions. About 30 questions are written from your agent's own knowledge and data lists. Around a fifth are deliberately about things your agent does not know. That matters, because a good agent should admit it doesn't know rather than make something up. The agent answers each question in a sandbox, and the answers are graded against your knowledge.
2. Attacks. About 20 tricky attempts are tried, such as:
Each attack is checked by fixed rules on the reply and on what the agent tried to do, and then reviewed by an AI judge. When something fails, you are told how to fix it.
The test happens in a sandbox. Lookups in your data lists are real, but nothing is sent, booked or saved, and nothing is posted to your webhooks. You also don't need to worry about your allowance: the launch check's tokens don't count toward your plan.
Open your agent and go to its Launch check page. The first check starts by itself as soon as an agent is created, so you may already have a result waiting. The agent overview always shows the latest one.
You can run up to 5 checks per agent per day, which is plenty for a fix-and-retest routine.
The result gives you:
Treat "nearly ready" as a to-do list, not a failure. It usually means a handful of small gaps.
If the agent answered a question wrongly, you can correct it right there. Your correction is saved to the knowledge as a verified answer, and the question is tested again. That is the quickest way to close a gap, because you are teaching the agent in exactly the place it stumbled.
A few tips:
The setup check looks at your agent's settings for security and accuracy problems. It can flag things such as:
Each finding links to the page that fixes it, so you don't have to hunt around.
After your fixes, run the check again. Your questions are kept as the agent's test set, so you are comparing like with like and can see the result improve.
A result is marked out of date once your agent's instructions, settings, tools, permissions or documents change. That is your cue to run it again after any meaningful edit, not only before launch.
When you switch on your first channel, you will be warned if the agent hasn't passed. It is a warning, never a block, so the decision stays with you.
The launch check gives you a fast, safe way to find out how your agent behaves before customers do. It asks realistic questions, tries to break the rules, and tells you what to fix. If you are building your first agent, you can try it with iGentrix and see where yours stands before you go live.


