The Bug Where Our Support Bot Sent People Back Where They Started
What was happening
Hugo is the bot behind HeLa's support surfaces — a Help board where people can post questions and requests publicly, plus a direct-message and email channel for one-on-one follow-up. The DM/email side has a deliberate design: answer the immediate question first, then, if it's the kind of complaint or feature request that needs developer follow-up, invite the person to post it on the Help board so it's tracked and enters the queue.
That "post it on the board" line was meant for the DM and email channels only. Instead, it had also been seeded as a row in Hugo's public knowledge base — the same store the board itself draws answers from. The effect: someone posts a question directly on the Help board, and Hugo's board-facing answer tells them to go post it on the Help board. The thread they were already looking at was treated as if it hadn't happened yet.
The fix
The redirect line was removed from the public knowledge-base seed entirely. It now lives only inside the DM/email persona content, scoped to those channels, where the loop can't occur — a board post can't retrieve a KB row that was never public in the first place. On the board itself, the copy now treats the thread the person is already reading as the official record, not a preamble to some other action they still need to take.
A structural check was added on top of that as a second layer: an automated reviewer pass on board-facing replies now specifically flags any draft that still tries to redirect a board poster elsewhere, so the same class of bug can't quietly reappear through a different KB row later.
Why this matters more than it looks
A one-line copy bug is easy to shrug off, but a support bot that tells a person who did the right thing (posted publicly, in the right place) to go do it again is actively worse than a bot that says nothing — it wastes the person's time and makes the support surface look broken even when the underlying triage process behind it is working fine. Fixed 2026-07-08, verified against a live review pass before it shipped.
Q&A
Where was the bad line actually stored? In a public help-board knowledge-base seed row, retrievable by the board's own answer-retrieval path — not in the DM/email channel it was written for.
Does the board still ever point people elsewhere? The DM/email answer-then-invite pattern is unchanged for those channels; what changed is that the board itself no longer redirects a board post back to the board.
How is this prevented from recurring? A reviewer check on board-facing replies now explicitly catches drafts that redirect a board poster elsewhere before they go out.
Source
Internal implementation: scripts/help_seeds/seed_help_kb.py (the redirect line removed from the public Help board knowledge-base seed), help_reviewer.py (the board-facing reviewer rule that flags any redirect attempt) in the HelaSyn engine repository, merged to main 2026-07-08.