SupportCandy stores tickets in its own custom table, wpsc_ticket, with status, priority, category, and assigned agent kept as fields on every row. The wp-admin ticket list mirrors that table closely, with a status column you can click to filter, but it still asks every agent to scan top to bottom to find work to pick up, which gets slow once you cross a hundred open tickets.

SleekView Kanban reads the same wpsc_ticket rows and the linked status field on each one, then renders one card per ticket grouped into columns by that field. The default statuses are Open, In Progress, Pending Customer, and Resolved, and any custom status you have added in SupportCandy Settings shows up as a column without configuration. Cards show subject, requester name, priority badge, and the assigned agent so triage is a one-glance task.

Dragging a card between columns calls the SupportCandy update API, which fires the same hooks your existing add-ons listen for, so customer notification emails, internal Slack pings, and SLA timers keep working. Tickets that need a custom status like Waiting on Engineering are handled by adding the status in SupportCandy first, then it appears on the board automatically the next time the page loads.

SupportCandy is a strong, free-friendly help desk that gives small teams a real ticket store inside WordPress, but it ships with a wp-admin list that asks every agent to do the work of grouping by hand. Reading status in a column is fine when you have ten tickets, and it gets painful when you have a hundred, because the eye keeps re-grouping the same rows on every refresh. A kanban view does that grouping once and gives the team a shared picture of where work sits.

Open is the inbox, In Progress is the active queue, Pending is the parked work that needs nudging, and Resolved is the satisfying drift right that says the day went well. The shape of the board signals problems before they hit a dashboard, like an Open column that keeps growing while In Progress stays static, which usually means the team is overloaded or the triage step is broken. Drag and drop matters because every alternative requires opening the ticket and editing the status dropdown, which is two extra clicks per change.

SleekView keeps the SupportCandy API in the loop, so the change still triggers customer emails, history entries, and downstream add-ons, with none of the friction.