Skip to content
All updates
  • Improved
  • Fixed
  • Security

HelpJet now says when it is temporarily unavailable instead of showing a generic error, and refreshing a website source skips pages that have not changed.

Whole-site crawls now train every page they find, very long chats work from the most recent messages, and chat requests are checked more strictly before a bot answers.

  • Improved: If HelpJet's servers cannot be reached, the chat window now tells your visitors Chat is temporarily unavailable. Please try again in a few minutes. with a Try again button, in the bot's language. The Page Embed and Chat Link show Chat is temporarily unavailable, and the dashboard shows HelpJet is temporarily unavailable with a way to retry. Before, these showed a generic error or a misleading "Bot Not Found".
  • Improved: Refreshing a website source no longer re-processes pages whose text has not changed. In the automatic refresh, pages that belong to a site, sitemap or crawl are now refreshed together with it instead of also on their own schedule.
  • Improved: In a very long conversation the bot now works from the most recent part of the chat (up to 80 messages) rather than the whole history.
  • Fixed: A whole-site crawl started through the Bot Management MCP now trains every page it finds. A crawl could stop after its first batch of pages.
  • Security: Chat requests are checked more strictly before a bot answers. A visitor can no longer keep a bot answering after its organization has reached its interaction limit by altering the request, a request must end with the visitor's own message, and a single visitor message is limited to 8,000 characters. Testing a bot from the dashboard now requires access to that bot.