Case study

Catching an AI chatbot that regressed on every prompt change

The assistant regressed on every prompt change, with nothing to catch it. We built the eval suite that turned that into a gate.

AI support chatbot · LLM behavior
no eval coveragegraded golden set on CI

The challenge

A live AI support chatbot regressed on every prompt change — a small wording tweak would quietly break answers that used to work, and nobody noticed until users complained.

The context

The team was iterating fast on prompts and swapping models, with no way to tell whether a change helped or hurt. Quality was a matter of opinion, and every release was a gamble.

What we did

  • Built a golden set of representative questions and expected behaviours from real conversations.
  • Graded answers for faithfulness, correctness and tone, flagging hallucinations and dropped context.
  • Wired the evals into CI so every prompt or model change is scored before it can ship.
  • Handed over the suite and the CI gate for the team to keep extending.

The outcome

Prompt and model changes are now scored automatically, and a regression blocks the release instead of reaching users. Quality moved from opinion to a number the team can trust.

Stack
promptfooRagasLangSmith
Get a free audit

Ship the next release without holding your breath.

Tell us what you're building — or what's breaking. We reply within one business day with a concrete plan, not a sales deck.

Or, the direct route
contact@qatestingplus.com
Replies from a human, not a CRM.

By sending this message, you agree to our Privacy Policy.