Share ideas to improve VoteLoop.
Allow customization of logos, colors, and basic UI elements to match the product’s brand identity.
Add public changelog auto-generated
Allow importing existing feature requests via CSV and exporting data for reporting, migration, or backup purposes.
Offer an embeddable widget or iframe to integrate the feedback board directly into existing SaaS applications.
Add internal notes for admin or owner.
Support tagging system to categorize and filter feature requests by product area, priority, or status.
Add a search bar to the public board that allows users to quickly find and navigate through available features. The search should support keyword-based lookup, enabling users to instantly filter and locate specific feature request without manually browsing the entire board. This improves discoverability and streamlines access to features, especially as the public board grows.
Provide insights into feature demand, engagement, voting trends, and user activity to help teams prioritize effectively.
Users can subscribe to specific feature requests or categories to receive email or in-app updates on status changes, comments, or release updates.
Enable threaded discussions on each feature request, allowing users and team members to collaborate, ask questions, and refine ideas.
Enable seamless multi-tenant architecture by mapping each customer to a unique subdomain (e.g., tenant.voteloop.app). This allows automatic routing, data isolation, and a fully branded experience per tenant supporting scalable white-label SaaS deployments with minimal configuration overhead.
Offer private feedback boards for internal teams, enterprise customers, or beta programs with controlled access.
Support multiple team members with roles/permissions, internal notes, assignment of requests, and workflow management.
Provide a developer-friendly API and webhook system for creating, updating, syncing, and reacting to feature request events programmatically.
Automatically detects when a user requests a feature that already exists in the system or product. If a match is found (e.g., “dark mode”), the system surfaces a subtle prompt like “Is this already available?” instead of creating a new feature request. This reduces redundancy, improves UX clarity, and helps users quickly discover existing functionality they may not be aware of.
Allow users to add comments and feedback directly to feature requests on the public roadmap. This enables open discussion, encourages collaboration, and helps product teams gather valuable insights and prioritize features based on community input.