I'm interested in hearing how everyone handles feature requests and bug reports from users. I initially set up a basic feedback form, but it turned out to be too one-sided. Without users providing their email, I've had no way to follow up for clarification. Even with emails, it feels like conversations get lost in the shuffle.
So, I'm currently developing a different approach—a system that mimics a Reddit-like structure, integrated straight into the app. Users can browse and upvote existing requests and bugs, and contribute their use cases directly. It can be fully public, or certain sections can be kept private as needed.
Additionally, there's a support chatbot that pulls from our knowledge base. If a user mentions a bug or feature request while chatting, it gets added automatically, skipping the need for a separate form. From a development standpoint, it features a Jira-like board for task organization and tracking. When we launch a new feature or fix a bug, everyone who showed interest gets notified.
I'd love to know if this is something you would find valuable as a SaaS product. Are there features you believe I should include to make it truly beneficial?
1 Answer
We usually use a single tracker combined with a basic form or email for managing feedback, relying on triaging and labeling to handle the noise. I'd consider adopting something like your system if it genuinely streamlines our process and minimizes duplicate entries rather than just adding another channel to monitor.
Thanks for sharing! We're focused on creating a centralized system that integrates support chat, bug reports, and feature requests. We're also tackling the duplication issue—when a user tries to submit a request, it’ll suggest similar existing entries for them to engage with instead. Does that sound helpful for your workflow?