A Support Bot That Never Quotes a Retired Article: Help Centre Search on HyperCrux

Wed, 07 Oct 2026 00:00:00 +0000

Picture a small software company with about 400 help articles and a chat bot on its website that answers questions from them. The bot works the way most of them do. It turns the customer’s question into a vector with an embedding model and finds the articles closest to it. A language model then writes the answer from those.

The weak spot is what happens when an article changes. Say the refund policy changes in March. Someone writes a new article and retires the old one in the help centre, but the vector database keeps its own copy of every article, and the job that should delete the old copy fails without telling anyone. Now the bot quotes a refund window that no longer exists, and nobody finds out until a customer forwards the chat to support. Plans have the same problem. The search only knows which articles are for the pro plan if someone copies that over too, and keeps copying it.

Customer Support on HyperCrux.com

A Support Bot That Never Quotes a Retired Article: Help Centre Search on HyperCrux