If you're here, you've landed in the new home for Guru feature requests, product feedback, and release notes. We wanted to give you a quick rundown of what's changing and what this space is for.

We know the community has been a place many of you used to ask questions, share feedback, and connect with our team — and we don't take that lightly. This wasn't a decision we made overnight, but after an honest look at how the space was being used, it was clear we could be serving you better.

Feature requests aren't going away — they're getting an upgrade. You're looking at it. Here's what that means in practice:

You can start submitting and tracking feature requests right now.

The old community will remain accessible until April 27th. After that, the site will no longer be available.

We've already migrated the majority of feature requests over, so there's no need to re-add them.

Our help center and support team aren't going anywhere. If you have a question or run into something unexpected, you can reach us here.

We're genuinely excited about this change — this new setup gives us a much better way to close the loop between your feedback and our roadmap, and we think you'll notice the difference.

Thanks for being part of this community. We're looking forward to continuing the conversation in a new place.

— The Guru Product Team

You can now revert a KA Quality run directly from the Quality Log.

If a Quality automation produces unexpected results, just click "Revert Run" on the log entry to restore all affected content to its previous verification state. A confirmation modal previews the changes before anything happens, and for large runs, the revert processes in the background with a notification when it's done. You can also navigate directly to editing the Quality rules if some tweaks need to be made.

Quality runs can be reverted for up to 15 days after they complete.

You can now connect Vitally as a source in Guru. Once connected, your team's account data, notes, tasks, and projects from Vitally become searchable through the Knowledge Agent. Ask questions like "what's the health score for Acme Corp?" or "what risks were flagged this week?" and get answers grounded in your CS data.

You can now connect Fathom to Guru to bring your meeting recordings, transcripts, and summaries into your knowledge base.

Once connected, your Knowledge Agents can search across your Fathom meetings to surface action items, decisions, and discussion context — making it easy to find what was said without scrubbing through recordings.

Meeting transcripts, AI-generated summaries, action items, attendee info, and recording details.

Filters available: Narrow results by date, who recorded the meeting, or transcript language.

Generate an API key in your Fathom account settings and add it in Guru's integration configuration. For the broadest coverage, we recommend using a Fathom Team Edition account so all team-shared recordings are included.

You can now filter Sources and Collections in Knowledge Agents by Date, Collection Folder, and Source Attributes (i.e. data from that specific sources, like "Owner" in SalesForce.)

Date filters support and using relative or absolute values.

Folder filters let you scope a Collection to specific folders.

Source Attribute filters let you narrow external sources like Salesforce or Jira by Record Type, field values, and more.

Filters can be added to a source via the Knowledge Agent menu or when you're adding a new source to Knowledge Agent.

Head on over to Manage>Knowledge Agents to start using filters!