No. SleekView Feedback reads the existing kustomer_conversation posts, post meta, and taxonomies that Kustomer for WordPress already writes. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your agents see in the admin, so all reports stay aligned.

Yes. The Feedback view inherits the same query filters as the SleekView Tables and Charts surfaces. You can restrict by ticket status, category, product, or any custom meta. Most teams expose only Planned, In progress, and Shipped statuses on the public board and keep open or internal tickets behind the admin.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged in users. You can also require a WordPress account before voting if your customer base already has accounts. Vote totals stay consistent across pageloads and devices for known users, with cookie based dedupe for anonymous voters.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync tickets across, then maintain two sources of truth. SleekView Feedback reads Kustomer for WordPress data live, so the board, the agent queue, and the reports always show the same numbers. There is nothing to sync because there is

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the category. The SleekView block exposes a dropdown for each role so you map the columns once through the block UI and never touch the underlying template to change configuration.

By default upvotes update the meta silently to avoid notification spam in busy agent inboxes. You can opt in to firing the standard Kustomer for WordPress ticket updated action on each upvote if you want agents to see live demand inside their existing notification flow, or threshold it to alerts every ten or fifty votes for a

Yes. SleekView lets you scope the query to one or many terms in any Kustomer for WordPress taxonomy, so you can run a board per product line, per language, or per support tier. Each board is a separate block on a separate page, all reading from the same underlying ticket store with their own filter and field mapping values

Because SleekView Feedback reads whatever query you point it at, you can swap the source from kustomer_conversation to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You only re map the column roles in the block settings, and the public URL stays the same