The simple feedback board alternative built on your WordPress posts
Most feedback-board tools, whether SaaS like UserVoice or standalone WP plugins, run on their own data store. SleekView's feedback-board view renders cards with upvotes over your existing CPTs and ACF or Meta Box fields, alongside table and kanban views over the same data.
♾️ Lifetime License available
Feedback boards as views, not as a separate product
The feedback-board space spans a few different shapes. SaaS tools like UserVoice and Canny run the whole product outside WordPress, with embed widgets and SSO bridges. Standalone WordPress plugins (the various "feedback board", "idea board", and "feature request" tools) install inside WP, but typically store ideas, votes, and statuses in their own database tables, much like the kanban plugins do. In both cases, the feedback board is the product, and the WordPress site is the host.
SleekView turns the relationship around. The feedback board is one of three view types over a CPT (alongside tables and kanban), so an idea is just a post in a feedback or idea CPT, with ACF or Meta Box fields for description, area, and status, plus an upvote count maintained by the view. Anything else on the site that wants to read or surface ideas (the public roadmap, an admin dashboard, a search index) sees them as posts because they are posts.
That changes a few practical things. Status updates feed back into the same field a kanban view groups by, so an idea moving from "Under review" to "Planned" shows up in both views without separate plumbing. Permissions follow standard WordPress capabilities. SEO and theme template fall-through work for free, because the public idea page is just a post page. The trade-off is that SleekView is not a feedback-management product on its own; the value comes from the CPTs being part of the rest of the site.
Workflow
How a feedback wall becomes a SleekView feedback board
Create the idea CPT
Import existing ideas
Configure the feedback view
Embed in public and admin
Comparison
SleekView vs simple feedback-board tools at a glance
Differences
What changes when you move off Simple Feedback Board
The Simple Feedback Board way
- Ideas and votes live in plugin or SaaS tables
- Hard to render as a kanban or table over the same data
- ACF and Meta Box fields aren't native on idea cards
- Often admin-only or via embedded widgets
- Reuse in the rest of the site needs bridging code
The SleekView way
- Feedback board over any CPT, no separate data store
- Upvotes tied to a meta field on the post
- Same data as kanban or table with one click
- ACF and Meta Box fields drive cards and filters
- Shortcode and block embed on the frontend
Features
Three things that actually change how you work
Upvotes on real posts
SleekView's feedback board stores upvotes as a meta field on the post, with one vote per logged-in user. The vote count is part of the same record everything else on the site already reads, so a top-voted idea is visible to themes, REST clients, and reports without extra integration.
Ideas as full posts
Each card is a regular WordPress post with a slug, an author, and the WordPress comments system. Comments, taxonomies, and theme single-post templates work without bespoke setup, so a feedback-board idea fits naturally next to articles, products, and other CPTs.
Status changes feed kanban
The status field a feedback board uses for filtering (Open, Planned, Shipped) is the same field a kanban view groups by. Toggle one view to the other for the same data; the team's roadmap board and the public feedback wall stay in lockstep.
Migration
Moving from a separate feedback-board tool to SleekView
1. Define the idea CPT
Create an idea or feedback CPT with ACF or Meta Box fields for description, area, and status. Add a vote-count meta field SleekView's feedback board can read and update.
2. Import existing ideas
Export ideas from the current tool and import them into the CPT via WP All Import or a similar plugin, mapping fields one to one. Vote counts can be brought across as initial values on the meta field.
3. Configure the feedback view
Point a SleekView feedback board at the new CPT, choose which fields show on the card, and enable upvoting for logged-in users (or anonymous, depending on policy).
4. Embed and decommission
Drop the SleekView feedback-board shortcode or block where the existing widget lived. Once verified, retire the previous tool, or keep it for any features (NPS, surveys) SleekView does not aim to cover.
Audience
Who tends to consider SleekView for feedback boards
Public roadmaps with voting
When the same ideas need a public feedback page (with upvotes) and an internal kanban (grouped by status), SleekView's two view types over one CPT remove the duplicated data set.
Sites that already use ACF or Meta Box
Teams who structure content with ACF or Meta Box can extend an idea CPT with the same fields they use elsewhere. SleekView reads them straight onto cards, no per-board mapping required.
Internal tools spanning multiple views
Support requests, internal feature requests, and operations ideas often need a board (for prioritisation), a table (for reporting), and a kanban (for execution). SleekView ships all three over the same CPT.
The bigger picture
Why feedback boards belong inside the rest of the site
Feedback boards are interesting because the data they hold matters far beyond the board itself. A top-voted idea is roadmap input, a planned idea is a release note, a shipped idea is a marketing story, and a rejected idea is a record the support team will reference for years. Tools that own the data, whether SaaS products or WordPress plugins with their own tables, treat the feedback board as the product and the rest of the site as a host.
That works while the feedback wall stays self-contained, and breaks the moment the team wants to surface ideas anywhere else: a public roadmap page, an internal dashboard, an automation that nudges users when their idea ships. The bridging code never quite lines up, because plugin tables and SaaS APIs are not posts, and posts are how WordPress thinks about content. SleekView's contribution is to make the feedback board a view, not a product.
The ideas live as CPTs, the votes live as a meta field on the post, the statuses live as a taxonomy or ACF field, and the feedback board is one of several views over that data. The same CPT renders as a kanban for the team and as a feedback wall for users, with no duplicate data set, and any other plugin or theme already knows how to read the records. The board stops being an island, and becomes a part of the site whose data was always going to outlast the original feature request.
Questions
Common questions about switching from Simple Feedback Board
No. Tools like UserVoice and Canny ship features SleekView does not include: SSO across SaaS, NPS surveys, customer messaging, status email digests. SleekView is a view layer, so the feedback-board view is one rendering of CPT data, not a standalone product. For full feedback-management workflows the dedicated tools remain the right pick or run alongside SleekView.
As a meta field on the post, with a separate record of which user voted (to enforce one vote per user). Vote counts are part of the post, so they are queryable with WP_Query and visible to themes and APIs without extra integration.
Configurable per view. Common setups require login (which removes vote-stuffing) or allow anonymous votes throttled by IP. Both options are part of the feedback-board view configuration.
As a field on the CPT, typically an ACF select or a taxonomy. The feedback board uses it for filtering and badges; a kanban view over the same CPT uses it for grouping. Updating the status anywhere updates it everywhere because there is one source of truth.
Yes, by enabling WordPress comments on the CPT. SleekView's feedback board card links to the standard single-post template, so comments use the existing theme and moderation workflow.
Export the ideas (and votes if available), create a matching CPT with ACF or Meta Box fields, and import via WP All Import or a similar plugin. Initial vote counts can be set as meta values; from there, voting continues inside SleekView.
Yes. Use a taxonomy or ACF select for category, then expose it as a filter on the feedback view. The same field can drive grouping on a kanban view or columns on a table view.
Yes, that is a core SleekView pattern: a public feedback board for users to vote on ideas, plus an internal kanban grouped by status for the team to work through them, both over the same CPT, no duplication.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout