Customise Aha! to Slack output

A deeper Slack integration for the Aha! Ideas portal would significantly improve customer adoption, engagement, and the overall value of the platform.

Today, our customers spend the majority of their day in our application and in Slack. Aha! is an important system for collecting ideas and sharing release notes, but it sits outside of their normal workflow. As a result, most customers only visit the portal occasionally, often just once a month, typically to review release notes. This limits both engagement and the quality of customer feedback.

Allowing customers to search, create, update, and comment on ideas directly from Slack would make interacting with the Ideas portal a natural part of their daily work. Beyond basic interactions, an AI-powered Slack integration could enable users to ask natural-language questions about existing ideas, feature requests, release notes, and other portal content without leaving Slack. This would increase visibility into existing enhancements, reduce duplicate submissions, and help customers find answers more quickly.

There is also an opportunity to improve the quality of submitted ideas. A Slack skill or guided workflow then becomes a great option so as to help users capture the right level of detail, ensuring ideas are submitted consistently and with enough context for effective evaluation.

The same value extends internally. Our employees use the Ideas portal to submit enhancements, provide feedback, and track potential production issues. Like our customers, however, they spend their day in Slack rather than Aha!, so adoption is similarly limited. Enabling employees to interact with the Ideas portal from Slack. whether to submit ideas, search existing requests, generate reports, or ask questions, would reduce interruptions to the product team and empower users to find answers independently. Since many employees already have reviewer access, conversational access to reporting and portal content would be especially valuable.

Ultimately, if Aha! is intended to be the source of truth for product feedback and roadmap visibility, it needs to meet users where they already work. Requiring users to leave their primary workflow to access a tool they use infrequently creates unnecessary friction. Expanding Slack capabilities would not only increase engagement with the Ideas portal but also reduce support overhead, improve the quality of feedback, and strengthen Aha!'s role as the central hub for product collaboration.

customize output: we'd like the ability to update the text that gets sent (for example, we currently send a notification to a team slack channel when an idea gets assigned to their product area. it says "Elizabeth updated Product Area field on Idea xyz". We'd like the option to customize that text, to say something like "xx Product Area has a new idea, check it out here".

remove unwanted fields: there are a few things that get auto added like record type, idea name, status, assignee, workspace. it would be great to be able to remove some of these because in our case, things like record type and workspace are irrelevant.

thanks!

We are also running into an issue with slack notifications where we do not want our employees seeing all feature status changes, we'd ideally want to filter it so that only features with certain 'lasso-only' tags go to slack so that the product team can add more private features in Aha that may not be ready for employee visibility

We want to have a slack channel open to our company to see a stream of ideas being submitted and when the status is changed. Today, there is no way to hide the score information, which we see as private information to the product team.

The workaround we could use (but are afraid to), would be to wait five minutes after updating the status of an idea to score it to avoid a score update trigger. If we update the status and score at the same time, both pieces of information will be posted for entire company visibility (not good).