Docs

What's new / 2025 weekly updates / February

Feb 23: User Interface Improvements

Week 7, 2025 — February 10 to February 23

User Interface Improvements

  • The entire web dashboard is now a smooth single-page app (SPA) with new pages for categories, articles, tickets, campaigns, analytics, Slack settings, Identity Provider settings, applications, access rules, and more. Navigation feels faster and snappier.
  • Added a full-page loading spinner during sign-in so you won’t see a blank screen waiting for Clerk to load.
  • You can now collapse and expand trees in the UI for easier browsing of nested items.
  • Improved error handling with a new basic error boundary to catch and display issues gracefully.

Smarter AI & Knowledge Base

  • Expanded search queries to improve accuracy when Risotto answers your questions.
  • Added prompts that generate alternative queries for better understanding of user requests.
  • Switched to a new embedding model backend for better knowledge indexing.
  • Fixed stale thread resolution by checking comment dates more accurately, reducing confusion in conversations.

Ticketing & Categorization Enhancements

  • Ticket categories are now configurable per organization and department, with UI support (currently hidden) for managing them.
  • Ticket categorization updates with every new message, keeping suggested categories fresh.
  • Added OpenAI batch jobs to help reclassify tickets automatically for better sorting.
  • Sequential ticket numbering improved for fewer conflicts and smoother ticket creation.

Slack & Integration Updates

  • Reduced the number of notifications sent during knowledge base indexing and reindexing to keep your Slack channels less noisy.
  • Added commands to clean up notification channels, so you can tidy up with ease.
  • Improved Slack message handling to prevent duplicate messages within short time windows.

Performance & Reliability

  • Added retries and delays for Okta API calls when rate limits are hit, improving reliability.
  • Improved concurrency control around ticket number generation to prevent conflicts.
  • Backend indexing tasks now run more efficiently, with better error handling and status tracking.
  • Removed unused or duplicated code and deprecated containers for a leaner, faster system.

Something wrong or missing? Report an issue · View as Markdown