You choose. The data source accepts any filter, including a specific label or tag that signals a thread is feedback worthy. Most teams flag threads with a simple tag so the board stays focused on intentional asks instead of every reply that crosses a channel.

You add a numeric column or meta key during setup, and SleekView increments it on every vote. Teams that prefer not to touch FluentComm tables store votes in a sidecar table keyed by message ID, which keeps the FluentComm schema unmodified.

Yes. Map the pill to any field that holds the workflow value: new, investigating, planned, shipped, closed, or any custom set. The pill renders with the color you assign and updates live whenever the source field changes in FluentComm.

Each SleekView block accepts its own source query, so you can run a separate board per channel or per category of channels. Filters on a single board let reviewers narrow to a particular channel without needing a different page for each.

Yes. WordPress roles drive who sees which board. The engineering board can show every thread with full context; the leadership board can show only the top scoring cards from the last quarter. Both read the same FluentComm source with different filters and gates.

If you mapped votes to a sidecar keyed by message ID, the votes persist for audit even after deletion. If you mapped votes to a column on the thread row itself, deleting the thread removes both. Most teams choose the sidecar so they keep the historical signal.

Yes. Each card carries a link to the underlying thread, so a reviewer who wants to read the entire conversation can do so in one click. The card itself shows the subject and the first lines of the body, plus the channel tag for context.

Notion and Linear live outside WordPress, so the link between the original thread and the tracked item is informal and easy to break. SleekView Feedback reads FluentComm directly and persists votes and statuses against the message ID, so the source of truth stays inside FluentComm itself.