No. SleekView reads the Copy.ai output rows your existing connector already saves to WordPress, so anything written to the outputs table or the equivalent meta keys is fair game. There is no second SaaS account to provision, no extra API key to manage, and no separate Copy.ai seat to pay for.

You pick the column when you configure the view. Most teams add an integer votes column on the outputs table or attach a meta key tied to each output ID. SleekView increments that value on click and reads from it on render, so the count survives connector updates and cache flushes.

Yes. The view supports numeric filters on any column, including votes, so you can hide every variant with fewer than three upvotes once a voting window closes. Hidden variants stay in the database for audit and can be brought back with a single filter change later.

Every click goes through a SQL increment that is safe under concurrent writes, so two simultaneous upvotes land as plus two and never as plus one. The card subscribes to the new count and updates in place without a full page reload, so both voters see the correct total within a second.

Yes. The board accepts manual items, which is the path most teams use for workflow requests, tone presets, and integration ideas. The card carries the same status pill, the same category tag, and the same Upvote button as a generated output, but points at a manual record you define.

If the outputs table carries a workspace identifier column, SleekView can filter the view to a single workspace or expose a workspace pill so reviewers can switch on the fly. Each workspace can carry its own category palette, its own status list, and its own access rules so brand teams stay separate.

Yes, as long as you keep the columns you mapped at setup. SleekView does not own the schema, it reads what you point it at, so a connector update that adds new columns simply gives you more fields to surface on cards. If a column is renamed, you remap it in the view config.

Yes. Place the SleekView block on a private page behind a login wall and grant the marketing role read access. Reviewers see the cards, vote on variants, and post workflow requests through that page without ever opening the WordPress admin or touching the editor surface.