No. SleekView Feedback reads the tidio_chat custom post type and post meta that your Tidio bridge already writes when chats close. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your reports chart against, so totals stay aligned across the board and exports.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by chat status, tag, department, Lyro intent, or any custom meta. Most Tidio teams expose only chats tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep the rest of the queue hidden.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require an account before voting if you want stricter dedupe. Vote totals stay consistent across pageloads and devices for known users, with cookie-based dedupe protecting anonymous voters from accidentally double-counting their own upvote.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync chats across, then maintain two sources of truth. SleekView Feedback reads Tidio data live through WordPress, so the board, the chat archive, and the dashboard always show the same numbers. There is one source of truth, your WordPress install.

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 Tidio columns once through the block UI and never touch the underlying template to change which fields render.

By default upvotes update the meta silently to avoid spamming busy agent inboxes. You can opt in to firing a standard WordPress action on each upvote that you bridge into Tidio webhooks if you want agents to see live demand, or threshold it to alerts every ten or fifty votes for a calmer cadence inside the tools they already use.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy synced from Tidio, including Lyro intents if your bridge writes them as terms. Each board is a separate block on a separate page, all reading from the same underlying chat store with their own filter and column mapping configured for that audience cleanly.

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