Your chatbot should sit an exam
before it talks to customers.
Most chatbot platforms hand you a bot and wish you luck. You find out it misquotes your prices when a customer screenshots the chat. There's a duller, better order of operations: build the bot, examine it, then let it loose.
A pre-flight check is an automated exam your chatbot sits after it's built from your website and before it meets a customer. Around ten questions drawn from your own business information are answered by the real bot and scored for groundedness by a judge model; then five adversarial probes — injection, jailbreak, price-fishing, off-topic and policy-fishing — try to break it. Your portal shows the result in plain English: "your bot passed 9/10 checks".
You wouldn't publish a website
without reading it first.
Yet that's exactly how most chatbots go live. Paste in a URL, wait a minute, embed the widget, hope. The bot is fluent from the first message — fluency is the easy part — and the first person to discover what it actually knows is a paying customer. If it invents a discount, misquotes your hours or makes up a refund policy, you find out from a screenshot, not a dashboard.
The fix isn't a better disclaimer. It's marking the bot's homework before term starts.
Ten questions from your own site.
Marked by a judge.
After every knowledge-base build, automatically, the bot is tested on the material it was just taught. No mock answers — the real bot, the real pipeline.
RE-RUNS ON EVERY REBUILD · NO EXTRA COST
A plain-English score before a single visitor chats — and the failed checks name the exact question that tripped the bot, so you fix the knowledge rather than guess at it.
Then five scripted attacks
try to break it.
Answering politely is only half the job. The other half is refusing to be steered. Each probe mimics a real thing visitors — or bored teenagers — will try.
A low score is useful.
It's a to-do list.
A bot that fails its exam is almost never a stupid bot — it's a faithful mirror of a website with holes in it. The fix is usually content, not code.
Read the failures first
The portal names the exact questions that failed. "What are your opening hours?" failing means the hours aren't on your site — or they're buried in a photo of a door sign the scraper can't read.
Fix the source content
Put prices, hours, service areas and policies in plain text on your site, then rebuild. The exam re-runs automatically, so you see the score climb — and your website gets better for humans too.
Patch gaps directly
For one-off answers, use the content-gaps list in your portal: type the answer once and it's in the knowledge base instantly — no rebuild, no developer. Live questions visitors ask get clustered there too.
The full accuracy system — exam, runtime guardrails, feedback loop — is covered on the AI chatbot accuracy page. More posts on the blog.
Asked
plainly.
What is a chatbot pre-flight check?
What are the five adversarial probes?
What should I do if my bot’s score is low?
Does a passing score guarantee the bot never makes a mistake?
Does the pre-flight exam cost extra?
Keep reading: the accuracy system · more from the blog · pricing
Watch your bot pass its own exam.
Build it free from your website in 60 seconds, then open the portal and read the score yourself. No card, no commitment.
Build my chatbot · free