Yes. SleekView reads the shop_subscription post status directly, so you can filter feedback boards by member subscription state. Common patterns include showing the full board to active members, a win-back board to cancelled members, and a Pro-only board to members on higher-tier plans, all from one shortcode.

Yes. Whichever meta key you store the reason in becomes the data source. SleekView reads _cancellation_reason or any custom meta you configured. Each unique reason becomes a card with the count of subscribers who chose it as the vote total.

Votes write to wp_postmeta on the feedback CPT or directly to a column you configured. They live independently of the subscription record, so renewals, cancellations, and reactivations do not affect the vote totals. The data persists through any normal subscription lifecycle event.

Canny and FeatureBase are external SaaS tools with their own login, their own data store, and their own per-seat billing. SleekView runs inside WordPress, reads from your existing subscription tables, and ships as a one-time plugin purchase. Members vote behind their existing subscription login, no extra account needed.

Yes. Pass a plan ID or billing period attribute to the shortcode and the card set filters accordingly. Most subscription stores run two boards, a public roadmap that anyone can see and a Pro-tier roadmap visible only to members on the higher-priced plans. The same data source feeds both.

No. SleekView is fully isolated from the subscription lifecycle. Votes only touch the feedback source you configured, never the shop_subscription post or its meta. There is zero risk of an upvote click affecting a member's renewal date, status, or billing schedule.

Yes. Plan upgrade requests become a category on the board with their own vote totals. The admin view shows which subscriber posted each card, which makes outbound follow-up trivial. Most stores use a Saved view in the admin filtered to Plan upgrade plus active subscriber for the sales handoff.

Their votes and submissions persist. SleekView does not delete or hide cards based on subscription state by default. When a former subscriber returns, they see their original requests, the status updates that landed while they were gone, and any new public cards. Win-back conversations get easier.