Both versions are supported. SleekView reads the ticket tables as long as they exist. Fluent Support Pro adds custom fields, automations, and richer statuses, which gives you more mapping options for vote columns and status badges on the public board.

Yes. Each upvote increments a numeric meta value on the Fluent Support Pro ticket. You can add a column to the agent list, sort by it, and use it inside Fluent Support reports. The Feedback view is a public render of the same number agents already see.

Yes. The SleekView source filter only queries tickets that match the conditions you set, for example a specific Fluent Support category, a particular product, or a custom field flagged as public. Anything outside that filter never reaches the front end.

Only the columns you map are rendered. Replies, internal notes, attachments, and private custom fields remain inside the Fluent Support Pro admin. The card shows title, vote count, author label, status pill, and category pill, nothing more than that.

By default they can vote without logging in, with rate limiting per IP. If you prefer authenticated voting, switch the source to require a logged in WordPress user and the upvote button will gate to customers who already have an account on your site.

Yes. The mapping screen lists every status defined inside Fluent Support Pro, including custom ones added through the workflow editor. Assign each status a palette colour and the board automatically renders the right pill on every card without any code.

SleekView paginates results and queries only the columns you map, so the source query stays narrow even on large installs. Vote writes are debounced server side, and the source cache can be tuned per board to keep popular pages off the hot path of the database.

No. SleekView runs entirely on your WordPress install. The Fluent Support rows, the vote increments, the status badges, and the rendered cards live on your own database and server. No third party SaaS is part of the pipeline for the Feedback view at any step.